Quenty
|
  |
| Joined: 03 Sep 2009 |
| Total Posts: 9316 |
|
|
| 08 Feb 2013 01:40 PM |
I posted this on my blog, but I thought I'd post it here.
It's on my ROBLOX blog here: http://t.co/P3gR0apT
ROBLOX has been coming into new problems of backwards compatibility. If you look at the recent blog post ( http://blog.roblox.com/2013/02/dynamic-lighting-and-shadows-the-voxel-solution/ ), you'll see that they say this:
"We obviously can’t just turn this on (the interiors of all your virtual homes would go totally dark, for one thing), so we’re kicking around ideas as to how we’re going to introduce users to our new lighting system. It could be an opt-in sort of scenario, or a setting for your place that you could turn on and off. We’re working daily on ironing out the bugs and we’ll keep you posted as soon as this becomes an active part of ROBLOX."
I think and believe the best solution is to create versions of ROBLOX. Like we have versions of HTML and stuff, ROBLOX would basically create a backwards compatible version, and then everything from that point on would be in "ROBLOX 2.0. This means they could change a lot of the weird unstandardized API, change how stuff works, change what's locked, and a lot of other stuff they can't do now for the fear of the lash back caused by breaking millions of games simultaneously.
Now, there are some problems with this, such as users complaining they can't use features without updating their games to accommodate others, and the fact ROBLOX would have to maintain 2 game versions. The best solution I can find is that after a few months, ROBLOX stop providing backwards compatibility. That would mean users could still play old games, but they would have to update to the new version of game in order to update it, and users would soon find that the new ROBLOX runs faster and loads faster.
ROBLOX could update a lot of things in their code, and fix a lot of problems. Version control could be as simple as modifying a value in the place config, and this update time period could give game creators enough time to update their place. And the incentive to update their place would be large, because if they don't, then they'll be missing out of dynamic lighting and other such things.
Other things that would be nice to receive as updates would be the ZIndex update described by Anaminus, and a API standardization, as well as a few other things.
What do you think? |
|
|
| Report Abuse |
|
|
TheMyrco
|
  |
| Joined: 13 Aug 2011 |
| Total Posts: 15105 |
|
|
| 08 Feb 2013 01:42 PM |
I think what you think.
Nice site you got there by the way. |
|
|
| Report Abuse |
|
|
Quenty
|
  |
| Joined: 03 Sep 2009 |
| Total Posts: 9316 |
|
| |
|
TheMyrco
|
  |
| Joined: 13 Aug 2011 |
| Total Posts: 15105 |
|
|
| 08 Feb 2013 01:54 PM |
Maybe we should make a thread where all the bugs, so far found, are posted in and possible fixes/ideas.
|
|
|
| Report Abuse |
|
|
Quenty
|
  |
| Joined: 03 Sep 2009 |
| Total Posts: 9316 |
|
|
| 08 Feb 2013 02:03 PM |
http://wiki.roblox.com/index.php/User:Quenty/Glitches
|
|
|
| Report Abuse |
|
|
TheMyrco
|
  |
| Joined: 13 Aug 2011 |
| Total Posts: 15105 |
|
|
| 08 Feb 2013 02:06 PM |
| Quenty stop doing good things xD |
|
|
| Report Abuse |
|
|
|
| 08 Feb 2013 06:56 PM |
The wiki has a bug log right here: http://wiki.roblox.com/index.php/Bug_log
I'd appreciate if someone could help maintaining it. We could actually report bugs, get them to be put on there, and get the developers to actually look at the list. |
|
|
| Report Abuse |
|
|
Parthax
|
  |
| Joined: 27 Apr 2011 |
| Total Posts: 6941 |
|
|
| 08 Feb 2013 07:03 PM |
or we could just have: game.Lighting.DynamicLighting of course, normally it would be set to false, but for more advanced users... it could be useful.
[Content Trolled] |
|
|
| Report Abuse |
|
|