Rigor Module


New type of module: Rigor modules. Rigor modules increase the probability of a recipe returning its most valuable product.

Content
4 days ago
2.0
3.40K
Manufacturing

g Broken server after update

7 days ago
(updated 7 days ago)

Hi
After mods update joining to server is impossible.
Ingame message after my translation: "next event managers are not identical to server. That means that mods are dangerous (save/load) for multiplayer (see log for details): rigor mod
Where is that log? Closest i could find is at current user\AppData\Roaming\Factorio\factorio-current:
122.131 Error ClientMultiplayerManager.cpp:1081: mod-rigor-module was registered for the following events when the map was saved but has not re-registered them as a result of loading: on_tick (ID 0)
122.131 Error ClientMultiplayerManager.cpp:86: MultiplayerManager failed: "" + multiplayer.script-event-mismatch + "
" + "
Or we need some another log file?
Server admin and me tried all the combinations of actions that we could guess, updating and reloading mods, but that didn't work.

7 days ago

Thanks for the report! Yes, that's the correct (client-side) log. The server also has its own log which could be helpful too, but I'm familiar with this family of multiplayer bug anyway.

If possible, do you know what was the rigor-module version before upgrade? And the version after upgrade too, though I'm guessing that's 0.3.2. Also were any mods removed?

I think I understand this issue enough for a general fix, but anything else you can provide will definitely help me test/verify any fix.

7 days ago

Rigor is right now 0.3.2, server is running more than 22 days, back then when it was created it had up to date mods. Admin say that he don't have old log files. Also he could send you our current save file for tests.

6 days ago

A savefile would be super helpful, thank you! That should be more than enough debugging and validation.

6 days ago

Here it is
https://limewire.com/d/r1bu1#HQqbeNYcqq
Thank you for saving our save)

5 days ago

Just pushed v0.3.3, which hopefully fixes this issue. MP bugs are always harder to test, so please let me know if it works!

5 days ago

Just pushed v0.3.3, which hopefully fixes this issue. MP bugs are always harder to test, so please let me know if it works!

Thank you! It works just perfect

5 days ago

🎉🎉

And thanks for playing my mods! It's very cool to see a Crucible base in the wild.

5 days ago

With 0.3.3 I get the following crash:

   38.614 Error ServerMultiplayerManager.cpp:84: MultiplayerManager failed: "The mod Rigor Module (0.3.3) caused a non-recoverable error.
 Please report this error to the mod author.
 Error while running event rigor-module::on_configuration_changed
 'health': real number expected got nil.
 stack traceback:
         [C]: in function '__newindex'
         __rigor-module__/control-helpers.lua:211: in function 'fast_replace_entity'
         __rigor-module__/control-helpers.lua:282: in function 'update_machine_for_rigor'
         __rigor-module__/control-helpers.lua:32: in function 'update_all_entities'
         __rigor-module__/control.lua:14: in function <__rigor-module__/control.lua:13>"
   38.614 Info ServerMultiplayerManager.cpp:808: updateTick(18446744073709551615) changing state from(CreatingGame) to(InitializationFailed)
   38.614 Info CommandLineMultiplayer.cpp:211: Exit point.
   38.626 Info ServerMultiplayerManager.cpp:146: Quitting multiplayer connection.
   38.626 Info ServerMultiplayerManager.cpp:808: updateTick(18446744073709551615) changing state from(InitializationFailed) to(Closed)
   38.626 Info ServerMultiplayerManager.cpp:166: Deleting active scenario (global = true).
   38.856 Info UDPSocket.cpp:238: Closing socket
   38.857 Goodbye
5 days ago

(But this seems to be an issue unrelated to one of this thread)

5 days ago

For now, I've adjusted the line in question to

    if health then
        new_entity.health = health
    end

Seems to work, but it's just band-aid.

5 days ago

Thanks for the report, and for finding a workaround! I'll have a fix up later today.

4 days ago

Fixed in v0.3.4.

New response