3 ms·
I think the acid test for a "game engine" should be the ability to use it to produce behaviour other than the original. For instance, if you somehow learn a Sup
by YeGoblynQueenne 9y ago
I think the acid test for a "game engine" should be the ability to use it to produce behaviour other than the original. For instance, if you somehow learn a Super Mario engine, you should be able to reprogram it to play a new level that you designed yourself. Even more importantly- you should be able to play the game and get a different outcome every time.
From the paper I think the "game engine" they learn is not even capable of playing the same level in a different way than in the examples. If Mario jumps in frame X, the "game engine" will always show Mario jumping in frame X, and not know there's any other possible state at that time than frame X with Mario jumping in it.
I mean, I see the value in this, totally- they've learned an automaton that can faithfully reproduce its examples and that's no mean feat. But like I say above it would make a lot more sense to define a "game engine" as an automaton that can reproduce the entire range of behaviours of its original- not just a set of its output frames and only that set of frames, in perpetuity.
Of course a "game engine" in the sense I give it above is (in the case of games) a Turing complete automaton- so it would be impossible to learn to simulate it just from examples of its output (there's a lot of maths on that). So the paper settles for the easiest task. OK. But the way they present it is misleading.