RogueBasin
Menu (Edit):
Contents:
  1. Roguelike engine

Roguelike engine


A roguelike engine is not a playable game but rather an underlying structure that can power many different games. Roguelike engines exist to allow people to easily write new games without the hassle of coding things like Line of Sight code, object handling, RNG, etcetera. The idea of a roguelike engine is a good one: roguelikes are too often forked. If an engine is used, this can decrease the likelihood of forking. Interactive fiction games, which are a non-roguelike type of adventure games, nowadays always use engines, the most common of which are Inform and the Text Adventure Development System.

The most popular roguelike engine is T-Engine, the engine powering ToME, made by DarkGod but which has other modules available.

Some other engines include (most abandoned for a decade):

  • libtcod, which eschews engine development for a pure library approach and has seen widescale uptake among 7DRL participants.
  • Carceri (abandoned)
  • The Ng Java Roguelike Engine (abandoned)
  • H-World a pure game engine by Hansjoerg Malthener (abandoned)
  • Tenney Level Generator .Net a new early stage library that is being written in C# for use in a Roguelike game. The author has decided to adapt the library to allow for more flexibility by other developers. (abandoned)
  • The Neon roguelike engine. (abandoned)
  • pYendor (abandoned)

While T-World is the most successful RL engine to date, it builds on the whole Angband variant explosion, which shows that a functional game with clean code can serve the same basic function as an engine. T-World developed as an engine only after ToME was established as a popular game. Various attempts at a roguelike engine have come and gone without any success, because there was no game to develop an audience that was thinking “Wouldn’t it be cool if…”. The comparison to IF games is somewhat misleading: IF games generally are not competing to find more interesting game mechanics, whereas roguelike developers are generally wanting to tinker with new magic systems, new combat systems, new this and new that, so that it is much harder for an engine to either not end up frustrating developers or requiring such complexity in designing a game with it to not represent an advantage over not using the engine in the first place. For these reasons, roguelike specific libraries may be a more promising route to making new game development easier. In any case, any engine developer should create at least one good game with his own engine, because if you can’t show success using your engine, why should anyone else expect they can?