Ideas - What are your opinions?

[Jacob__mybb_import1]

Lately I've been thinking about making Buildism easier to use, and also more different from that 3D game making program that everyone likes to post about. Here are the main things I'm going to do:

• No more adding characters or starting/stopping physics. You just build your game, then click a "Test" button to add a character, run all scripts and start the physics. When you leave test mode, everything will be reset.
  
• No more script objects. Instead, all scripting is done through events (like the current events menu that you get when you right click something.) The only way to run event scripts is to test the game, but they will be checked for syntax errors as you type.
  

Here is a prototype of the new editor layout, ignore my horrible sketching.

[Qwertygiy]

[*]No more script objects. Instead, all scripting is done through events (like the current events menu that you get when you right click something.) The only way to run event scripts is to test the game, but they will be checked for syntax errors as you type.

I like the checking for syntax errors part a lot; however, making them only use events would make having indefinitely looping scripts slightly more difficult.

[Hippo]

Maybe you could make it optional which editor you use?

[Duck]

• No more script objects. Instead, all scripting is done through events (like the current events menu that you get when you right click something.) The only way to run event scripts is to test the game, but they will be checked for syntax errors as you type.
  

nonononononononononononononnoonononononononononoo

[Jacob__mybb_import1]

[*]No more script objects. Instead, all scripting is done through events (like the current events menu that you get when you right click something.) The only way to run event scripts is to test the game, but they will be checked for syntax errors as you type.

I like the checking for syntax errors part a lot; however, making them only use events would make having indefinitely looping scripts slightly more difficult.

Infinite loops are almost always bad design anyway, so I'll probably make "while true do" a syntax error. In java, a while loop with a sleep() in it causes a compiler warning.

sleep() will be also be done away with, since it causes more bugs than it's worth. To replace sleeping and using infinite loops, I'll add something like the setTimeout() function in JavaScript, so you could do this:

[lua]function doSomething()
print("something")
setTimeout(doSomething, 0.5) --call the function again after 5 seconds
end
doSomething()
[/lua]
All of that code would go in the game.Started event that will be added.

You could also do this put this in a Clicked event limit the firing rate of weapons: (object will be the object that the event goes with, to replace "script")
[lua]
if not object.Enabled.Value then return end
--...
object.Enabled.Value = false
setTimeout(function() object.Enabled.Value = true end, 5)
[/lua]

[Mustachio]

[Dignity]

So... no more scripts?

I thought you wanted games...

[Jacob__mybb_import1]

Tell me one thing that won't be able to be done with the new scripting system.

Also, I'm pretty sure the old one would be more confusing if you hadn't used Roblox first.

[Glome]

I like the idea.

Also, fix the triangles.

[Paradox]

I like this, it's seem a lot similar to Blockland's Event system, which I really liked also.