Factorio Forums

• "Disable" widgets so that users cannot interface with them, but is still visible, just faded.
• New events such as, on_player_open_inventory, and on_player_open_main_menu.
• Able to create drop down menu widgets. (Already Implemented as of 0.15)
• Before force merge, and after force merge events. (ssilk's idea)
• Able to create slider widgets.
• Label widget can word wrap.
• Force colors?

•A more advanced graphical user interface for advanced users in the api. For example being able to manipulate the size and position of gui.

Karutoh wrote: [*]Change game.merge_forces(string source, string destination) to game.merge_forces(string source, string destination, bool mergeResearch). This will allow you to merge research as well.[/*]

[*]New events such as, on_player_open_inventory, and on_player_open_main_menu.[/*]

ssilk wrote:

Karutoh wrote: [*]Change game.merge_forces(string source, string destination) to game.merge_forces(string source, string destination, bool mergeResearch). This will allow you to merge research as well.[/*]

Mergeing can be done in several ways and makes no sense to introduce just one. Such a merge needs to be programmed out. Which is no problem, just a programmers work. what makes more sense is to have an event (...before_merge, ...after_merge) that is called when two forces are merged. Isn't that already the case?

[*]New events such as, on_player_open_inventory, and on_player_open_main_menu.[/*]

Sorry, I don't see the use case for that. Maybe you can explain that...

Karutoh wrote:

ssilk wrote:

Karutoh wrote: [*]Change game.merge_forces(string source, string destination) to game.merge_forces(string source, string destination, bool mergeResearch). This will allow you to merge research as well.[/*]

Mergeing can be done in several ways and makes no sense to introduce just one. Such a merge needs to be programmed out. Which is no problem, just a programmers work. what makes more sense is to have an event (...before_merge, ...after_merge) that is called when two forces are merged. Isn't that already the case?

[*]New events such as, on_player_open_inventory, and on_player_open_main_menu.[/*]

Sorry, I don't see the use case for that. Maybe you can explain that...

I do like that idea better, however there still needs to be a way to get, and modify the research of a force, I'll move it up to the top. As an example for on_player_open_inventory and on_player_open_main_menu, I have a mod that's mainly a gui, the idea would be to close this gui if the player were to open the main menu, or open their inventory.

Klonan wrote: You can easily modify the technologies of a force:
http://lua-api.factorio.com/latest/LuaF ... chnologies

Karutoh wrote:

Klonan wrote: You can easily modify the technologies of a force:
http://lua-api.factorio.com/latest/LuaF ... chnologies

This doesn't work, all the values in that array are nil. What am I missing?

Rseding91 wrote:Are you trying to iterate it with ipairs? Because that doesn't work per what the API docs page says about the "LuaCustomTable" type.

darkfrei wrote:

Rseding91 wrote:Are you trying to iterate it with ipairs? Because that doesn't work per what the API docs page says about the "LuaCustomTable" type.

What is different between pairs and ipairs?

Rseding91 wrote:Are you trying to iterate it with ipairs? Because that doesn't work per what the API docs page says about the "LuaCustomTable" type.

for i = 0, #ply.force.technologies, 1 do
	game.print(ply.force.technologies[i]);
end

for i, t in pairs(ply.force.technologies) do
	game.print(t.name);
end

Rseding91 wrote:The technologies table keys are strings - there aren't any prototypes with integer names so when you try to index it with 1, 2, 3 and so on it doesn't find any result and returns nil.

Rseding91 wrote:The technologies table keys are strings - there aren't any prototypes with integer names so when you try to index it with 1, 2, 3 and so on it doesn't find any result and returns nil.

Mjo20031 wrote:sslik did'nt you say one suggestion per per thread?

1. Call me ssilk, SSilk or ßilk. ßilk is the word to express a state that cannot exists due to the rules (in that case of German language a word that begins with sharp s), but exists, cause it is possible. And don't ask me about the "ilk".
2. Who am I to take my sword and cut a useful discussion?
3. I "remind" sometimes to the rules, but what I have in mind is to let the users think about useful behavior.
4. Yes, but I said also, there is rule number zero, which allows to change rules, if it makes sense.