engine

Required skills: Python

Difficulty: Easy

For the initial asset conversion, openage provides textual output to signal which stage of conversion has been reached. The output usually looks like this:

INFO [py] converting metadata
INFO [py] [0] palette
INFO [py] [1] empires.dat
INFO [py] Starting conversion...
INFO [py] Extracting Genie data...
INFO [py] Creating API-like ob

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'map engine test'
2. Press the key 'n' until you get to Tristam.
3. Wait about 3 seconds '....'
4. See the fire effects that are on the ground stop animating. This same problem seems to occur on all maps but it's easiest to find in Tristam.

**Expected beha

The fix for #3307 was done for GitRepository only. This bug tracks the rest of the repositories.

System Information

• Ogre Version: e80555d6a06dbcad192286818113ad69618b04a1
• Operating System / Platform: andr

Is your feature request related to a problem? Please describe.

Killing one script at a time is a complete and absolute pain when doing testing. Especially if the code is already in disarray and generating a plethora of identical scripts.

Describe the solution you'd like

Please add support for killing a range or sequence

RulesEngine has many amazing features but lacks detailed documentation on those.

• Json based rules defination
• Multiple input support
• Dynamic object input support
• C# Expression support
• Extending expression via custom class/type injection
• Scoped parameters
• Post rule execution actions

Please comment on which feature you feel needs more/improved documentation.