Enhance torment punishment with escalating delays and subtle quirks#378
Merged
Conversation
Enhance the /lag (torment) punishment system to make it significantly more evil while keeping most mechanics subtle and unobvious: ### Disconnect Retry Cycles - When a tormented IPID reconnects, immediately restart their disconnect timer instead of letting them stay connected - 66% chance of scheduling a secondary "ghost disconnect" 20-60 seconds after the first one — nukes them if they manage a quick reconnect - Extended base timer from 5-235s to 8-292s for longer sustained torture ### Increased Ghost Rate - Bumped from 1/3 to 1/2 (50%) chance that messages vanish silently - Applies to both IC and OOC messages equally ### Hidden, Unnoticeable Quirks 1. **Variable delays**: Message delivery now ranges 10-35s (IC) / 8-40s (OOC) instead of fixed 20s — unpredictability makes it hard to pinpoint 2. **Rare duplication**: 1/25 chance (IC) / 1/20 chance (OOC) that the message is delivered twice with different delays, simulating race conditions 3. **Name corruption**: 1/30 chance per OOC message to subtly corrupt the sender's displayed name by 1 ASCII character — very noticeable after the fact but goes unnoticed in real time 4. **Delayed area change confirmation**: 1/25 chance that moving to a new area delays the "Moved to X" confirmation by 15-45 seconds, making them question if they actually switched areas All quirks use the existing tormentIntn RNG for consistency. Disconnects are now truly unpredictable and persist through reconnects. https://claude.ai/code/session_01RBPSKwtAp6Z5ExDNHtf95a
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands the torment punishment system with more sophisticated harassment mechanics, including escalating reconnect penalties, variable message delays, rare "hidden quirks" (duplication, name corruption, delayed confirmations), and improved unpredictability to make the punishment less obvious while more effective at discouraging continued play.
Key Changes
startTormentDisconnectis immediately rescheduled, ensuring lag persists across reconnection attemptsImplementation Details
time.AfterFuncto avoid parking goroutine stacks during waitsisIPIDTormented()before executing, allowing/unlagor/untormentto cancel pending timersrune(1+tormentIntn(2))shift to avoid obvious garblingtormentIntn()for consistency with existing randomizationhttps://claude.ai/code/session_01RBPSKwtAp6Z5ExDNHtf95a