Negative mesos fix. (command)

Quote:

---

Originally Posted by GoldenKevin

You guys are idiots, it's impossible to get more than 2147483347 mesos.

---

What, everybody here knows.

Quote:

---

Originally Posted by GoldenKevin

You guys are idiots, it's impossible to get more than 2147483347 mesos.

---

It was possible if you played like in v55

Quote:

---

Originally Posted by SirDanielot

Its acually in math term 'Less than' XD

---

I didn't know "less than" was a math term... ?

Quote:

---

Originally Posted by kevintjuh93

Can anyone explain me how someone can fking get negative mesos? It shouldn't even be possible to get negative mesos. And MapleStory cannot write negative mesos lol. I've never seen negative mesos when opening my Inventory. If I receive negative mesos it would start at max mesos. That's how people hack mesos ...

---

Wondering the exact same really, I don't get how people don't have a check in gainMeso.

Quote:

---

Originally Posted by Carrino

After adding these, update message will show everytime when they enters a new map, login, and so on.

v75

Code:

---

PLAYER_UPDATE = 0xD5

---

Handler

Code:

---

package net.channel.handler;

import client.MapleClient;
import net.AbstractMaplePacketHandler;
import org.slf4j.LoggerFactory;
import tools.data.input.SeekableLittleEndianAccessor;

public final class PlayerUpdateHandler extends AbstractMaplePacketHandler {
    private final static org.slf4j.Logger log = LoggerFactory.getLogger(PlayerUpdateHandler.class);
    public final void handlePacket(SeekableLittleEndianAccessor slea, MapleClient c) {
    try {
        c.getPlayer().saveToDB(true);
        log.info("LezDev : Player's data saved : " + c.getPlayer().getName());
    } catch (Exception e) {
      log.info("LezDev : Error caught when saving - " + e);
      }
  }
}

---

Okay, the code explains everything.

I don't actually need to read anything from it, since I don't need any data.

kabooom.

---

LOL savetodb? :w00t:

Quote:

---

Originally Posted by GoldenKevin

You guys are idiots, it's impossible to get more than 2147483347 mesos.

---

actually, if you made mesos into a long... =O
I think it would just show as negative though, yet still continue increasing.

@carrino: good idea to save players when they just logged in.
your way will reduce cpu&memory&harddisk usage alot.

Quote:

---

Originally Posted by buya

@carrino: good idea to save players when they just logged in.
your way will reduce cpu&memory&harddisk usage alot.

---

I know it long ago before adding in, but in order to prevent rollback and suchs, I choose to do this way.

Quote:

---

Originally Posted by buya

@carrino: good idea to save players when they just logged in.
your way will reduce cpu&memory&harddisk usage alot.

---

What lol? It'll constantly send queries, that's what will happend.

This was release a long time ago...

It's not "gaining" mesos. You all fails at thinking.

And yeah, if I can recall correctly, all public source doesn't have this "patched", you can get negative mesos.

I say Nexon failed for making the storage variable for mesos a signed value in the first place, but that's just me.

Quote:

---

Originally Posted by Zygon

I say Nexon failed for making the storage variable for mesos a signed value in the first place, but that's just me.

---

Yeah, it would be really nice from NEXON to make it unsigned, knowing that. mesos - amount < 0 as being unsigned will always be false.

You first need to know what you're talking about before posting, just saying.

Quote:

---

Originally Posted by XxОsirisxX

Yeah, it would be really nice from NEXON to make it unsigned, knowing that. mesos - amount < 0 as being unsigned will always be false.

You first need to know what you're talking about before posting, just saying.

---

You should take your own advice Osi. You assign a higher primitive type for storage (such as a long) on the server (if your engine is Java-based) if they did have it that way, or you could ditch Java and go with a .NET language and have unsigned values.

har har

if (getMesos() < 0) {
setMesos(0);
}

Quote:

---

Originally Posted by Zygon

You should take your own advice Osi. You assign a higher primitive type for storage (such as a long) on the server (if your engine is Java-based) if they did have it that way, or you could ditch Java and go with a .NET language and have unsigned values.

---

Ermm Zygon, that post made not sense at all. You SHOULD know by fact why you have to use a higher data type for unsigned in this case.

Java doesn't support unsigned and believe me, I have researched about this subject way more than what have you read about java at all. So, don't come with shits like "You should take your own advise", what you said makes not really a difference at all, that's the only way around when dealing with unsigned values at a C++ client and using a non-supported-unsigned language in the server.

Don't change subjects by the way, since what you said was really far from what I said.

Let's go back to what you said, why don't you create a Java client, so you don't use what the STUPID NEXON CODERS used, the unsigned values.

Quote:

---

Originally Posted by XxОsirisxX

Ermm Zygon, that post made not sense at all. You SHOULD know by fact why you have to use a higher data type for unsigned in this case.

---

Errr Osi, most of your post is just a re-iteration of mine.
Let me google that for you
First link...

Quote:

---

Originally Posted by XxОsirisxX

Java doesn't support unsigned and believe me, I have researched about this subject way more than what have you read about java at all.

---

Actually, if you knew anything, you can add support for that if you actually knew where to look. You would write it in C, and we both know you can't write C, so GG. Wait, so you've read over 1000+ pages of information on just unsigned values? That's really sad you would waste your time on such a subject that could be covered in little under a page.

Quote:

---

Originally Posted by XxOsirisxX

So, don't come with shits like "You should take your own advise",

---

No, you.

Quote:

---

Originally Posted by XxOsirisxX

what you said makes not really a difference at all, that's the only way around when dealing with unsigned values at a C++ client and using a non-supported-unsigned language in the server.

---

Way to re-iterate my post... *head desk*

Quote:

---

Originally Posted by XxОsirisxX

Don't change subjects by the way, since what you said was really far from what I said.

---

I wasn't changing the subject. My post was just saying what you would do if they did change it to unsigned in the client, please learn to read more carefully.

Quote:

---

Originally Posted by XxОsirisxX

Let's go back to what you said, why don't you create a Java client, so you don't use what the STUPID NEXON CODERS used, the unsigned values.

---

You give me a wz manipulation library in Java and I will make you one, kthxbai.

Quote:

---

Originally Posted by Zygon

Errr Osi, most of your post is just a re-iteration of mine.
Let me google that for you
First link...


Actually, if you knew anything, you can add support for that if you actually knew where to look. You would write it in C, and we both know you can't write C, so GG. Wait, so you've read over 1000+ pages of information on just unsigned values? That's really sad you would waste your time on such a subject that could be covered in little under a page.


No, you.


Way to re-iterate my post... *head desk*


I wasn't changing the subject. My post was just saying what you would do if they did change it to unsigned in the client, please learn to read more carefully.


You give me a wz manipulation library in Java and I will make you one, kthxbai.

---

re-iteration of yours? HA!

Just for your information, before going into Java, I were into C/C++. Then again, this subject is not about coding language, this is about unsigned values. And yeah, I may waste my time looking for it (actually, no), just like I'm doing right now trying to prove you wrong again.

This whole subject became because you failed with unsigned values, implying that NEXON should make mesos unsigned (Which may never works, unless you add 2 variables in the method).

Then, you came to me and said that I should take my own advise which was "You first need to know what you're talking about before posting". In that post, I did and proved. But you changed the subject to "You can use a higher primitive data type if you're using Java and the data sent by client is unsigned" (Which is something that I know by fact, and really off-topic) and also "You could ditch Java and go to .NET then".

You can say anything you wants Zygon, but that's really a subject change right there.

"I wasn't changing the subject.". Yes, you did..

I re-iterated your post? Looks like you're just putting up craps without thinking before posting again.

Seriously, take my advise.