The devs have decided to remove the research queue implementation for 0.17. Nope, once again ONE dev has decided. So the overall decision was to remove this feature, on the condition that I have to say that I kovarex, personally, killed it. I am the one to blame :) Feels like the bots vs belts topi...

The thing is optional, if you don't like it don't use it. It is always "not good" if a single person decides what others need/want ;) And in a game that is all about automation, this is clearly contrary. It's ok to say "this is the way 'we' would like you to play" and disable it ...

One way to reduce the clutter would be to destroy empty blueprints on curser when you press 'q'. Have them required to be put in a slot if one wants an empty sheet. As you said, there are two kinds of blueprint use-cases. The "I have a good build I want to use often", and the "I need ...

It's all good (for me). If I don't find something I just ask on discord

Things I might have searched for in the last month would be:
Prototype/GuiStyle
Prototype/Rail
Prototype/TrainStop

But since I don't even remember that, it is not in the least important for me.

Possible reason for low usage: people don't find what they are looking for too often and disregard the wiki for that kind of lookup

I did not often search for prototypes, but when I did all I found in the wiki was a red link, meaning there is no page for that prototype.

Also part of: viewtopic.php?f=28&t=60942

I started a little mod yesterday that I might extend to more stuff and the ability to generate the add{} code to copy/paste. https://mods.factorio.com/mod/kitchensink But that's inside the game. Some outside reference would be better I guess, for the cases where your own code prevents starting the m...

@eradicator

yes, that is what I recommended in discord too. I only opened this thread so it is here to find. As in "asked and answered"

The best option would be to be able to choose. The changed by player can be emulated by hooking the other two events (on_gui_closed and on_entity_settings_pasted) The changed due to circuit-condition would catch all changes, but might lead to more (over-)load when you have lots of "flickering&q...

Would fire when the the control_behavior of an entity gets changed. My use-case: At the moment I have to iterate all lamps on a map to see if there is any change (i.e. in use_colors) An event that fires if there is a change would make a lot of useless iteration and checks disappear. To not fire for ...

As a LuaEntitiy the train-stop already got an unique id in the unit_number.

Just so the request is there, with no real hope that it gets implemented :) Use-case: Allow for dynamic recipes. Either influenced by external factors, or for production challenges/goals. "Build 100000 green circuits, but due to [reason] they cost double the iron plates and an additional copper...

@eradicator: Yea, something like https://getbootstrap.com/docs/4.1/components/alerts/ would be better I guess. The other one only gives a fast overview how things look with that theme providing that you already know how to create stuff. For starters a list of available types/styles and how they woul...

Brute force for the luaTrain.rotate() would be serialization and deserialization in the opposite direction, but (since you can on the c++ side) keep the trainId.
Same should work for the lone carriage/loco.

That would be the "how they" look part. Still would be no big help for modders since you do not get the type/style you have to use in lua to get them.

You already got them in the game somewhere. They are used for example in the train schedule UI.
Even better would be real support for tabbed planels.

Not modding interface related, but would be a big help for any modder that tries to do UIs in factorio. A kitchensink is an overview of all available (vanilla) styles, their configurable attributes, and how they look. Something like this http://code.divshot.com/bootstrap-theme-white-plum/examples/ki...

Alternative to that: Put a big battery in the fuel-slot and let it be charged at stations or exchanged by the player. If there was an event on_remove_fuel you could take the leftover burner-gauge and tag the item with it (not sure if/how that would work) more generic: Put a tank (the one holding liq...

I know, there is for sure nothing more unimportant than this. But anyway:
I would like to be able to only remove certain types of decoratives in an area.