xanderindalzone

Does that run in every tick? if it does, wouldn't that be more spammy than the InputEvent that runs when the player presses any controls? I could be wrong, it's the first time I heard of ClientTickEvent XD

Ok so I've now finished the packet implementation, its working as expected but I wanted to know your thoughts to know if its fine. Mod class packet handler registration PacketHandler: Client-Side Event: Message Class: Gun Reload Method:

Thx a lot This is my first time with packets anyway XD, I'll give it a try this afternoon. Yeah, I'm aware of this, I just needed the message class.

After reading a few posts and wikis etc etc, I started with the packet thing, but when I tried to make the Message class, it appears I cant implement from IMessage. Is this a bug? or does this interface doesnt exist anymore?

Previously I was calling the key variable from 2 places: 1.A client event from the client-side only event-handler like you said now. 2.A private method (reload) in the Gun class. I guess I'll have to make that reload method (2.) an event in the same event-handler as (1.), right?

I believe I have to put some sort of annotation on top of the class/variable to specify its only a client class/variable. But from what I read from the Javadoc, this wouldn't work with initializers I think, right? What do I have to put to specify that this class/variable only runs in client, if this isn't it? Or no annotation at all, like you said here?

I had this before in the mod class... but diesieben07 told me that KeyBinding was a Client-Only class so I removed it.

I just have this left to do to fix Client-Side Only issues i think. I've directly created the KeyBinding object inside the register method in the client event, also removing the static init I had, but now I cannot access the key from outside to check for example, if that key is being pressed. Is there a way to check that key status? or a better way to register the key without violating the Client-Side Only code thing, and being able to access it by other methods?

I've been a bit busy this weekend but now I'm working with the mod again.... Is this the proper way of registering stuff now? This is what I saw in a DeferredRegister tutorial. I asume the way to access the Objects in code is with "InitItems.BULLET_CAL_45.get()" because it's at least working normally. But correct me if i'm wrong.

I had it previously in FMLCommonSetupEvent. So...... FMLClientSetupEvent is only ran in client-side, right? so its safe to put the glass code there, right?

If there's a way of doing it once in a Client-Only event, I'm open for suggestions

I've done 2, 3 and 4 from the list atm, but I dont know if this alternative for the transparent glass is appropiate.

Thank you for taking your time to analize my code, I'll start fixing stuff when I have a moment.

Also, have this in mind, I have custom key settings for my minecraft, so the mod keybinding "R" is not actually my current reload Key(but it is R by default) it currently just says "Press R to Reload" in the message when the gun has no ammo because thats the default key of that new KeyBinding.

my bad, it should be public now