Ducat overflow bug

I wish to know how it works. Someone PM me the details. You want something in return? Work it out with me over PM.

That'll depend on what you can give in return

In KOR client, this occured RANDOMLY.

and already patched (...some of users are banned and all of overflowed ducats are removed).

If devCAT is stupid enough to apply Ducat system with this 'Glitch' not patched,
This will work:


Make your ducat '-1'
then, because ducat is 'Unsigned Long' type variable, it'll be 4294967295(FFFFFFFF).


However, Buy more than my budget to make negative ducat is never worked for me.
It always crashed my client.

Quote:

Originally Posted by kcy1019 In KOR client, this occured RANDOMLY. and already patched (...some of users are banned and all of overflowed ducats are removed). If devCAT is stupid enough to apply Ducat system with this 'Glitch' not patched, This will work: Make your ducat '-1' then, because ducat is 'Unsigned Long' type variable, it'll be 4294967295(FFFFFFFF). However, Buy more than my budget to make negative ducat is never worked for me. It always crashed my client.

You don't have to explain just what an overflow error is.

So you mean to say this is totally random, implying it can't be controlled, yet people were being banned for it?

And how are you even accomplishing making the client crash? You're not trying to memory edit your client's Ducat reading or something are you? Because that isn't going to accomplish anything. Neither is trying to force purchase of more product than you have Ducats, as there is a server side check.

Now, I'm not entirely convinced this bug exists just yet, but there were multiple king maces being sold by a single player on Alexina on day 1, lending pretty heavily to proof of it's existence on NA servers.



As a side note, if I'm offering source code to Potato, and help with getting a working dev enviroment set up for those who want to make their own pake mods, or I can do the grunt work, just tell me what you want it to do, assuming it's possible.

Hit me up with the source code to potato.

Quote:

Originally Posted by Misdirection You don't have to explain just what an overflow error is. So you mean to say this is totally random, implying it can't be controlled, yet people were being banned for it? And how are you even accomplishing making the client crash? You're not trying to memory edit your client's Ducat reading or something are you? Because that isn't going to accomplish anything. Neither is trying to force purchase of more product than you have Ducats, as there is a server side check. Now, I'm not entirely convinced this bug exists just yet, but there were multiple king maces being sold by a single player on Alexina on day 1, lending pretty heavily to proof of it's existence on NA servers.

Simply,
I edited pleione and standard to ignore error messages and sent the buying packet.
then crashed..

and What I posted is just a 'fact'.

LF>secret to registering at dedrain

wat secret

I figured there was a secret, after a hundred times of trying I keep getting an error saying that I typed the verification code incorrectly. :/

It's spambot counter measures. I didn't add a question to the registration.

Anyways, if you need help with pake, you can do it without an account. Dunno why you need one.

Dan, PM.

I don't get it, it's just a lame sign up, that you don't really need.....

It's a useless forum...

It works, i found a video of it. Pm for it

Quick fact : yesterday, I got dc'ed for maintenance after selling good at tara. Today I login, and I see that I'm still having my cart full. And I still have my full ducat too. So I sell it again.

There might be something to do with this... (god couldn't be any clearer than that)

Quote:

Originally Posted by goldencoolsam Quick fact : yesterday, I got dc'ed for maintenance after selling good at tara. Today I login, and I see that I'm still having my cart full. And I still have my full ducat too. So I sell it again. There might be something to do with this... (god couldn't be any clearer than that)

Hopefully this maintenance didn't patch it... Anyone get it working since maint ended?