Hi, I made an Extended Entity Properties because I want to save some data but when the player dies, the data is not saved and I don't know why.

 

 

Code: https://www.github.com/DiabolicaTrix/MinecraftLifeRPG

Oh, I forgot, the EEP is only saved on server side. I tried to put a Sysout in my debugItem and the output is: 


[10:47:10] [Client thread/INFO] [sTDOUT]: [me.diabolicatrix.items.ItemDebug:onItemUse:49]: 0 !
[10:47:10] [server thread/INFO] [sTDOUT]: [me.diabolicatrix.items.ItemDebug:onItemUse:49]: 2 !


and here is my onPlayerClone event:

    @SubscribeEvent

    public void onPlayerClone(PlayerEvent.Clone event)

    {

        if(event.wasDeath)

        {

            NBTTagCompound compound = new NBTTagCompound();

            PlayerEEP.get(event.original).saveNBTData(compound);

            PlayerEEP.get(event.entityPlayer).loadNBTData(compound);

        }

    }

It's worth noting that

IEEP

has been deprecated in favour of the Capability system and may eventually be removed.

@diesieben07 No it's not, I want the EEP to be synced with the client

 

 

@Choonster Oh, I didn't know, I'll give it a try.

@diesieben07 No it's not, I want the EEP to be synced with the client

 

That doesn't happen automatically. If code on one side (like server) is changing the EEP without similar code running on client, then you'd have to use a custom packet I think to sync it.

 

Also, are you doing this for your own custom entity or adding EEP for vanilla entities. For your own custom entities you don't really need to use the EEP system, but rather can directly override the writeToNBT() and readFromNBT() methods. But again, to sync client to server you need a packet.

Ok, I tried with the Capabilities but it's doing the exact same thing, the value is saved server-side only. https://github.com/DiabolicaTrix/MinecraftLifeRPG/blob/master/src/main/java/me/diabolicatrix/other/PlayerCapabilities.java

Sorry, I misexplained. The AttachCapabilitiesEvent is called before the PlayerCloneEvent on client-side but it works on server-side.

 

 

 

[15:30:19] [server thread/INFO] [sTDOUT]: [me.diabolicatrix.events.CommonEventHandler:onAttachCapability:62]: Attach Server

[15:30:19] [server thread/INFO] [sTDOUT]: [me.diabolicatrix.events.CommonEventHandler:onPlayerCloned:49]: Clone (server only)

[15:30:19] [Client thread/INFO] [sTDOUT]: [me.diabolicatrix.events.CommonEventHandler:onAttachCapability:62]: Attach Client

 

 

So even if I try to sync with a packet, the value will be overwritten by the attach event.

In my constructor, I set the default values of my variables. And when I attach the capability, I make a new Instance of PlayerCapabilities.

It's doing exactly what I said before:

 

 

 

[16:43:24] [server thread/INFO] [sTDOUT]: [me.diabolicatrix.events.CommonEventHandler:onAttachCapability:62]: Attach Server

[16:43:24] [Netty Local Client IO #1/INFO] [sTDOUT]: [me.diabolicatrix.packets.PacketSyncCapabilities$ClientHandler:onMessage:58]: Packet Received

[16:43:24] [Client thread/INFO] [sTDOUT]: [me.diabolicatrix.events.CommonEventHandler:onAttachCapability:62]: Attach Client

Oh, that solves all my problems! I just started using forge 1.8 so I didn't know the packets were handled differently. Thanks you very much for your help.

 

 

EDIT: I tought it would work but it doesn't, the value is still overwritten by the constructor.

Where I attach it: https://github.com/DiabolicaTrix/MinecraftLifeRPG/blob/master/src/main/java/me/diabolicatrix/events/CommonEventHandler.java

 

 

My capabilities class: https://github.com/DiabolicaTrix/MinecraftLifeRPG/blob/master/src/main/java/me/diabolicatrix/other/PlayerCapabilities.java

 

 

My packet: https://github.com/DiabolicaTrix/MinecraftLifeRPG/blob/master/src/main/java/me/diabolicatrix/other/PlayerCapabilities.java And https://github.com/DiabolicaTrix/MinecraftLifeRPG/blob/master/src/main/java/me/diabolicatrix/other/ScheduledPacketTask.java

 

 

Also, how do I save it when the player disconnect?

only my sync packets are two ways? Ok, I'll try.

 

 

EDIT: It doesn't work, it does the exact same thing.

Sync should never be two way, it should only be server -> client

Thanks, it works but how do I save it when the player disconnect?

    public static class Storage implements Capability.IStorage<PlayerCapabilities>
    {


        @Override
        public NBTBase writeNBT(Capability<PlayerCapabilities> capability, PlayerCapabilities instance, EnumFacing side)
        {
            NBTTagCompound compound = new NBTTagCompound();
            
            compound.setInteger("Test", instance.getTest());
            
            return compound;
        }


        @Override
        public void readNBT(Capability<PlayerCapabilities> capability, PlayerCapabilities instance, EnumFacing side, NBTBase nbt)
        {
            NBTTagCompound compound = (NBTTagCompound) nbt;
            
            instance.setTest(compound.getInteger("Test"));
        }

    }

 

Like that? 

@Override
    public NBTTagCompound serializeNBT()
    {
        NBTTagCompound compound = new NBTTagCompound();
        compound.setInteger("Test", this.getTest());
        return compound;
    }


    @Override
    public void deserializeNBT(NBTTagCompound compound)
    {
        this.setTest(compound.getInteger("Test"));    }

I mean, do I need to call these functions from an event or something?

serialize is called but deserialize is not, do I need to call it by myself?

Well, I put a sysout in the deserialize function and it's not called.

What do you mean by "use a debugger", how do I do that?

It works, thank you very much for your help and for your tip (debugger)

No, istorgae is for the default implementation of serialization.

If youre attaching to another entitiy that is not your own and you want tonstore data, your icapapbilityprovider must implement inbtserializeable.

@diesieben07 My ResourceLocation was wrong (I used player.getUniqueID() to determine the location), I changed it to MODID + ":PLAYER_CAP" and it works fine.

 

 

@Lexmanos Thanks for the information!

Yes, the resoure location should be your mod id : some internal name you want