It looks ok. I think the convention is to assign the array (result from store.find) to the content property if you’ve extended ArrayController, rather than model. Last I checked though, one is aliased to the other, so it shouldn’t matter.
There’s a good deal of unnecessary indirection in your code example, so I’m assuming you elided some lines, though it’s common for newcomers to try to do a lot of things manually that Ember would otherwise do automatically. Maybe the issue is in the elided lines, or else the store/adapter is not finding any game records.
The problem was with that line. I suppose if you override the default template to say EntityList then it will also assume there’s an EntityListController.
I fixed it by specifying a controller name as well using:
this.render(“entityList”, {controller: “foo”});
There are plenty of omitted lines. For instance I’m extending EntityListRoute into a GameListRoute so I assumed it would look for GameListController. Since I changed it to use “entityList” in that line I guess it changed the default name again.