Blockland Forums > Suggestions & Requests
Brick limit
Ephialtes:
--- Quote from: mctwist on March 08, 2010, 09:24:14 AM ---If you are no fancy of my idea, then you come with something better.
--- End quote ---
I don't even understand why you're telling us your "idea" - nobody asked for it and it doesn't solve any sort of problem that anyone's mentioned.
--- Quote from: mctwist on March 06, 2010, 02:11:54 PM ---
--- Quote from: Badspot on March 06, 2010, 01:05:04 PM ---I'd like to point out that the ability to get to the 128k limit without running out of ram is a relatively recent development. How quickly such things are taken for granted.
--- End quote ---
I know that you don't want to change in the engine, but I think there is a way of fixing this.
--- End quote ---
Fixing what?
-Jetz-:
--- Quote from: mctwist on March 08, 2010, 09:24:14 AM ---Even if dedicated servers could have a higher brick limit, the client still have to see those bricks.
To fix more problems on my idea, the client have the original limit on 128k bricks, but when it reaches it, it moves brick from RAM to HDD that is out of sight. If bricks are removed, it takes the closest brick and fetches it back from HDD to RAM. If some bricks come in sight, and others are out of sight, it makes the same swap as above.
When it saves, it takes bricks from both RAM and HDD and merges them together to the file it saves to. (Ouch for events and owners)
If you are no fancy of my idea, then you come with something better.
--- End quote ---
What happens when we get a bunch of new bricks in sight, but we don't have any that have moved out of sight?
Deathwishez:
I know you can go beyond the limit in offline mode.
Although, there was this one time where my friend had a messed up creep mod. It would add to the brick count, but not subtract once you killed the creep. Blockland said his emtpy server had over 800,000 bricks.
mctwist:
Rephrasing:
This is used to increase the possibility to have more bricks on a server and the client may still receive and see them. In this case dodge the brick limit of 128k.
A dedicated server stores bricks on the HDD if it reaches the brick limit. HDD is still faster than an internet connection, so having a dedicated server with 1 Gbit/s upload wouldn't help if the HDD have 3Gbit/s(As I assume most dedicated servers have).
The client receive all bricks from the server. If it reached the brick limit, it caches it on the HDD depending on the distance from the client. If the limit is reached within a certain area, you are not allowed to build there. This area is the closest bricks in a radius from the brick you plant. When the client moves through the server, bricks that will be in sight are fetched from the HDD and those out of sight cached to the HDD.
This does also means that if you teleport from one place to an another, first time you will load the bricks. Next time it will also load the bricks, but do it a lot faster, or not even noticeable.
If this is made correctly, there wont be any problem causing you lag when caching or fetching bricks.
If there still are questions about this, notice me.
Ephialtes:
You're very persistent aren't you.
The biggest reason why this is totally not feasible is because of the processing involved of calculating which bricks are within your range and which are not. This is a lot of processing and would slow down everything considerably. I think you should leave network architecture to the people who have professional experience.