- Removed Client Side requirement
- Added a config file (in
config/safelogin/config.json5) withprotectionType, MOVE (default), COMMAND, and GUI- MOVE, (mostly) the same mode as 1.0.0 but the way you are unpushable is executed differently (fully server side approach)
- COMMAND, you must enter in a (configurable) command to disable the protection, if you attempt to move off the block, you will be stopped and prompted to enter the command
- GUI, when attempting to leave your login block, a GUI will open and upon closing, will disable your login protection
delayJoinMessage, if you wish to only have the join message send when the player has disabled protection (i.e successfully loaded in)commandwhere you can set the command in which the player executes to disable protection in COMMAND Protection Type
- Added logic to store previous user state in case (for instance) the player is in creative mode and their invulnerable boolean was set to true before SafeLogin set it to true, so when protection is disabled mobs will target and can attack and damage you in creative mode upon having protection disabled
- Added ignoring of certain packets (attack, break, and place) when invulnerable in case someone were to try to abuse the perks of invulnerability (even if they could only hit, break or place, while staying inside 1 block)
Login protection, invulnerable (no damage), invisible (no mob tracking), un-pushable while in the same block you logged in on. You are still pushable by fluid like running water, and it will disable login protection and if you log out in an ocean, it will disable as well (moved off the block you were on, y-level), so long as you log out and log in on a solid block, you should be fine/it should work as intended, if not, open an issue.


