Lots of code could probably be cleaned up. Mainly in the StatBoostMgr.cpp file.

Can only add one enchantment?
two
three
......Configurable

It happens with statbooster module and dungeon respawn module.

Loving this module so far and very thankful that you made it. After 48 hours of my players enjoying it here are their/my enhancement requests.

1. Allow us to adjust the enchant chance on rarity could be cool and a better config option than the current implementation which is "what is the minimum rarity to begin enchanting" this way you could set for example.

White.Quest.Reward = 5%

Grey.Loot = 10%

Green.Crafted = 25%

etc.

2. Decimal places.

If you put 2.5% the config errors out on worldserver boot and sets it to 100%.

Allowing us to have one decimal place would be nice.

3. Multiple cascading enchantments.

The other random enchants is beautiful because you can have options like;

First.Enchant: 50%
Second.Enchant: 10%
Third.Enchant: 10%

So that 50% of items have one enchant, but 5% have two enchants, but 0.5% have three enchants. It's really cool how this changes everything.

One enchant is enough to shake gearing up a bit, but multiple enchants completely rewrites the game.

After some testing and playing with this module i got weird situations with some interface addons.I am using NUI+ addon for wow https://www.curseforge.com/wow/addons/nui
After some time when i got item and equipeed it(example shield with enchant +5 health my interface start bugging and fps start slowdown because of errors.Buggrabber saved situation but it start spamming evry 30 sec to chat about bugs and NUi addon stopped showing buffs durations.I even tried few other addons which work with showing buffs, but they also was broken(example elks buffs https://www.curseforge.com/wow/addons/elkbuffbars )

The scoring is all hard-coded at the moment and should be moved to the database.

The readme is getting quite large and would probably benefit from extracting the notes and writing a wiki.

The database table needs to be populated with enchants up to the wotlk ilvl range.

The file contains like 350 or so enchantments with ilvl min and max carefully calculated into around 8 tiers.

Enchantments will appear when the ilvl begins and disappear in 4ish tiers from then. For example +3 spirit can appear on both lvl 5 greens but also lvl 60 epics but will never appear on TBC gear.

Tier 1: Levelling enchantments. (Under 50)
Tier 2: Classic blues. (50+)
Tier 3: Classic epics. (65+)
Tier 4: TBC dungeon gear. (90+)
Tier 5: TBC heroic/raid gear. (125+)
Tier 6: Wotlk dungeon gear. (170+)
Tier 7: Wotlk purples (200+)
Tier 8: Wotlk real gear (223+)

All that is missing are the

• element spell damages (e.g +8 fire damage)

• element resistances (e.g 10 fire resist)

• weapon damage (e.g +5 damage to beasts)

• resilience/mp5/hp5

statbooster template v3 enhanced.txt

Does this module can use any stats id from Randomproperty.dbc or also Randomsuffix.dbc?

I ask this because theiy differs and stats from randomsuffix.dbc can be scale with item level if two different items will have same suffix but with different item level those stats will be differ.

I can't figure out how to solve this problem the server crashes

crash.zip

It would be a good idea to implement the subclass mask column into the db and be handled in the module.
Now that the class mask system is in place it should be easy to implement without an overhaul.

This change helps with assigning enchants to certain subclass, avoiding enchants like Fiery on a bow and scopes on general weapons like daggers/staves/etc.

It might be a good idea to add extra scoring for the scoring field so the scores can be very specific.

For example, a cloth helmet with intellect would be scored as SPELL but a plate helmet with intellect would be scored also with SPELL where it should be HYBRID, adding extra fields would allow the user to score them differently.

I have added about 1k of enchants to test and the ilvl does not quite work well or does not work.

The stat analysis function needs to be optimized and smarter. There are still some cases where items are incorrectly assigned stats that do not match the item.

I think it would be a good idea to be able to define whether or not an enchant can only be rolled on weapon or armor or both.
This would prevent things like Fiery Enchant being rolled on armor if it was added to the enchant table.

I suspect there may be some memory leaks somewhere and would appreciate help finding them.

On sheet:

When linked to chat:

It would be nice if enchants were visible so that they can be seen via linking.

E.g. uses:

"WTS: [link]"

or

"/w hey friend look at [link] how cool is this"