You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. Could you create some documentation for developers? I have an idea for a very modular and overengineered HTML5-based platform for text quests and I'm curious if it is (at least partly) implemented in this engine.
My idea is such:
Layer 0 is the js engine and other components provided by the system. The examples are Mozilla Firefox, Google Chromium, Node.js with packages, Windows 10 Universal Platform.
Layer 1 is the engine abstraction layer.
Layer 2 is the core framework.
On the layer 3 GUI engines are placed, providing necessary widgets: inventories, menus, maps, HUDs, etc...
On the layer 4 game engines lie. Game engine is an interpreter of game programming language with its std library. Its purpose is to either translate the game source code into JS, or work above JS. This way we'll be able to plug any platform, such as python based RenPy (using PyPyJS) or lua based Instead (using tools like https://github.com/kripken/lua.vm.js) or even z-machine (using https://github.com/curiousdannii/parchment).
On the layer 5 quests frameworks lie. They are based on core framework written in available programming languages. Here we can create models for world, objects, characters, relationships, etc.
On the layer 6 the actual game is.
How is this architecture related to the architecture of your engine?
The text was updated successfully, but these errors were encountered:
KOLANICH
changed the title
Any documentation for developers
Any documentation for developers?
Feb 20, 2016
Hello. Could you create some documentation for developers? I have an idea for a very modular and overengineered HTML5-based platform for text quests and I'm curious if it is (at least partly) implemented in this engine.
My idea is such:
How is this architecture related to the architecture of your engine?
The text was updated successfully, but these errors were encountered: