Jump to content
View in the app

A better way to browse. Learn more.

Forge Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

  • Author

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);

        }

    }

  • Author

@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.

Check out my tutorials here: http://jabelarminecraft.blogspot.com/

  • Author

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.

  • Author

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

  • Author

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

  • Author

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.

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

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

  • Author
    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"));
        }

    }

  • Author

 

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"));    }

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.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

  • Author

@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

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.