Forth was used for a few commercial games in the 80's(e.g. Starflight), but game programming tends towards getting knee-deep in a statically allocated global state with a large, bespoken update procedure, both of which run contrary to Moore's preferred style of Forth(small word sizes, most things on the stack). So relative to macroassembers, the obvious competitor, most of the potential in Forth can't be usefully realized without reframing it as a metaprogramming tool that emits an assembler binary(In which case - you are going for high level abstraction. There are languages that give you lots of those without effort on your part.)

Forth does excel at low memory usage, but the gains are only realized when you don't have a static allocation driving things. Game scenes and most real-time code are statically allocated because statics will allow you to "deliver on what you promise" - if memory is maxed out, the system still hits its deadlines.