BONUS System

This project involves a bunch of refactoring and some thought into how it should be built

State:

The BONUS system is currently is very text based, which results in a lot of processing in order to capture the current bonus value for a particular bonus type.
The BONUS system is also deeply integrated in the core (code tangles or circular class dependencies depending on your vocabulary)

Project Goals:

Ideally, the BONUS system should be more "random access" than the incrementing that is required in many cases
The BONUS system also has problems with and vs. or logic. One can apply a bonus to all melee weapons, or to all slaphing weapons. However, a BONUS cannot be applied to all weapons that are slashing AND melee (and only slashing AND melee)

Output System

This subsystem is primarily composed of our export tokens.

State:

Output Tokens have a nasty habit of silently consuming errors, and there is very little in the way to validate Output Token Syntax.
Ouptut Tokens are half-plugin-ized, meaning many of them are plugins, but some are too tightly integrated in the core.
We also need a documentation review of Output Tokens, to ensure the documentation is complete and up-to-date.

Project Goals:

The system needs a new concept of plugin to give export tokens more flexibility to allow them all to be plugins
Review export tokens vs. our documentation
Longer term, it would be nice for export tokens to be able to validate their syntax, as well as import and export tokens from the same file (the plugin). This gives a clean way to test round-robin behavior, as well as allowing us to deprecate tokens and change them to something else much easier.