Housing sucks rn!

[Shibi]

I would be in favor of larger apartments.

I do agree.

Outside of diskspace - which should be solvable - I sort of find it nonsensical that the internal layout can't be switched at the door to any of the other standard interiors. A small house interior should - in any system design I think of - be able to be put behind the door of an apartment. Same with medium and large insides, they should be able to fit behind the apartment door.

Outside of diskspace, there would be a database entry for the layout and internal wall type and some coding required to allow the player to select the internal walls and layout but SE are surely smart enough to do this.

Honestly, it would be awesome to allow any door to have any of the internals, to the point of one could have a large external with a medium sized layout internal, or an apartment with a large layout behind the door. Bonus points for SE if they add in more than the 4 internal layouts and/or a tenants system too.

But I guess, apart from them not wanting too, what happens if everyone with an apartment switched to medium and jumped from 100 objects to 300 objects in terms of space and backup time? Still, it's not a unique problem, I've worked on mission critical systems with petabytes of data and we managed with zero downtime outside of major patches.

[GeminiReed]

But I guess, apart from them not wanting too, what happens if everyone with an apartment switched to medium and jumped from 100 objects to 300 objects in terms of space and backup time? Still, it's not a unique problem, I've worked on mission critical systems with petabytes of data and we managed with zero downtime outside of major patches.

A bit of napkin math. Complete SWAG because I don't know how talented their data designers are or are not.

- placeable id: 4 bytes
- posittion (x,y,z): 6 bytes (3 half-floats)
- rotation: 2 bytes (another half-float)
- dye: 2 bytes (just in case)

14 bytes per object. At 200 extra objects that's an additional 280 bytes per interior. Assuming the 21,600 figure is correct for number of apartments per world the additional storage budget would be a whopping 6Mb per server.

*hands a quarter to Square* keep the change.

[Silverbane]

A bit of napkin math. Complete SWAG because I don't know how talented their data designers are or are not.

- placeable id: 4 bytes
- posittion (x,y,z): 6 bytes (3 half-floats)
- rotation: 2 bytes (another half-float)
- dye: 2 bytes (just in case)

14 bytes per object. At 200 extra objects that's an additional 2802800 bytes per interior. Assuming the 21,600 figure is correct for number of apartments per world the additional storage budget would be a whopping 6Mb60MB per server.

*hands a quarter to Square* keep the change.

I fixed some simple math errors in your post.