Originally Posted by
ProHackBot999
If anyone decides to do the horrible idea of making leveling super easy and quantitative (ie 200 god kills = level 9 000 000 000 000), there is a possible way to enumerate the level value much, much higher than Int32.MaxValue ...
Without going into too much detail, every time one's level value exceeds Int32.MaxValue, it regroups over to a second integer value that would act as "the next place value", and the integer value would simply be named with a numeric value. When this is done as a function, the end max level value would be something like...
Code:
10Int32.MaxValue x Int32.MaxValue
This is possible because the level value would be held by multiple integers instead of just one. And one can go even further if I'm correct if they apply the function to our current function by regrouping the storage integers and making new ones... (by then it'd get pretty crazy with naming)
Code:
10Int32.MaxValue x Int32.MaxValuey
y = number of times you repeat the function
I'm not too sure of the storage problems this would create as I'm not sure how many bytes that Int32.MaxValue of integers each with Int32.MaxValue as a value would take in total.
If you were to display these ungodly values in a client, you might want to switch to scientific notation or a logarithmic function. I'm not too sure if this is the best way of going beyond the max value of an integer, but it ideologically works.
Code:
decimal.MaxValue (79,228,162,514,264,337,593,543,950,335)