LiSE

LiSE copied to clipboard

Limit the amount of time a rule may take to run

1

Currently, if a rule has an infinite loop in it, LiSE cannot recover; you just have to kill it and start over. There should be a time limit after which...

clayote

You have to log stuff in your simulation code in order to understand what it's doing. This will be less urgent when the debugging tools (#54) are ready but in...

clayote

Game switcher

1

ELiDE should have a window to browse to some other world database and load it with all the associated code.

clayote

If a rule raises an exception, its effects should be cancelled. The planning feature may be useful to implement this, as there is already a facility to cancel a plan.

clayote

Currently there is no convenient way for the user to tell if a plan they are making contradicts one made previously. Contradicted plans are always canceled unceremoniously. If you want...

clayote

Accessibility features

1

It'd be useful for visually impaired users to have ELiDE say the names of entities when you mouse over them, read out stats for you and whatnot. I could implement...

clayote

Partial function configurator

1

Some functions that you use in rules will take keyword arguments that need to be pre-filled by the user before using the function in a rule. They're a kind of...

clayote

To make the Pixel City buildings work I need to give them a new widget that can stack repeating textures into a TextureStack in response to button presses corresponding to...

clayote

There should be an interchange format that contains the definitions of some rules and the Python code necessary to run them. It should be easy to make these and easy...

clayote

Rulebook priorities

1

Currently, if you want to change the order your rulebooks are executed in, you can't really; you have to change the name of the entity the rulebook's on. You ought...

clayote