| Blockland Forums > General Discussion |
| Terrain (OH stuff I JUST WENT THERE) |
| << < (9/16) > >> |
| heedicalking:
--- Quote from: otto-san on April 11, 2013, 06:51:19 PM ---how would they know it'd be a detriment to development of features they haven't even started on yet? perhaps not even planned? that's not how coding works. badspot didn't make the engine, and definitely didn't go into BL knowing the exact C++ workings of it. it was probably realised later on that they were becoming an inconvenience and waited awhile before pulling the trigger on removing them. though obviously i'm not badspot and am certainly not close enough to any of the developers to know any of this for sure. it's just an educated guess. --- End quote --- normally i might agree that they wouldn't have realized that a feature would inhibit the implementation of future features, but in this case it doesn't seem like that was the problem the developers brought up. --- Quote from: Komp ---These two features complicate Blockland’s code tremendously. That means we can’t add game features very quickly. They still have bugs in them (after years of work). They are slow, too - bricks are about 90% of their speed and can do a LOT more (explosions, events, in-game editing). --- End quote --- they realize that they are making bricks slow. bricks have been in the game for years. this is just a matter of code efficiency testing and has nothing to do with future updates, its about making the current game run faster. this could've been fixed from day 1 if they traced what was causing things to run slow. "after years of work" shows that they've already known that t/i were buggy and bad. they've been putting band-aids on a tumor instead of removing it when it was first discovered. this is what happens when they wait. this is the end result of putting off problems like this. features CAN be re-worked to be more efficient. see: "reworking the inventory system to be more efficient!" "reworking the game framework to support future updates!". |
| otto-san:
--- Quote from: heedicalking on April 11, 2013, 07:05:08 PM ---normally i might agree that they wouldn't have realized that a feature would inhibit the implementation of future features, but in this case it doesn't seem like that was the problem the developers brought up.they realize that they are making bricks slow. bricks have been in the game for years. this is just a matter of code efficiency testing and has nothing to do with future updates, its about making the current game run faster. this could've been fixed from day 1 if they traced what was causing things to run slow. "after years of work" shows that they've already known that t/i were buggy and bad. they've been putting band-aids on a tumor instead of removing it when it was first discovered. this is what happens when they wait. this is the end result of putting off problems like this. features CAN be re-worked to be more efficient. see: "reworking the inventory system to be more efficient!" "reworking the game framework to support future updates!". --- End quote --- you're making valid arguments but they aren't extremely sound he was saying bricks perform 90% as well as terrain; it was a comparison. they were working on patching because they wanted to avoid removing them, i'd guess. these 'patches' would be the attempts at reworking you're talking about, and when they weren't working, it would be decided to just remove them instead of wasting more time on them. i'm sure if they wanted to rework enough of the engine to fix them they probably could, but, as it was said, they'd been trying for years with apparently unsatisfactory results. |
| Tomcat:
--- Quote from: otto-san on April 11, 2013, 07:12:02 PM ---you're making valid arguments but they aren't extremely sound he was saying bricks perform 90% as well as terrain; it was a comparison. they were working on patching because they wanted to avoid removing them, i'd guess. these 'patches' would be the attempts at reworking you're talking about, and when they weren't working, it would be decided to just remove them instead of wasting more time on them. i'm sure if they wanted to rework enough of the engine to fix them they probably could, but, as it was said, they'd been trying for years with apparently unsatisfactory results. --- End quote --- let's see what gameplay features were added after terrains were gone. bots (shaky because they were already done.) let's see what gameplay features were taken away. decent vehicle collision decent fps on 1-2km sized maps decent dog fights, fort wars, etc. let's see what we got. shadows and shaders that add nothing to gameplay because 50% of blockland users can't use them. |
| BuildaBox:
--- Quote from: Tomcat on April 11, 2013, 07:17:49 PM ---decent dog fights, fort wars, etc. --- End quote --- Like whoever said before, that's about the user base, not the developers. If you don't like the current servers then make your own. |
| The Resonte!:
--- Quote from: heedicalking on April 11, 2013, 07:05:08 PM ---blibbity blop --- End quote --- essentially what you're saying is They procrastinated fixing/removing terrain/interiors please come back when you have never procrastinated ever --- Quote from: Tomcat on April 11, 2013, 07:17:49 PM ---let's see what gameplay features were added after terrains were gone. bots (shaky because they were already done.) Along with balls, Speedkart gamemodes, camera events, and a hell lot of bug fixes. let's see what gameplay features were taken away. decent vehicle collision the vehicles were always like that with bricks with terrain sure why not decent fps on 1-2km sized maps decent dog fights, fort wars, etc. time to build your own maps mwahahahahaha let's see what we got. shadows and shaders that add nothing to gameplay because 50% of blockland users can't use them.to be more specific it's about 35% --- End quote --- --- Quote from: BuildaBox on April 11, 2013, 07:19:54 PM ---Like whoever said before, that's about the user base, not the developers. If you don't like the current servers then make your own. --- End quote --- People might have reasons to not make servers, even if they have great ideas. like Internet issues too costly for hosting like RTB and private reasons like hackers and viruses. |
| Navigation |
| Message Index |
| Next page |
| Previous page |