What exactly holds back the bricklimit?

[Crøwn]

There isn't a brick limit really now.

[Ad Bot]

[Ipquarx]

There isn't a brick limit really now.

You can only ghost so many before you hit a hard-coded limit.

[Kalphiter]

you can go over the brick limit, its just once you get like ~400k bricks stop rendering.

Although it doesn't explain why, it's right. Everyone else in this thread is wrong.

The ghostIDs are transmitted using 17bits.  2^17 = 131072 ghosted objects at a time.  Due to bugs in the ghosting code, if you have more objects than that, you may have problems like not seeing other people or not being able to respawn.  Even if it works perfectly, you won't be able to save everything at once from the client because not all of the server's objects will be represented on your client.

I have no idea what Badspot did to make it increase.

[Hectic II]

If I recall correctly, badspot said if people start hitting the brick limit, he'll raise the limit on bricks. Anyone else remember that?

[Crøwn]

If I recall correctly, badspot said if people start hitting the brick limit, he'll raise the limit on bricks. Anyone else remember that?

you can set the brick count limit now.

[Doomonkey]

I have no idea what Badspot did to make it increase.

Another bit changes 131072 into 262144.

[YourBuddyBill]

Another bit changes 131072 into 262144.

And there we have it.