This page is out of date

You've reached a page on the Ren'Py wiki. Due to massive spam, the wiki hasn't been updated in over 5 years, and much of the information here is very out of date. We've kept it because some of it is of historic interest, but all the information relevant to modern versions of Ren'Py has been moved elsewhere.

Some places to look are:

Please do not create new links to this page.


Tile Engine for Tile-Based Maps and Unit Engine for Turn-Based Games

The Tile Engine and Unit Engine are extensions, written by Chronoluminaire, for adding isometric or square-grid tile-based maps into Ren'Py.

Contents

Where can I get them?

What are they?

The TileEngine is a Ren'Py object you can use to represent and display a map that's built out of tiles. It'll do the following:

The UnitEngine is a Ren'Py object that builds on top of the TileEngine, providing a lot more infrastructure for games that want to move units around the map, especially in a turn-based way. It lets you do the following:

The UnitEngine works either with "Movement Points" or "Action Points", and you specify which one you want to use when you create it. In the Movement Points (MP) system, each unit gets to move a certain number of spaces per turn, and also gets a specified number of actions per turn (usually 1). In the Action Points (AP) system, movement and action both come from the same allocation of Action Points each turn.

It has a Callback system so that your own Ren'Py code can be executed whenever the user selects a unit, moves a unit, or takes an action.

Restrictions:

Known bugs

Features for a possible later version

General