hey guys,

 

this has always been in the back of my mind. Do u guys thing that they have a billion gp category. Like u know how when u have 10000k that becomes 10M. Well if u had 10000M would that become like 10Bil..? Does ne1 in the game even have that much cash!?! That would be insane. Another thing i hav thought about is u know how in the trade screen--1M turns blue--would a billion gp turn a differnt color?? those are all might money questions. Think about them or come up with ur own questions

The cap is 2.1 bil. (2100 Mil)

whoaa...really??..how did u stumble upon this bit of information?

Didn't someone get that much and then it dissapeared... That's what my friend said anyways..

whoaa...really??..how did u stumble upon this bit of information?

 

You learn a lot of things in Tip.It Forums.

u know how in the trade screen--1M turns blue--

 

 

 

 

 

I seem to remember 1Mil turning green on the trade screen.

The cap is 2.1 bil. (2100 Mil)

 

 

 

 

 

Sorry to disagree, but I think it's 2.3.

 

 

 

Issy.

The cap is 2.1 bil. (2100 Mil)

 

 

 

 

 

Sorry to disagree, but I think it's 2.3.

 

 

 

Issy.

 

Its 2.1 :mrgreen:

The cap is 2.1 bil. (2100 Mil)

 

 

 

I second that. Atleast I'm fairly sure it was 2.1 billion. How do we know? I'm not sure who it was, but I do believe 1 person tried to deposit billions of gp into there bank and only 2.1 billion went in. The rest of it dissappeared.

 

 

 

Something of that sort. Not sure of the real story. Perhaps I'm completely wrong and a Jagex staff member told us?

There was a very detailed post about the GP cap that I remembered reading. It was quite interesting. Here's two links to specific posts within that topic. (I'll quote the highlights for those that can't be bothered to go to the links. :P) The first one explains why it's capped at 2.1B and the second explains why the gp would not disappear but turn the stack negative (-2.1B instead).

 

 

 

http://forum.tip.it/viewtopic.php?p=2771382#2771382

 

 

 

The PROBLEM is surely within the database that stores the user records. GP is stored as a 32bit signed int (2.1B = 2^31 - 1). The concern isn't space. We could possibly convert the signed int into an unsigned 32 bit int, doubling the cap. But, this really isn't a good fix. The solution is a 64 bit number.

 

 

 

The problem is size of the dataset. Millions records will have to be reorganized - and since they're probably optimized on disk to the extreme, I expect all records will have to be rewritten totally on disk.

 

 

 

Modifying tables with data isn't done lightly. Heck, it's not good to do at all. When you add in millions of records, there's a huge downtime involved.

 

 

 

Then there is an issue with speed. Doing arithmetic on 64 bit values, for the most part, is slower than 32 bit values. This is because most processor registers are 32 bits, so you can't do the work all at once. So, we have AT LEAST two times the instructions necessary for addition and subtraction, and more for division and multiplication.

 

 

 

 

http://forum.tip.it/viewtopic.php?p=3002537#3002537

 

 

 

As for the situation where the amount becomes negative after the cap, this is an effect called overflow. This is introduced by the way that computers use to handle and represent numbers in binary format. You can imagine if all numbers are placed on a wheel in ascending order. Thus the next slot equals to current slot + 1. But since the wheel is circular, if the current slot is the maximum value, then the next slot will be the minumum value. Thus you get negative value if you go past the maximum positive value. This effect is unchangeable as of now, but it can be avoided. For example, a message saying "You can't bank anymore!" can be added to stop you from getting past the cap, thus avoiding the overflow effect.

alot of games have number caps including runescape.

 

Have you ever noticed something being capped at 65535?

 

thats cause its 2 to the 16. likewise, 2 to the 32 is 17,179,869,184. Therefore i would have thought the cap would be 17 billion, it being a 32 bit system.

 

 

 

Caps are there to prevent negativity. In some old tycoon games, if you tried to construct something stupidly expensively, the cost would go so high, it would be negative and actually give you money rather than take it away. The same goes for Runescape. Plus, if you had 2.1 billion, you could always splash out on something pointless like 100 phats to lower that a bit.

2^32 is 4294967296. You're doing 2^34.

 

 

 

And as they have all said, its just how it caps it out. I don't see why it isnt capped at 4.3 bil instead of 2.1. Being as nothing in Runescape goes negative, theres no reason to have a set of negative values as it does now. Cause usually when its 2^15 or 2^31 thats cause it has a set of negative numbers as well.

;lknf4 3-3j-04it nm3knkl nw cd= is the cap number

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

jokin i dont have a clue what all this about cap is :? any1 care to explain in idiot form? (i read the post but i need a guide for idiots :-s )

2^32 is 4294967296. You're doing 2^34.

 

 

 

And as they have all said, its just how it caps it out. I don't see why it isnt capped at 4.3 bil instead of 2.1. Being as nothing in Runescape goes negative, theres no reason to have a set of negative values as it does now. Cause usually when its 2^15 or 2^31 thats cause it has a set of negative numbers as well.

 

 

 

problem is that our CPU doesn't know that and it runs with 2's compliment binary digits. it has to have negative number even if you don't use it. and range is from 2^31-1 to 2^-31. this translate to 2 147 483 648. one more coin and u get overflow :)

hmmm, i shall remember this topic once i manage to get 2.1M

 

 

 

 

 

 

 

cya in 100 years :wall:

Something for us all to look forward to. :)

 

The PROBLEM is surely within the database that stores the user records. GP is stored as a 32bit signed int (2.1B = 2^31 - 1). The concern isn't space. We could possibly convert the signed int into an unsigned 32 bit int, doubling the cap. But, this really isn't a good fix. The solution is a 64 bit number.

 

 

 

The problem is size of the dataset. Millions records will have to be reorganized - and since they're probably optimized on disk to the extreme, I expect all records will have to be rewritten totally on disk.

 

 

 

Modifying tables with data isn't done lightly. Heck, it's not good to do at all. When you add in millions of records, there's a huge downtime involved.

 

 

 

Then there is an issue with speed. Doing arithmetic on 64 bit values, for the most part, is slower than 32 bit values. This is because most processor registers are 32 bits, so you can't do the work all at once. So, we have AT LEAST two times the instructions necessary for addition and subtraction, and more for division and multiplication.

 

 

 

 

 

The part about doing arithmetic on 64 bit values is truely slower on 32 bit processors...Most servers now run on Itaniums(64 bit) or Opterons(also 64bit) so I don't foresee this being that large of an issue. The rest of the problems, however, are still problems. 8-)