Below is a short video showing how easy it is to alter the Ember models on the fly, to better fit with the data sent from the server.
Since Worldforge is built around the server and client agnostic Atlas protocol, there’s no firm connection between how entities appear on the client (for example Ember or Sear) and how they are represented on the server. We do provide examples of 2d clients too for example.
This disconnect requires that Ember knows how to present different entities to the user, and this is most often done by using some kind of 3d mesh. The following video shows how the server-entity-to-mesh mapping can be altered on the fly.