LWC
LWC copied to clipboard
Remove all actions after turning persist off
Common source of confusion for players using persist mode; there may still be a lingering action (e.g. /lock
) after turning persist off. Eventually, they may accidentally apply that action.
Example
- Player executes
/lwc mode persist
to turn on persist mode - Player executes
/lock
and begins punching many chests to mass lock them - Player executes
/lwc mode persist
to turn off persist mode - Later, player punches a lockable item (e.g. sign or chest) and accidentally locks it, because of lingering lock action
Notes
- This change was made via GitHub's file edit interface; therefore it has not been tested for compilation or runtime errors
- To ensure I used the correct behaviour, I used
DropTransferModule.java
and line 1927 ofLWC.java
for reference
- To ensure I used the correct behaviour, I used
- This suggestion arose after repeated confusion and accidents on our server. I also think this is more convenient behaviour (wouldn't turning persist mode off signal the end of one's mass-locking, for example?)