Sapphire -> RE: On Guests (4/2/2022 12:00:50)
|
Dealing with Guests will likely be a ton of work, but if staff wanted to "fix" charisma I think there's only one solution. Manual updates of guests, and a different P.O.V of BM's. Let's be realistic. a BEASTMASTER, when that player decides to train Charisma, is purposefully knowing they're going to be doing a ton of damage WITH Charisma. Just like a warrior uses Strength. Just like a Mage uses Intelligence. Just like a Ranger uses Dexterity. Some say the introduction of charisma weapons, et al was mistake. Maybe, if you believe Charisma to be a secondary stat... But the reality is, to a Beastmaster, it's not. It's their mainstat. So I think everyone should just realize that we have 4 Mainstat builds in AQ and stop playing pretend like we don't. Mainstat+END+LUCK = the Pure builds for Warrior, Mage, Ranger, and Beastmaster alike. It's really that simple. Stop overcomplicating the game. Therefore, You place BTH at charisma+luck, for charisma weapons and pets/guests just like with the other mainstats. You then understand that the Charisma weapon is this build's main weapon of choice. Staff assumed charisma weapons in their models. It never made sense (still doesn't) because the CHAR/END/LUK build is not really a feasible build unless there's more charisma gear made, ESPECIALLY F2P stuff. This means, what we think of as standard beast builds *are actually beast-hybrids*, where the other mainstat is serving more like a co-main or even a secondary stat either for more weapon damage (STR/DEX) at the cost of BTH (luk), or the INT then supplies MP-based guest upkeep and if so desired, spells.. I was originally thinking maybe charisma weapons should take on a damage decrease, but then why not just train INT and use magic weapons? Solution-> If using a charisma weapon, guest upkeep is given a discount This might incentivize the "pure" BM playstyle and compete with hybrid BM's...?? Solution-> Increase upkeep for MP-based Guests by quite a bit, based on 20 turn models. 2632 MP/20= 131.6 per turn. Mages get 4 casts @ 653. This leaves 20 MP. So lets use 2612 instead. 2612/20=130.6. I say MP Guest upkeep get bumped to 131/turn. If using a Charisma weapon, which will have lower damage than a magic weapon, guest upkeep is then pushed to 98. This is a 25% discount. At 98, in 20 turns they spend 1960 MP, leaving 672. This is enough for 1 spell used in 20 turns. To me, that's fair. The charisma weapon held, is paying for a lower Guest upkeep which goes from 131 to 98 per turn, allowing for 1 spell cast. The same needs to occur for SP. If a "BeastMage" gets 20 turns of MP-based guest upkeep, so should other variants. Starting SP-> 395. Max SP-> 1470 SP Regen/turn.-> 98 SP Guest-> 86/Turn So this is +13 /turn In 20 turns, the 395 starter SP becomes 655 SP (turn based regen minus guest upkeep) But this means no misc upkeep, or anything else. +13 is small. So 25% SP upkeep discount then means: 65 SP Guest Upkeep. That's +33 SP gained per turn. In 20 turns, the 395 starter SP becomes 1055 SP. So Proposal: 1. Charisma recognized as a mainstat 2. CHAR/END/LUK is the Pure Beastmaster build 3. Other Mainstat/CHAR/END or LUCK = BM Hybrids 4. Lower Charisma Weapon Damage below Magic via STATS. Unsure where as of yet. I think 56% Melee as of now, but will see. (25% off 75%) 5. Raise MP Upkeep on MP Guests to 130 from 114. This leaves 20 MP after 20 turns, just like 4 Mage spell-casts. A BeastMage uses the same MP if they cast 4 spells, or have MP guest for 20 turns. 6. Keep Guest SP Upkeep the same 7. Discount MP and SP Guest upkeeps 25% if wielding a charisma weapon. If Charisma weapons are lower than magic, this incentivizes their use by discounted upkeep costs. This becomes 98 MP and 65 SP. 8. Hybrid BM variants will use resources less efficiently, and can use a variety of things...better weapons, spells, skills, etc. Pure BM gets discounted upkeeps to use guests longer, charisma weapons continue to override all type locked skills, but has a lot lower damage. This would require manual updates to guests. I think while the workload is a lot, it's the best answer. No band aid solution here.
|
|
|
|