Jump to content

[1.7.10] Implementing a toggle-button in a GuiContainer


Recommended Posts

Posted

Hello, I'm looking to create a toggle-button in a GuiContainer.

 

The idea can be explained as:

- the user opens the GUI of the container, there is a button labeled 'no' there

- the user clicks on the button, the client sends a packet to the server to set a boolean to true on the server-side

- the server would send a packet back, so the GUI would set the button's label to 'yes'

(e.g. think of a 'Machine Enabled' button that can be 'yes' or 'no', perhaps).

 

Also, if a player opened the GUI, the server would have to update the button with the updated value.

 

I already have the button click sending a packet to the server (using SimpleNetworkWrapper), but how can I keep the client updated with the value?

I was intending to send the packet back, but how can I access the GUI from within the messagehandler?

 

Or, is there a better way that I should be using instead to send an update to the GUI?

 

Thank you in advance, I appreciate any pointers that I can receive for this.

Posted

I would just suggest updating the value client sided when the button is clicked, and then send the packet to the server so the server can store it. There's really no reason to send the packet back.

Posted
  On 3/15/2015 at 7:09 PM, 61352151511 said:

I would just suggest updating the value client sided when the button is clicked, and then send the packet to the server so the server can store it. There's really no reason to send the packet back.

 

That's true.

 

However, when the user opens the GUI and the value has already been changed, how can I synchronise the client in that case?

 

 

Posted
  On 3/15/2015 at 8:07 PM, shadowfacts said:

You'll need to add the state of the button to your TE's NBT and then use getDescriptionPacket to return a new S35PacketUpdateTileEntity with your NBT.

 

Thanks, that's pretty much exactly what I was looking for!

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

×
×
  • Create New...

Important Information

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