Okay, since it still didn't work and there's no checks to see if it is greater than the default amount, I went into the DBC file and it is pulling the maximum amount from there. Since the configuration settings aren't working correctly, you can edit the CurrencyTypes.dbc Ids 392 (HonorPoints). But you shouldn't be required to edit the DBC to change the cap, else, they wouldn't have the option to.
I do see the flaw with the Honor points though. In Player.cpp under 'Player::GetCurrencyTotalCap':
The if statements I highlighted should be removed because the logic makes no sense. Why make a configuration setting for a max cap and check to see if the config setting is greater than 0, set it to the default cap in the dbc.. Anyway, just remove those if statements because I don't see any harm in removing them as it seems it shouldn't have been added in the first place.
uint32 Player::GetCurrencyTotalCap(CurrencyTypesEntry const* currency) const
uint32 cap = currency->TotalCap;
uint32 honorcap = sWorld->getIntConfig(CONFIG_CURRENCY_MAX_HONOR_POINTS);
if (honorcap > 0)
cap = honorcap;
uint32 justicecap = sWorld->getIntConfig(CONFIG_CURRENCY_MAX_JUSTICE_POINTS);
if (justicecap > 0)
cap = justicecap;
That might solve your max Honor Points issue.. Now for the Conquest Points:
Sadly, the "Currency.ConquestPointsWeekCap" config setting serves no purpose as "CONFIG_CURRENCY_CONQUEST_POINTS_WEEK_CAP" isn't being used anywhere in the source but loading from World.cpp.
I looked further into the source and this comment confused me:
This is inside the Player.cpp file under "Player::GetCurrencyWeekCap":
//original conquest not have week cap
Currency Conquest Points returns the Conquest Arena Meta and Conquest BG Meta points..
Since Conquest Points has no actual cap, I really can't seem to help much towards that. Anyway, I hope this helped.