Talk:Design Tips for a Fun Brickbattle Map: Difference between revisions
>Sloso No edit summary |
m Zunne moved page Talk:Design Tips for a Fun Multiplayer Map to Talk:Design Tips for a Fun Brickbattle Map: they told me to do it |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 15: | Line 15: | ||
Hope it helped! | Hope it helped! | ||
---Sloso | ---Sloso | ||
Destroy stuff. it brings out rage. | |||
10,000 brick limit? Not anymore. Someone should try to reevaluate how many bricks are too many bricks in certain situations. --[[User:Toxsikkilla|Toxsikkilla]] 08:31, 14 August 2008 (CDT) |
Latest revision as of 02:03, 14 October 2024
Destroyable Maps -- Are They Worth the Cost?
Roblox maps with many large, destroyable objects give a fun playing experience. However, they have a significant trade-off; destroyable objects made of many parts cause lag (sometimes VERY large amounts), longer regeneration times, and long level-loading times. Are destroyable objects worth the trade-off?
I try to break up the things, so that the regen time is a little less. Like, having the track in my level regen, then the stations, then the maglevs. I agree, there is a lot of lag that can be caused, but there can also be a good bit of it due to the fact that you are just looking at the bricks. If you look at 500 bricks which are anchored, you will get some lag. If you look at 500 loose bricks in a pile, you will get a lot of lag, due to the fact that you are not only rendering, but you are also calculating collisions like mad.
---Mr Doom Bringer 10:00, 25 March 2007 (CDT)
Yeah. I know. Rendering can be quite slow. Physics can slow down too, and for each brick moved, the computer needs to update.
---Gamer3D 16:59, 25 March 2007 (CDT)
Hehe I put in a new spawnkilling guide Hope it helped! ---Sloso
Destroy stuff. it brings out rage.
10,000 brick limit? Not anymore. Someone should try to reevaluate how many bricks are too many bricks in certain situations. --Toxsikkilla 08:31, 14 August 2008 (CDT)