I suspect that "write support for index of existing element" is much more complex to implmement than it sounds or they'd have added it long ago. And without writable index there can't be writable order. I struggle to imagine what may let you add a new element at a position, but not move a...

Potential duplicate: https://forums.factorio.com/viewtopic.php?f=28&t=99233 Less a duplicate and more an elaboration. They want the order property to be writable specifically, so that rearranging elements is as easy as changing their order. edit: Personally, I would love to see a way to rearran...

None of the energy source prototypes in runtime say what units emissions are in. Most other fields are also without units or any description.

NotRexButCaesar wrote: ↑

Wed Sep 15, 2021 2:50 pm

For the production graphs, I believe there is a way to hide recipes: the vanilla barrels use this to stay out of production graphs.

But how do you hide the generator's consumption?

I don't think the API website should need any tutorial. It must be simple and intuitive to use.

Yea, it should say item-names and entity-names. The "etc" is also suspicious. Are there actually any other prototypes supported other than __ITEM__ and __ENTITY__? There is also __TILE__ and some other things. But regardless, there should be a proper list of keywords, not "items and ...

https://wiki.factorio.com/Tutorial:Localisation#Built-in_parameters says "We can also use this for items and entities etc.", but there is no list of acceptable keywords anywhere.

The "crafting" recipe category is hardcoded to disallow fluids, but this isn't documented anywhere obvious (Recipe.category or RecipeCategory). If anything is hardcoded about any other categories, or something else about the "crafting" category, it would also be good to know.

Ah, sorry. What is considered official then, besides Prototype/* and Types/* pages?

https://wiki.factorio.com/Mod_portal_API - the field "score" in mod result is undocumented.

Sanqui wrote: ↑

Fri Sep 03, 2021 1:50 pm

The old web had to go

Just to clarify, you mean the backend and you took this opportunity to redesign the frontend, or was there something objectionable about the old design?

I observe choppines and reduced responsiveness while scrolling the classes page. Doesn't happen in the old version.

A better and unambiguous logic would be to check if both events fire. If yes, then placed by a player (and you get which from the player event). The effectiveness of this depends on the event order though.

Remove the monospace font altogether? It makes it so much harder to read. If not, the above font-weight change would help, perhaps generally making the monospace text bigger would also be better. Edit: this may actually be more to do with the font choice (which seems to be unspecified(?), so might ...

The very first impression upon opening the docs: this design is too overloaded and overcomplicated for the task. Although the expand button helps to hide the background and increase usable space, so it lessens the effect somewhat. At a first glance, the search is nearly useless. I can search through...

https://lua-api.factorio.com/latest/Concepts.html#TrainScheduleRecord doesn't say that wait_conditions can be nil.

-> Thanks, fixed for the next release.

https://lua-api.factorio.com/latest/Concepts.html#SoundType is sorely missing any details about what is special or different about all these types. No info on the wiki either (https://wiki.factorio.com/Prototype/Sound#category).

Someone was confused the other day about what nil means in https://lua-api.factorio.com/latest/LuaEntity.html#LuaEntity.render_to_forces . Is it render to all or render to none? -> Thanks to you (and Eradicator), I have clarified this for the next release. If it's nil (and in the case of forces, an...

There is about as much in common (if not less) between prototype explorer and data/control stage as between the stages themselves. So take what it shows with a grain of salt.

Then read it from the prototype: https://lua-api.factorio.com/latest/LuaEntityPrototype.html#LuaEntityPrototype.filter_count