player.setInvincible(boolean)

yahwho · Sep 26th 2018

Hi!

I know we have a player.setInvisible(boolean); but can we also get a player.setInvincible(boolean); ?

I know there is a player.setCreativeModeEnabled(boolean); but I kind of don't like the idea of using that "just in-case".

Good luck on the update tonight!

Solveign · Sep 26th 2018

Hi yahwho,
can't you use

public class PlayerDamageEvent

extends PlayerEvent
implements Cancellable

and depending on the player just cancel all those events?

yahwho · Sep 26th 2018

Hmm yes, will require a little more coding rather than the two lines I had hoped, but yes I can get what I need to to work in the meantime with PlayerDamageEvent

yahwho · Sep 27th 2018

Actually no, it doesn't really work. Canceling player damage still means the thirst and hunger bar goes down

Solveign · Sep 28th 2018

Ok, didn‘t take that kind of damage into account, sorry

yahwho · Sep 28th 2018

No need to say sorry Solveign It's for the first server screen - just don't want people tabbing to chrome (other browsers are available hehe) to read the rules only to return to find their character dead. I've implemented the no damage for now, but someone may find they need food and water rather desperately if they stay on that screen too long.

red51 · Sep 28th 2018

Actually it's intended that the hunger/thirst bar still go down when cancelling the PlayerDamage event, but the player doesn't take any damage

If you want to disable hunger/thirst, you have either have to disable it by setting the permission key (although this could be overridden if the player permission group gets changed in the meantime), or alternatively you have to create a timer and set the hunger/thirst back to 100 every minute or so, for example:

Java

@EventMethod
public void onPlayerSpawnEvent(PlayerSpawnEvent evt){
    Timer timer = new Timer(60, 0, -1, () -> {
        evt.getPlayer().setHunger(100);
        evt.getPlayer().setThirst(100);
    });
    timer.start();
}

yahwho · Sep 28th 2018

Cool i'll try that, I'll also use an accessor before the mutator so people don't use it it cheat their health back up

Solveign · Sep 29th 2018

If you work with that timer you will probably need to stop the timer when the player logs out, otherwise you would probably get a nullpointer exception the next time that timerevent is triggered...

red51 · Sep 29th 2018

Quote from Solveign

If you work with that timer you will probably need to stop the timer when the player logs out, otherwise you would probably get a nullpointer exception the next time that timerevent is triggered...

Good point! You won't get a nullpointer though, but it's still a bad thing if too many unnecessary timers are running in the background. Having a small check inside the timer if the player is still connected (and kill it if needed) would be indeed a better approach:

Java

@EventMethod
public void onPlayerSpawnEvent(PlayerSpawnEvent evt){
    //Since we need a reference to our timer, we have to init it with a null task...
    Timer timer = new Timer(60, 0, -1, null);
    //...and set the task separately
    timer.setTask(() -> {
        Player player = evt.getPlayer();
        if(!player.isConnected()){
            //Kill the timer
            timer.kill();
            return;
        }
        player.setHunger(100);
        player.setThirst(100);
    });
    timer.start();
}

Display More

Participate now!