LiSE: Difference between revisions
From Game Making Tools Wiki
LogicalDash (talk | contribs) (Link to where you can get in touch with me instead of just my github profile) |
m (Glossary link update) |
||
| Line 8: | Line 8: | ||
}} | }} | ||
'''LiSE''' is an engine for life simulation games. It is currently in alpha. The [https://github.com/LogicalDash/LiSE source code] is available under the [https://github.com/LogicalDash/LiSE/blob/master/LICENSE GPL3] | '''LiSE''' is an engine for life simulation games. It is currently in alpha. The [https://github.com/LogicalDash/LiSE source code] is available under the [https://github.com/LogicalDash/LiSE/blob/master/LICENSE GPL3]. | ||
Though there is a graphical frontend available, with the option to export your game planned, the engine itself runs in a server. It's meant to handle the parts of game logic termed the "simulation," here meaning the abstract sort of simulation present in life simulators of the kind that [[:Wikipedia:Maxis|Maxis]] once made. The intent is to enable a [[Glossary | Though there is a graphical frontend available, with the option to export your game planned, the engine itself runs in a server. It's meant to handle the parts of game logic termed the "simulation," here meaning the abstract sort of simulation present in life simulators of the kind that [[:Wikipedia:Maxis|Maxis]] once made. The intent is to enable a [[Guide:Glossary#Workflow|workflow]] where one developer can focus solely on the logic of the game, while others worry about making it look good and respond well to user input and so forth — and these developers never need to even talk to one another. Building your game in LiSE means you get a modding [[Guide:Glossary#API|API]] for free. | ||
== Core features == | == Core features == | ||
| Line 27: | Line 27: | ||
* Rule constructor: Build rules out of functions represented as cards. Looks like deckbuilding in a card game like Magic. | * Rule constructor: Build rules out of functions represented as cards. Looks like deckbuilding in a card game like Magic. | ||
* Autosave. Actually, anything you do gets put in a transaction that gets committed when you quit. In any case you never need to save | * Autosave. Actually, anything you do gets put in a transaction that gets committed when you quit. In any case you never need to save | ||
[[Category:Game Builder]] | [[Category:Game Builder]] | ||
Revision as of 23:35, 13 June 2021
| LiSE | |
|---|---|
| Release date: | Alpha |
| Made by: | Zachary Spector |
| Runs on: | |
| Exports to: | |
LiSE is an engine for life simulation games. It is currently in alpha. The source code is available under the GPL3.
Though there is a graphical frontend available, with the option to export your game planned, the engine itself runs in a server. It's meant to handle the parts of game logic termed the "simulation," here meaning the abstract sort of simulation present in life simulators of the kind that Maxis once made. The intent is to enable a workflow where one developer can focus solely on the logic of the game, while others worry about making it look good and respond well to user input and so forth — and these developers never need to even talk to one another. Building your game in LiSE means you get a modding API for free.
Core features
- Object relational mapper for graph based world models.
- Journaling to allow world state changes to be rewound and replayed.
- Integration with NetworkX for convenient access to various graph algorithms, particularly pathfinding.
- Rules engine: define your game's behavior in terms of actions that are performed in response to triggers. Change the connection from trigger to action without effort. Copy triggers and actions between games easily.
- Can be run as a web server, so that you can control LiSE and query its world state from any other game engine you please.
Frontend features
- View and edit state graphs in a drag-and-drop interface.
- Rewind time and the interface will show you the state of the world back then.
- Code editor with syntax highlighting.
- Rule constructor: Build rules out of functions represented as cards. Looks like deckbuilding in a card game like Magic.
- Autosave. Actually, anything you do gets put in a transaction that gets committed when you quit. In any case you never need to save
