The game template supplies the available events/action/value. The Game Creator guides you through the available options supplied by the template. It then tries to use a human speech like interface to receive the input, the game logic. Currently there is only one game template. Each new game template would need to supply it's own possible events/actions/values to suit it's needs.
This game template was design for students with zero experience. So the create new objects command was omitted in the user defined rules. The game itself controls the box placement for this game. The goal of that game was to learn about events and actions.
I plan to add more game templates with the create object command for more advanced users. You can set it's properties, game physic values and so on. The game itself will need to implement and execute that command. The game template just tells the Game Creator what that current game supports. So the magic happens in the game code. Hit view source on the game if want to see it.
The project was built in a 2 weeks; server, Alexa integration, mini-game, and game creator logic. If the project gets any traction, I'd love to keep working on it.
Mostly yes. The difference is rather than changing values, you are creating event handlers, actions, and their values. You can only trigger actions on events the game already has and execute actions the game supports which is defined in the game template. With that said, there is no reason why it couldn't support all the events and actions from the core game engine it uses. For this release the focus was for beginners and the options were minimized.
A game template looks something like this: https://gist.github.com/jamesfdickinson/65b9f5a05f4902468c46...