Difference between revisions of "Neon"

From RogueBasin
Jump to navigation Jump to search
(added current work)
Line 17: Line 17:
==Description==
==Description==
===Engine===
===Engine===
Neon is not a single game, but an engine that can run roguelikes. All data needed for a specific game is stored in a set of XML files. These files are loaded when starting the engine.  
Neon is not a single game, but an engine that can run roguelikes. All data needed for a specific game is stored in a set of XML files. These files are loaded when starting the engine. This allows anyone to make their own roguelike without the need to write code.


===Features===
===Features===
Line 24: Line 24:


==Current work==
==Current work==
===Map===
The cell-based map structure will be transferred to a tree structure with an xml backend. This has the advantage that the whole map is contained in a single structure, and will make it easier to stream map data to/from the hard disk.

Revision as of 22:00, 20 February 2008

Neon roguelike engine
Alpha Project
Developer mdriesen
Theme
Influences The Elder Scrolls, ADOM
Released 28th of august 2007
Updated 7 Oct 2007 - 0.1.0
Licensing GPL
P. Language Java, JavaScript
Platforms Java 6
Interface Unicode
Game Length
Official site of Neon roguelike engine


Neon is a roguelike engine. It features a huge overland map and can be modified with XML and JavaScript.

Description

Engine

Neon is not a single game, but an engine that can run roguelikes. All data needed for a specific game is stored in a set of XML files. These files are loaded when starting the engine. This allows anyone to make their own roguelike without the need to write code.

Features

The engine can handle truly huge maps. The main overland map for testing in the alpha version measures 19584 x 13152 tiles, but can be much bigger. The overland map is on the same scale as the dungeons and scrolls with the player character centered on screen. Dungeons are for now more or less limited to single-level dungeons. Multi-level dungeons can be created, but the implementation is still somewhat awkward.

Current work

Map

The cell-based map structure will be transferred to a tree structure with an xml backend. This has the advantage that the whole map is contained in a single structure, and will make it easier to stream map data to/from the hard disk.