[SOLVED][1.14.4] Persist Player attributes on respawn

[JimiIT92]

As the title says i want to persist some modified player attributes when the player respawn. Say i've modified the strength or the health of the player, how can i reapply those modified values when the player respawn?

Edited October 20, 2019 by JimiIT92
Solved

[diesieben07]

Probably store them in a capability and re-apply in PlayerRespawnEvent.

[Differentiation]

1 hour ago, diesieben07 said:

Probably store them in a capability and re-apply in PlayerRespawnEvent.

Clone, not PlayerRespawnEvent.

[MairwunNx]

51 minutes ago, Differentiation said:

Clone, not PlayerRespawnEvent.

```kotlin @SubscribeEvent fun onPlayerRespawn(event: PlayerEvent.PlayerRespawnEvent) { ```     ```java @SubscribeEvent public void onPlayerRespawn(PlayerEvent.PlayerRespawnEvent event) { ```   upd: sorry, I thought you did not find the event.

Edited October 20, 2019 by MairwunNx

[JimiIT92]

Thank you, i was able to do this catching the Clone event
Ps: looks like notifications are broken, i haven't got one for this thread

[diesieben07]

No, this is NOT what the clone event is for...

[JimiIT92]

But then how can i retrieve the capability of the "original" player, the entity that is dead? Since there is no "getOriginal" or something like that in the respawn event

[Animefan8888]

3 hours ago, diesieben07 said:

No, this is NOT what the clone event is for...

What would it be used for then if not making data persist across death, and what event would you use for making data persist across death because there is no way to use PlayerRespawnEvent to do so.

[diesieben07]

The clone even is for transferring data from old player to new (like capabilities or in old versions IExtendedEntityProperties). Applying attributes is something else...

[RaphGamingz]

22 hours ago, diesieben07 said:

Probably store them in a capability and re-apply in PlayerRespawnEvent.

wouldn't it then be transferring the capability which stores the attributes

4 minutes ago, diesieben07 said:

The clone even is for transferring data from old player to new (like capabilities or in old versions IExtendedEntityProperties). Applying attributes is something else...

Edited October 21, 2019 by RaphGamingz

[diesieben07]

I do not understand your question.

[RaphGamingz]

10 minutes ago, diesieben07 said:

I do not understand your question.

me? JimiIT92? Animefan8888?

Edited October 21, 2019 by RaphGamingz

[diesieben07]

No, the other one who replied and asked a question... ?

[RaphGamingz]

whats the syntax called 

edit: its called ternary

Edited October 21, 2019 by RaphGamingz

[diesieben07]

Jesus lord.

You quoted me and asked a question.

I responded: I do not understand your question.

[RaphGamingz]

9 hours ago, Animefan8888 said:

What would it be used for then if not making data persist across death, and what event would you use for making data persist across death because there is no way to use PlayerRespawnEvent to do so.

i think he is asking what the event you use because you cant use playerrespawnevent (according to him)

[diesieben07]

27 minutes ago, RaphGamingz said:

wouldn't it then be transferring the capability which stores the attributes

 

[RaphGamingz]

oh 

33 minutes ago, RaphGamingz said:

wouldn't it then be transferring the capability which stores the attributes

because you said to store the attribute in a capability

Quote

Probably store them in a capability and re-apply in PlayerRespawnEvent.

then you say

Quote

The clone even is for transferring data from old player to new (like capabilities or in old versions IExtendedEntityProperties).

and you use the clone event to transfer capabilities

[diesieben07]

Yes, you use the clone event to transfer the capability data.

You do not use it to apply attributes.