Feature - Rejected Starter items - Preference and command

[Theraze]

Would be nice to have a command to collect the newbie items. This would let HC people optimize their worthless item gathering as well. Shouldn't be too difficult; basically just calling the 'optimized' worthless item gatherer with either 0 or 3 worthless items, probably 3, so it's guaranteed to work.

Tied into this, would be nice to have a preference regarding whether you'd like to use the optimized or cheap system. Defaults to detecting which it thinks it should use, but can be set to always use optimized or always use cheap (which of course becomes optimized once you've collected the newbie items).

The combination of these two means that you can optimize your ascension's worthless item gathering as quickly as you actually have meat for it, and nobody should feel the need to circumnavigate the system with large quantities of individual worthless item collections because they actually have some control over how it works.

 

[lostcalpolydude]

I feel like this was related to some other discussion. Since mafia uses 1 chewing gum at a time in-run and goes for saving server hits in aftercore, I don't think there's any need to change things (though it's possible something was changed after this thread was made).

 

[Theraze]

Basically, during aftercore or SC, you use an optimized system which will automatically retrieve all 13 starter items if you ask for 1. During HC or ronin, it will buy and use one at a time.

The request was to make it easier to achieve the optimized system earlier if you're in a meat-rich run, and allow for manual control of the optimized system in a SC meat-poor run (fist, for example) so that mafia isn't doing things that the player isn't asking it to do and screwing you out of your healing or nightcap.

 

[lostcalpolydude]

The request was to make it easier to achieve the optimized system earlier if you're in a meat-rich run

I don't think that's really necessary. You can always just "use 10 chewing gum on a string" if you really want to.

and allow for manual control of the optimized system in a SC meat-poor run (fist, for example)

The check is actually KoLCharacter.canInteract(), so this isn't actually an issue. Unless the concern is post-ronin fist runs, but that seems like such a niche case that it isn't worth worrying about (and probably isn't an actual problem).