How many layers can be in a ROS?

[pallid tusk]

Just saw this shape (SwSwSwSw:WrWrWrWr:CrCrCrCr:WbWbWbWb:CwCwCwCw) as my operator level shape. It has 5 layers. I thought we were limited to 4 layers! How many layers can be in a ROS? Asking for a friend who's making a MAM. 🙂

[bronze hearth]

there can be as many layers as the current scenario allows (5 in insane, 4 otherwise)

[pallid tusk]

Thanks! As I thought about this, given the way stackers work, there really is no actual limit (other than MAX_INT) to how many layers a ROS could be. Which had me really sweating about how many squares, circles, etc I was going to have to collect to feed my MAM. LOL

[severe sage]

The world map is infinite, right? /jk

[devout kernel]

I’m confused by MAX_INT. Is this an actual variable the devs use? Or are you just a creative individual

[severe sage]

It's a bit of programming terminology, it's just the largest number a computer can store in the 1s and 0s available to it without extra fancy code

[devout kernel]

Oh, so what he was saying was a joke. Got it

[pallid tusk]

Chuckle, one of the devs used the term MAX_INT recently and I remember thinking "Its a good thing I'm a programmer and understood that." But of course when I use it, I confuse people. 😛

[devout kernel]

I’m a programmer. But that doesn’t mean I know what MAX_INT means for this game.

You’re talking about a variable that is not defined. Which means that it means nothing

[graceful charm]

MAX_INT isn't a variable here, it's a short for Maximum Int, which is 2^31-1

[fickle yoke]

…no…
MAX_INT is a constant, it’s the maximum integer before under/overflow

[fickle yoke]

Integers have a storing limit

[fickle yoke]

(Int = Integer btw)

[devout kernel]

I understand what MAX_INT is generally speaking from a programming pov.

What I don’t understand is MAX_INT on shape layers. This is my point

[fickle yoke]

that there could be MAX_INT layers on a shape (i think)

[devout kernel]

That would be a different variable specifically not called MAX_INT. Again, I feel like I’m just repeating myself at this point.

The terms MAX_INT and Shape layer limit are two completely different things. And since we are talking about layer limit, therefore MAX_INT is incorrect.

Which is why I said earlier that I didn’t understand why it was being used, and then briefly after that I thought the person who used that term was joking (for obvious reasons).

[pallid tusk]

MAX_INT is a constant defined in the default libraries of many popular programming languages like C++, Java, Python, etc. It is so prevalent that most programmers assume that it, or some variation of it, will always be present in any language. As such it somewhat transcends any particular language.

[devout kernel]

Why are you telling me this? lol are you one of those AI bots?

[devout kernel]

I genuinely am asking

[pallid tusk]

Because you seemed to be quite confused about what/where MAX_INT comes from?

[devout kernel]

Nope, I’m genuinely confused about why you are using the term in this context.

Could you explain how MAX_LAYER and MAX_INT are related? Thanks

[pallid tusk]

MAX_INT is a generic programming term. It exists outside the domain of Shapez 2.

MAX_LAYER is a term that I don't see in this thread before you asked about it. However, I believe most programmers would assume MAX_LAYER represents the maximum number of layers that could exist in a constructed shape.

In the context of the early discussion in this thread: If MAX_LAYER were equal to MAX_INT (a VERY big number), then constructing that shape would be outrageously difficult. The comparison was tongue-in-cheek, expressing my relief that there was a very small and limited number of layers that could be in a shape.