It would be nice to have the save. I was recently looking at trying to improve performance around this exact thing.

Circuits can only 'request to close' a signal; they can never force it to be green and even in the 'try to make it closed' state the tooltip explains that it's not a guarantee that it will happen:

Last i checked the game supports ipv6.

Unfortunately there is no generic drag-and-drop list. Every one you see in the base game is a custom implementation based off the way it needs to be used in that GUI.

... UPS issue in late-game forcing you to use only one type of solution: only solar energy can be used, only trains can be used to transport basic materials, etc... Adding new UPS-friendly ways to do things can add more diversity to the late game. ... If ultimate UPS is the goal, and there is a 'be...

https://wiki.factorio.com/Application_directory should have the information you want. Mind if I ask: why do you not have your games/programs on the SSD? If you don't have your games/programs on the SSD what do you have on it? The whole idea of the SSD is anything you put on it is fast... so if you d...

:) /c game.player.character.die() game.player.ticks_to_respawn = nil game.player.ticks_to_respawn = 10 Anyway, it doesn't seem to be important, but I guess it's possible to create unintentionally a character in events by mods in some cases. That's the same as setting ticks_to_respawn on a not-dead ...

This is what data stage is for and why mods are a thing. So, no.

Unless another developer wants to go looking into it I'm fine with saying that we only support 24 bit, 48000 Hz audio and if anything else works that's fine but we won't be looking into bug reports/issues around audio outside that setting.

I can't reproduce any issue: when I walk into a landmine it triggers the event as expected:

Writing a value to ticks_to_respawn forces the player into the respawn state regardless of where they were before. This doesn't kill the character entity they were previously controlling (if any). Additionally the character entity is just that; an entity. There can be any number of them in the game ...

Thanks for the report however how it is working is how it is meant to work. The respawn time is on the character prototype: https://wiki.factorio.com/Prototype/Cha ... spawn_time and is not adjustable runtime.

A small addon to the conversation: if a given method/property is valid for something like an entity/player can runtime depend on the state of the entity so saying 'this method/property is valid for this object' is not a simple docs-parsing task. Example: reading data about a crafting queue from a pl...

Yes, but this returns the actual object name, like "LuaTilePrototype", etc, right? So in the case of LuaEntityPrototype, I'd still need to query the .type property to know exactly which entity type has been passed, correct? So in a function where it's meant to be passed either LuaTileProt...

You're describing object_name and it already exists as mentioned: https://lua-api.factorio.com/latest/Lua ... bject_name for each thing in the API.

In the vast majority of the usages asking for an invalid key/method is an error and silently suppressing that error by returning nil isn't doing mod developers a favor. Ideally the game could verify that the API calls are even vaguely possible before they get executed but due to Lua being Lua that i...

Most likely that is the issue. The root problem is books were written ignoring the core mechanics of item-with-inventory.. unfortunately. So once that was fixed generically it broke the blueprint book behavior.

Thanks for the report. It's now fixed for the next release.

Thanks for the report. I added a check for this for the next release. A fluid stream with no particle support makes no sense because it will just kill itself the first time it updates.

Thanks for the report however I can't reproduce what you describe. It raises script_raised_destroy every time.