Greetings, glorious adventurers! If you're joining in our Alpha One spot testing, please follow the steps here to see all the latest test info on our forums and Discord!
Options
32-bit System
Jiraiya
Member, Alpha One, Adventurer
Those who have alpha one access may have seen the gold glitch where you would recieve 2,147,483,647 gold in your bag. Does it concern or worry anyone that AoC is going to be running on a 32-bit system since this is the max gold stack?
0
Comments
I feel like I have at least enough experience to label this take as 'not even wrong'.
This allocation is something Intrepid can set as they see fit, other numbers that need not be that high could be set to 8 or 16 bits, as needed.
Having things vendor for less and quests give you less gold is a step in this direction. Since nearly everything in Ashes is player made. The market will always adjust itself to the currency supply. Currency is only created from vendors and quests, so it should not be that hard to keep the numbers low and have them work.
Another possibility would be having a currency conversion system. Instead of just having gold alone have like: [Platnum, Gold, Silver, Copper]. Each being like 10x the value of the one before it in the list. This could be done in a way where the character has 4x32bit numbers to fill to reach gold cap.
I think as long as they are conservative about how large they make reward numbers, they will be fine.
If I had more time, I would write a shorter post.
They can fairly easily put a check in place so that you cant go negative.
Even if people did manage to work around it, Intrepid should have systems in place to alert them if a character all of a sudden has 2 billion gold, at which point they can investigate. Personally, I'd rather see it be 100 of each in order to equal one of the next tier up.
If we assume the base currency is copper (if we assume anything else, copper serves no purpose), a 10x system would make a platinum piece worth 1,000 copper.
A 100x system (which happens to be what most real world currencies are based on), that platinum piece is worth 1,000,000 copper.
While this may seem kind of trivial, is means that using 4 32-bit numbers, a 10x system will see the cap on a player of 2,385,854,331,817 copper, while with a 100x system, that cap is 2,169,175,379,318,350 (my math may be off, feel free to double check my numbers here).
But yeah, the general idea you have here is absolutely spot on.
(Back to the topic) No. And FYI 64 bit systems can still have 32 bit datatypes, and 32 bit systems can have 64 bit ones.
I can't remember what game it was, but I do remember playing a game where you could take a specific number of coins and melt them down to get a bar of that metal. If Ashes has a system like this, keeping each coin type separate would be key - though I doubt it will have such a system.
I totally agree with you, realistically i think that they will probably make it not even obtainable to max out. I think having more than one currency is a great solution.
This is probably what that cap is.
Does the existence of a Boolean mean we run on Boolean systems?
The reason RuneScape has that limit is because, when the game was implemented, they used the Java data type "Integer", when they obviously should've chosen "Long".
I guess they used a signed 32-bit data type in AoC because they don't think anyone will ever reach that amount of gold.
And so "why 2,147,483,647 and not the round number "2,000,000,000 ? "
as said maybe not definitiv amount. and... i think it is faster and easier to set the limit bind to how memory works than adding a line "maxmoney="