What is the maximum level of a character?

[lbcosta]

I'm already at level 60 and have not yet unlocked the last passive space.

[Panterich]

>> What is the maximum level of a character?
You still have a long way to go.

>> I'm already at level 60 and have not yet unlocked the last passive space.
And it will stay this way for any character level.

[Jay]

Kill the last 2 bosses then, and you will unlock the last area.

[lbcosta]

Originally posted by Panterich:

>> What is the maximum level of a character?
You still have a long way to go.

>> I'm already at level 60 and have not yet unlocked the last passive space.
And it will stay this way for any character level.

I saw that you completed all the achievements! Did you release the last space at what level?

[Niss3]

You need 8 characters with 3 skills each for achievement.

Im not sure what max level is but I would make a guess that there is no max level.

[GlassDeviant]

255, the most an unsigned integer variable can store, I expect. Unless they used a longint, which I doubt but it's possible.

[iAshZz]

Originally posted by Zombielord Ativan:

255, the most an unsigned integer variable can store, I expect. Unless they used a longint, which I doubt but it's possible.

This assumes the game is running in 8 bit... I would assume at least it runs in 32 bit meaning the largest 'unassigned' integer would be 4,294,967,295.

To this point I currently have a level 502 character with no end in sight!

[Panterich]

Originally posted by Zombielord Ativan:

255, the most an unsigned integer variable can store, I expect. Unless they used a longint, which I doubt but it's possible.

255 is max value for byte. 8bit integers were used 50 years ago.
Game uses signed 32bit integer to keep level value, so its (2^31)-1 max. However with such big level other stats will overflow and since devs are either too lazy or too incompetent to implement checkups, game will probably hang or crash as soon as some of them are used.

[GlassDeviant]

That all depends on the compiler used. Some make integers 8 bits, long integers 16 bits and so on, while others use whatever is native to the OS. And it may not be an unsigned integer, come to think of it, they could have specifically made it a single byte variable. Or there could be a hard cap assigned regardless of the variable type used.

I can't imagine going to 500+ levels, the grind is bad enough as it is and I've started a new save file to test some theories, since there is nothing to do with the endless mats once you've upgraded the magic shop to tier 3.

What level is your endless dungeon at?

[Panterich]

Originally posted by Zombielord Ativan:

That all depends on the compiler used. Some make integers 8 bits, long integers 16 bits and so on

That is illogical and unproductive. There is zero sense in making 8bit integer on a non 8bit cpu architecture. Can you provide a modern example excluding the case when you do a manual override?

What actually does happen, is that an integer without length specification may become 16, 32 or 64 bit withing the current gaming PC systems. And i would be surprised finding 16bit integer within anything compiled in the last 10 years.

[GlassDeviant]

I am not aware of a specific one, but I can think of a reason why you would do it. Say you specifically want a variable to wrap at 255 (or 127 for unsigned) and your compiler doesn't have a byte variable type, or to provide a convenient limitation (without wrapping) on a value without having to write special code to enforce it. Not the cleanest solution, but sometimes quick and dirty is all you have time for. The code to do that in a 2-byte variable would be a huge waste.

I'm not saying it's a good solution in any way, just that it happens. I've seen MUCH worse things done in the name of expediency, and not only on games. Regardless, we're getting way off topic here.

[Panterich]

Originally posted by Zombielord Ativan:

I am not aware of a specific one, but I can think of a reason why you would do it. Say you specifically want a variable to wrap at 255 (or 127 for unsigned) and your compiler doesn't have a byte variable type, or to provide a convenient limitation (without wrapping) on a value without having to write special code to enforce it. Not the cleanest solution, but sometimes quick and dirty is all you have time for. The code to do that in a 2-byte variable would be a huge waste.

That is exacly how you should not do it. That is not any kind of solution. You can`t limit or wrap this way (or any other way without writing special code to enforce it). Incrementing "FF" by 1 will always result in "01 00" and bitlength does nothing there. Best case scenario - that is your own memory space you are corrupting. Worst case - access violation exception.

Originally posted by Zombielord Ativan:

I've seen MUCH worse things done in the name of expediency, and not only on games. Regardless, we're getting way off topic here.

That is probably why SOHO router firmwares are not secure by default. Regardless, i do not see any real topic there. A lot of answers to OP were already given in many other topics.