First, a little about me: I’ve been making games for 20-25+ years in some capacity, started out with text adventures on the BBC Micro, some of my faves include The Hobbit, Colossal Adventure and Hampstead. Moved onto the Amiga and finally onto PC.
Fast forward to now and I’ve been busy developing a role-playing / text adventure engine for the last year (including one total rewrite)… which just happens to be multiplayer =D (you are able to collaborate with others with world building / editing right built into the engine). All commands are descriptive and very easy to pick up.
Why am I building it, because the older I’ve got the more I’ve slowly become fascinated with how much power there is in words and that’s what I want at the heart of #adlengine and any scenarios I create within the engine.
The aim is to make it customisable and moddable to allow people to bring words to life in unique ways, offering both freedom to create and freedom of play, including CYOA, Dungeon Crawler and more.
The engine can be deployed to the web using webfiles + .adlengine files. Or your game can be shared with others by sharing the .adlengine file/s which they can play on the downloadable software versions.
Would love it if you got chance to check it out. All questions / feedback welcomed
Here’s a few gifs for demonstration.
Below is a custom theme I’ve made in adlengine for an adventure I will be creating in it called Adliberum…
Hi yes the parser currently doesn’t take variations for objects (currently) although, to interact with the dirt pile, dirt should work. e.g. push dirt, take dirt. look at skull would work / examine skull.
Single player should work in any browser and your game / work can be downloaded using the dl command which exports it to a .adlengine file which can be imported. (IF you name this file game.adlengine it auto loads if its found either in the web directory or in the main folder.)
Look plinth - i don’t understand that.
Look stone plinth - i don’t understand that.
Look on plinth - i don’t understand that.
look skull - i don’t understand that.
examine skull -> picture of skull. Yea!!
get skull - I don’t understand that.
take skull - You take the skull. Yes!!
the skull breaks revealing a small key
examine small key - you can’t see a SMALL KEY
take key - you cant see a KEY
look key - i don’t understand that.
reply with the symbol rendered. If it worked you should have just typed the @ symbol. Please provide as much detail as you can, including location, keyboard type, keyboard layout, language etc.
Please reply whether the keys render in Russian or not and whether they render correctly for you. Please provide as much detail as you can, including location, keyboard type, keyboard layout, language etc.
try entering the following command смотреть (look) and pressing ENTER. If it worked, the screen will refresh and you will be presented with the first starting room of the demo scenario.
Engine seems to rely on scancodes rather than input characters, and implements the phonetic layout itself. But this layout very rarely used (I think only met it on soviet PDP-11 clone, some 25 years ago, and it was already obsolete back then). Modern and much more widely used layout sometimes is referred as ЙЦУКЕН.
Much more comfortable, thanks:) One thing though: in second row rightmost key (’/") should produce э/Э instead of 0. And key right below ESC (`/~) can produce ё/Ё, but this is not obligatory, the letter is kinda disputed and in most cases can be safely replaced by e/E. So if it poses a problem, don’t give it to much sweat.