Maddy Miller
Maddy Miller
This is caused by a bug in Spigot, where removing the original drops causes the tool to not take damage
So this wouldn't really be feasible in terms of pathfinding, as these lodestones would presumably be fairly far away. Best that'd be possible to do without killing performance would just...
The main concern here is that pausing it instead of resetting it requires keeping around a MIDI Sequencer, which has an open file handle and uses a decent amount of...
A timeout would be problematic, but having a max amount paused could technically work. My concerns there would be around what would happen if that limit is hit, would it...
I’d rather it not reset the oldest one when the limit is reached as that’s realistically more confusing behaviour, and also would require more tracking. And sure, unloading the sequencer...
This sounds like the issue is Spigot isn't providing the item in the list of results, like it should. This is a bit of a larger issue that involves me...
This isn't a bug, this is a feature request.
This sounds like Spigot has stopped persisting that information on carts. This would be a Spigot bug - would need to say how resolvable it is, because in the past...
As I said, "because in the past setting it twice caused carts to become invalid". If that bug still exists, that's not doable.
I'd question how useful this is as a blanket option. It feels like a better way of refilling them would be more helpful? (Including admin refills that keep them infinite,...