[SOLVED] GUI not updating values

[sham1]

  On 6/10/2016 at 9:26 PM, Melonslise said:

  Quote

  Quote

  Quote

This is not a tutorial on how to use the debugger. Google will help you.

The debugger just allows you to modify code in real time. I don't really understand how that would help me determine if the packets are received.

 

While hotswapping is possible via a debugger, the thing what diesieben probably wants you to do is have a breakpoint in the method that is supposed to be called in the client side, from context I assume onMessage. You check that the values are correct, and if they are not, fix your code until they are.

 

But doesn't a breakpoint just skip a part of code? How would that help?

 

Nope. What a breakpoint does is that it tells your debugger to stop on the line marked by the debugger. Thereafter you can do things such as single-step through your code and inspect variables and their values.

 

A quick google search on your part would have saved me the effort of having to explain breakpoints.

[Melonslise]

  On 6/10/2016 at 9:27 PM, diesieben07 said:

A breakpoint stops execution at that point and let's you inspect the values of local variables and fields while the code is paused.

 

 

I don't understand how to examine the variables from here. I can't find any proper tutorial

[sham1]

  On 6/10/2016 at 9:38 PM, Melonslise said:

  Quote

A breakpoint stops execution at that point and let's you inspect the values of local variables and fields while the code is paused.

 

 

I don't understand how to examine the variables from here. I can't find any proper tutorial

 

Which line did you put your breakpoint at.

[Ernio]

* Grabs a rope *

 

Remember that statement about "you are too lazy to learn this shit" - yeah, kinda comes together. Just google java tutorial (official) go step by step with code examples, then go to eclipse usage tutorials (including debugger) and learn that shit - only then - start modding.

 

Aside from that - you can just print to console (System.out) to check if onMessage is being called.

 

Seriously - this is like first thing you learn in java. Just because you "had a  little pascal" or other shit in school doesn't mean you are remotely close to being modder. You need EXTENSIVE java knowledge to write anything beyond basic. Right now you are questioning us on totally basic logical concepts on (spoiler alert) MODDER SUPPORT - which you are not.

 

I am surprised you haven't been burned to death yet

 

For you own good (and our sake) please - do some few-days course on java and working in IDEs. >.<

 

Question like that (longest thread in weeks about basic stuff) won't stop if you won't actually learn something.

[Melonslise]

  On 6/10/2016 at 9:48 PM, Ernio said:

* Grabs a rope *

 

Remember that statement about "you are too lazy to learn this shit" - yeah, kinda comes together. Just google java tutorial (official) go step by step with code examples, then go to eclipse usage tutorials (including debugger) and learn that shit - only then - start modding.

 

Aside from that - you can just print to console (System.out) to check if onMessage is being called.

 

Seriously - this is like first thing you learn in java. Just because you "had a  little pascal" or other shit in school doesn't mean you are remotely close to being modder. You need EXTENSIVE java knowledge to write anything beyond basic. Right now you are questioning us on totally basic logical concepts on (spoiler alert) MODDER SUPPORT - which you are not.

 

I am surprised you haven't been burned to death yet

 

For you own good (and our sake) please - do some few-days course on java and working in IDEs. >.<

 

Question like that (longest thread in weeks about basic stuff) won't stop if you won't actually learn something.

 

Hey don't rage. When this thing with the GUI will be solved I will (probably/hopefully) not show my face around here again

[sham1]

  On 6/10/2016 at 9:58 PM, Melonslise said:

  Quote

* Grabs a rope *

 

Remember that statement about "you are too lazy to learn this shit" - yeah, kinda comes together. Just google java tutorial (official) go step by step with code examples, then go to eclipse usage tutorials (including debugger) and learn that shit - only then - start modding.

 

Aside from that - you can just print to console (System.out) to check if onMessage is being called.

 

Seriously - this is like first thing you learn in java. Just because you "had a  little pascal" or other shit in school doesn't mean you are remotely close to being modder. You need EXTENSIVE java knowledge to write anything beyond basic. Right now you are questioning us on totally basic logical concepts on (spoiler alert) MODDER SUPPORT - which you are not.

 

I am surprised you haven't been burned to death yet

 

For you own good (and our sake) please - do some few-days course on java and working in IDEs. >.<

 

Question like that (longest thread in weeks about basic stuff) won't stop if you won't actually learn something.

 

Hey don't rage. When this thing with the GUI will be solved I will (probably/hopefully) not show my face around here again

 

The fact that you cannot even Google for some of these things properly kind of tells that you are not ready to mod.

 

You know what, Go through this, and then try modding again. It will teach you the absolute basics about java, and the most basic things you need in modding. That plus learning to Google should be your next objective if you want to continue this exercise. We would not want to be mean to you, but you are not exactly helping with that.

[Melonslise]

  On 6/10/2016 at 10:06 PM, sham1 said:

 

The fact that you cannot even Google for some of these things properly kind of tells that you are not ready to mod.

 

You know what, Go through this, and then try modding again. It will teach you the absolute basics about java, and the most basic things you need in modding. That plus learning to Google should be your next objective if you want to continue this exercise. We would not want to be mean to you, but you are not exactly helping with that.

 

Will do, but let's just finish what we started.

 

  Quote

Seriously?

First result on google for "eclipse debugger tutorial": http://www.vogella.com/tutorials/EclipseDebugging/article.html

 

 

It seems that the packet is being received because the value of 'amount' is 30.

[Melonslise]

  On 6/10/2016 at 10:21 PM, diesieben07 said:

And is the value still there in the GUI?

 

Well it certainly draws "30/30"

 

I updated the GUI and added two ints.

	int currentMana = props.getCurrentMana();
	int maxMana = props.getMaxMana();

	mc.fontRenderer.drawStringWithShadow("§1" + currentMana + "/" + maxMana, 2, 2, 1)

 

and here's the debug:

 

 

It seems that they are still there

 

[Melonslise]

  On 6/10/2016 at 10:38 PM, diesieben07 said:

What is your issue then?!

There are no updates. As in when the mana decreases the GUI does not follow. It stays at 30/30. e.g. an item is used with consume mana.

[sham1]

I went through your Github repository, and nowhere do I see any mana consumption in any of your items.

[Melonslise]

  On 6/10/2016 at 10:44 PM, diesieben07 said:

And you are sure the values are updated on the server? And the server sends packets with the updated values?

I'm sure that they are updated on the server since I set up prints like this in the item:

			ManaProperties props = ManaProperties.get(player);

			if (props.consumeMana(15))
			{
				System.out.println("Player had enough mana. Do something awesome!");
			}
			else
			{
				System.out.println("Player ran out of mana. Sad face.");
				props.replenishMana();
			}

 

and they are displayed correctly.

 

And as you can see in the repo all mana modifying methods have syncMana which sends packets. I have no idea why the GUI is not updated

 

  Quote

I went through your Github repository, and nowhere do I see any mana consumption in any of your items.

 

ItemScrollFirebolt

[sham1]

And while answering to diesieb above, answer me this. Why do you sync max mana and current mana in different packets. Why not just use one packet.

[Melonslise]

  On 6/10/2016 at 10:50 PM, diesieben07 said:

You did not answer either of my questions.

Not sure if that's what you meant, but I set up a print in the IEEP under the cosumeMana()

public boolean consumeMana(int amount)
{
	if(this.currentMana >= amount)
	{
		this.setCurrentMana(this.currentMana - amount);
		System.out.println(currentMana);
		return true;
	}
	else
	{
		return false;
	}
}

 

seems to be working correctly

 

(I'm not updating the repo rn)

[Melonslise]

  On 6/10/2016 at 11:24 PM, diesieben07 said:

And then the packet with the updated value arrives on the client?

 

Well obviously because I have already debugged that.

 

EDIT: Actually I didn't debug the updated value. I'll check that tomorrow (don't have time right now)

[Draco18s]

  On 6/10/2016 at 5:28 PM, Melonslise said:

I have 2 packets because I don't know how  to store 2 variables in one packet (I know I am retarded).

 

Holy fuck.  It's exactly like sending a packet with one variable, except there are two variables.

[Melonslise]

  On 6/10/2016 at 11:24 PM, diesieben07 said:

And then the packet with the updated value arrives on the client?

Aright, I set up this print in the handler for the message:

@Override
public IMessage onMessage(CurrentManaMessage message, MessageContext ctx) 
{
	EntityPlayer player = RunicInscription.proxy.getClientPlayer();

	int amount = message.getCurrentMana();

	System.out.println(amount);

	ManaProperties props = ManaProperties.get((EntityPlayer) player);

	props.get(player).setCurrentMana(amount);


	return null;
}

 

It seems that the correct values are coming through. I still don't understand why the GUI is not picking up the values.

[Ernio]

Just to end this thread I can help you via TeamViewer - debugging from github/source is kinda pointless (something is being missed here).

If you want that help send connection info here or on Skype: ernio333

 

Seriously, this thread will otherwise continue for next 4 pages and it alredy took exponentially more time (mine and others) than time needed to just do it myself.

[Ernio]

Follow-up:

 

Main reason was he fucked up getCurrentMana() which returned this.maxMana.

Other than that - a lot of global mistakes and conventional miss-doings - everything fixed.

 

Shit... should have done it yesterday.

 

I guess solved.

[Melonslise]

Thanks to everyone who helped (especially Ernio).

 

I can't believe it. Such a stupid mistake.