Bind Server Capabilities & Custom GuiScreen to modify it

[Durzann]

Hi there, I'm happy to join the MCForge community today

 

I'm actually looking for creating a mod which allow players to create custom description for their character (Roleplay server), It's a complicated object, which handle several layers of description (not a simple string)

So I have my Capability classes, and i'm using a basic serializer to save it as a json string.

 

On the other side, I sucessffuly created a custom GuiScreen, with many inputs to edit the description and create new layers (But I didn't create any server/client interaction to open it.... Did I miss something ?)

 

 

But now, i'm struggling to get the next step with the server/client architecture :

 

_ What did I need to store the Capabilities on the server side (one per player), and send it to the Client to let him make some modifications (via my GuiScreen) ?

 

I Want to allow any players to right-click on another player, get his description, and make some modification on it, so what's the next things that I have to looking for ?

 

I can find detailed infos by myself, I just want to have a clear view of what I will need to make that works (And If you guys, can teach me a bit of how Client/server works, it will be great for me  )

 

 

 

Edited March 8, 2020 by Durzann

[diesieben07]

The way to do this would be to attach the capability on the client as well (same procedure applies).

Then you need to decide whether the data is needed on the client only while the GUI is open or also outside of it.

 

Only during the GUI:

Send the data to the client as part of opening the GUI (NetworkHooks#openGui allows you to write extra data to the PacketBuffer).

 

Also outside the GUI:

• You need to include Entity#getEntityId in the packets so that the client knows which player you are talking about. World#getEntityByID is the counterpart.
• You need to send the data as follows:
  • In PlayerLoggedInEvent, PlayerRespawnEvent and PlayerChangedDimensionEvent: Send the data of PlayerEvent#getPlayer to only that player.
  • In PlayerEvent.StartTracking send the data of StartTracking#getTarget (if it is a player) to PlayerEvent#getPlayer.
  • Whenever the data changes send it to the player itself and all players tracking it: see PacketDistributor.TRACKING_ENTITY_AND_SELF.

 

As for client-to-server communication: Send information about what the player does to the server and validate it properly, do not send "commands". I.e. "Player clicked button x" not "change field 123 to value 'hello'". Treat the client as a lying bastard at all times and verify things.