I was having an issue with projectiles triggering before reaching their target, and I suspected it had something to do with their max range.
After a while, I found out the default max range of projectiles is 1000, which isn't listed in the docs.
Should be an easy fix, thank you in advance!

Most modded prototypes already follow the third restriction, so people won't really have to update anything. This change simplifies string matching in mods as well, and as someone who's made both mods and external tools, I'd definitely support this change.

Upon further inspection, it's because I had the quick_bar_set_selected_page permission disabled.
I would expect this permission to actually disable the player's ability to do that, rather than just make it desync state between the api and the client.

When a player changes their active quickbar row manually, whether it's from Shift + #, clicking on the button, using previous/next hotkeys, or rotating quickbars, none of it is reflected in the API. The script isn't ever aware of what the active quickbar is, unless the script sets the active quickba...

When clearing the bar through script, the bar button is still toggled, even though there is no bar. This makes the player have to click on the button twice when they want to set the bar manually, instead of the normal twice. If the player closes the GUI and opens it again, it's fixed. Steps to repro...

It's almost impossible to search for multiple words at once currently, for the example "Resource Marker" I would want both of those words to have the same priority in a match, so if something was most recently updated that had just the word "resource", that would show up first, a...

Sounds like you'd want to add an extra layer for biters anyway, so they are not impacted by this setting. That's an option, but I'm trying to avoid creating any new collision layers if I can. It still doesn't solve the original issue for when they still collide, and I am not comfortable forcing the...

Why not simply remove the player layer from pipe collision mask? Is it really so important for characters to collide with pipes when the intent is for pipes to be crossable? I can see the importance for larger buildings, but not for something so small as a pipe. Because biters have the same mask as...

I'm currently writing Squeak Through 2 from scratch, as the original mod hasn't been updated since it's 1.1 version bump and the mod creator is MIA. `pipe` and `pipe-to-ground` entities are causing a bit of trouble, because of the 0.2 border added to the bounding box when the FluidBox receives a new...

As I suspected, just wanted to put it here for public record.
For clarification, would the custom collision box orientations still be an issue in 2.0 with rails having hard coded collision boxes, or is that part irrelevant as well due to the new rails?

I'm assuming this is because of the secondary collision box that curved rails have, but when the curved part collides with something and the straight part does not, the method returns the incorrect result. I don't expect this to be fixed for 1.1.x, but I at least wanted to make sure this was made aw...

Sometimes, though, I have something sitting in my clipboard that's semi important to me that I just haven't had the chance to paste somewhere, yet. Sometimes, too, it's currently the only existing copy, or would require some time and hassle to get back to the original. If you're on windows, you can...

As the title says, NothingModifier is missing the type field, while all of the other technology effect modifiers have it.

The Binding of Isaac wiki does a decent job of handling different DLC items and such, here's a page with a lot of them (scroll down to synergies): https://bindingofisaacrebirth.fandom.com/wiki/Brimstone Just a small icon next to the thing it's related to, slightly large for my liking, but it's very ...

I have a bunch of sprites that are increasing in "height", that when created start at a "height" of 0. Right now I have to call LuaRendering::bring_to_front() on every single rendering object in reverse order every time a new one is made, whereas a send_to_back() method would onl...

LuaSurface::create_entity allows the use of the `type` field for use with underground belts, and that is listed. However, you can set "input" and "output" on loaders as well, and this isn't listed on the method doc. I assume this is not intentional, and I'm glad I guessed that i...

It's for when characters are running against a collision box, how close they have to be to "slip" in a different direction to avoid getting caught on the corners of collision boxes too much. You'll notice it whenever you try to run between two entities right next to each other, like stone ...

Thanks for fixing those! I went through every class searching for [or "] and found a couple more: LuaCustomInputPrototype::consuming LuaFluidBoxPrototype::production_type LuaRendering::set_alignment LuaRendering::set_vertical_alignment LuaSurface::create_entity.type for underground-belt

LuaItemStack::set_mapper() has an UpgradeFilter parameter that says it can be nil to remove a filter in the description, but isn't marked as optional in the actual documentation. This trickles down to a LuaLS warning, either missing-parameter or param-type-mismatch.

There are a number of places where things like function parameters and concept fields have a type of string, but can only be strings from a defined list. Would it be possible to make those unions, that way they show up in the autocomplete list when using FMTK + LuaLS? It's not the end of the world b...