BYOND has a limit on the amount of theoratical enviroments it can handle, after a certain amount of dimensions, the inter-spatial rifts break and make each environment cascade and destroy the links between each environment.

But on a serious note, i belive its around 65000 for most objects, mobs etc

Is thier a max map size?

Dark_Shadow_Ninja wrote:

Is thier a max map size?

This is a guess but i'd say 1414x1414 as that would be about 2 million turfs. Assuming byond didnt crash and you didnt have any other turfs that seems like the max or at least what the max would be

Dark_Shadow_Ninja wrote:

I think crispy might of ment how many turfs you can define.

No, he meant how many actualunique turfs you could have in the world.

I dread to think how long it would take to compile 2 million individually defined sub-classes of turf.

Last I knew, each dimension had a maximum length of 1000. So it would be more like 1000x1000x2.

There is also a 65000 limit on unique turfs. Turfs that are the same as others (all of the same type if you haven't changed any aspect of them yet) are counted as 1 for this limit. So you could have a million turfs, but if they are all the same then they will only count as 1 toward this limit.

I was going to respond to say that he meant megabytes, but how on earth does he have 20k+ megabytes. Doesn't seem that it could be too easily accomplished. Most commercial games now are around 1000Mb.

Dude, what have you been smoking on? It's nowhere near 255x255!

Loduwijk wrote:

Technically, however, I suppose you could overflow the world.time variable if you left it running for 15 years.

Actually, if world.time is a floating point number (which I think it must be, since all numbers in DM are), then it'll take quite a while to overflow! It'll get pretty inaccurate after a while (see: world.realtime), but it shouldn't overflow for a while.

According to Wikipedia, the maximum value of a single precision floating pointer number is about 3.4028234 x 10³⁸. So the maximum duration that world.time could hold would be 3.4028234 x 10³⁷ seconds, which is equivalent to about 1.07829 x 10³⁰ years. So call it 10³⁰ years.

That's a long time. =)

Though actually, now that I think about it, world.time is probably an integer internally and is just being converted to floating-point when it's accessed. So depending on the size of the integer, it could overflow after a mere few decades.

Just to expand on this: There is a "map cell" limit. Which limits the number of "unique" turfs to 65535 as well. However, most games shouldn't have a problem with this. (Most games on BYOND have a bunch of fields with a few areas of interest, not that this annoys me or anything) More advanced games, however, might run into some issues when they get into things that need to modify each individual turf in some unique way. Even so, this is really only a problem on very large-scale maps, and most of your problems with this can be alleviated by using a system such as LummoxJR's SwapMaps, which I'd highly recommend taking a look at. I've since then created my own saving/loading system, and I can basicly create worlds limited only by the size of my hard drive, they just have to be loaded and moved between dynamicly. Multi-server is another thing to consider. Right now, it's a LITTLE shaky going between servers, but I haven't really had much complaint from Bomberman Arena players (about that at least) and they have to go between servers each time they connect to a server.


All in all, BYOND has it's limits, but with some careful planning, they're quite managable.

Keep in mind that adjacent areas sort of get squashed together into one area object - so a map like this:

A A B B
A A B B

Where A is one type of area and B is another type of area, would only use two area objects, not eight.