Separate spikesuits out into sub groups allowing for easier logic placement.

[nn357]

Following on from the discussion about some spikesuits being too difficult / the room carry thing etc etc and with the possibility of an expert+ type intermediate level to introduce the tech it is probably a good idea to subdivide the tech as there are so many setups.

Not all of the spikesuit setups are more difficult than some for the same reasons though, it seems the issues people have with some of the more complex setups are.

canTrickySpikesuit (A spikesuit setup that requires complex / difficult inputs / has a higher chance of failure - eg noob bridge bomb boosts / quick drop etc. -> this room has a good farm and repawning crumbles so you get at least a few attemps per room, its just the spikesuit requires quick inputs.

canFarmlessSpikesuit (A spikesuit in a room with no/very poor quality farm, where failing it will require going somewhere else to farm back the health or room resets- draygons room for example)

canPatientSpikesuit (A spikesuit that takes a longer time than usual to setup).. eg gauntlet from the right side requires breaking blocks / waiting for acid, running over a respawning enemy, potentially taking acid damage if you mess it up and re-farming health).

Perhaps 3 options is too many / not enough (names are just first ideas and probably needs to be refined).

[blkerby]

Seems like a good starting point to think about.

The "canFarmlessSpikesuit" case seems handled already by the lenience requirements, so probably no need for that tech.

Something like "canPatientSpikesuit" probably makes sense to use on setups that involves resetting the room, either because of a cross-room shinecharge setup or because of a non-respawning farm. Though if the farm is good relative to the amount of spike damage, where you can do a lot of attempts per room reset, then it's probably not needed. This can depend on whether it is spikes vs. thorns, how good the farm is, and what suit(s) you have.