5HT2
commented
3 years ago now players will be autologged from the mere existence of a crystal.
No, you're misunderstanding how it works.
It calculates the damage of loaded crystals, and if you're close enough that exploding the crystal would kill you it logs.
Previously, it would log for ANY crystal placed in a hardcoded range, when placed.
The main differences between the two behaviors is proper damage calculation and logging if you walk into a crystal vs a crystal being placed on you.
When the Crystal option is selected, at say 5 times the range that would cause autologging, start pinging the bell in a distressed pattern pingpingpingpingping
Well CrystalESP displays the damage it'll do to you, iirc it also displays it as a color, so if you walk closer you'll see it.
automatically put baritone into pause
Pause instead of logout is a fantastic idea, but only for modes such as this one and maybe player range.
HoratioGamer
Is your feature request related to a problem? Please describe. Owing to a change in the default behaviour of the Crystal feature of the AutoLog module, where before players only autologged when a crystal was actively placed too close to them, now players will be autologged from the mere existence of a crystal. So when one is walking around, one cannot have Crystal active while walking by crystals.
Describe the solution you'd like Since walking toward a crystal is a gradual process, there must be a range at which the crystal is judged to be too potentially harmful and the player is autologged. On 2B2T this consigns the player to another hour, or 4 in the Q getting back in.
As an example, when a stash comes into scanner range, there is an audible bell and a text message in the chat scroll informing the user of KAMI of the presence of the stash.
Combine the two concepts. When the Crystal option is selected, at say 5 times the range that would cause autologging, start pinging the bell in a distressed pattern pingpingpingpingping (5 bells = nautical for immediate hazard) and put the message in the chat scroll -- "too close to a crystal with Crystal Autologging active -- take alternative action", and automatically put baritone into pause. This would allow the user to evaluate the situation and maybe turn off the Crystal option so that they can walk past the crystal, explode it with an arrow, or go another way.
Describe alternatives you've considered
Additional context