Sapphire -> RE: =AQ= Stat Overhaul Discussion & Feedback! (1/31/2024 13:51:51)
|
quote:
While we are at it, why not fix the issue where guests' MP upkeep is unfair for non-mage builds ? I.e., beast-mages have the SP bar free to do other things when they use Summon (To avoid future build identity debate again ). Sorry if this was discussed by any of the previous posters. Do not have the opportunity to read everything. I've talked about this at great length in a variety of places. The MP upkeep guest is both a problem and not a problem. But IMO the MP upkeep guest should be on a separate standard than the SP upkeep guest, but that won't happen. Let's assume a Mage variant Beastmaster is using MP guests, and then let's compare them to Rangers/Warriors who'd be using SP upkeep guests. Let's also assume pet and guest accuracy are fixed. And lets assume 60% guest valuation. The Ranger and Warrior, using a FD armor will be doing 100% melee per turn. Bows and Warrior Lean will ensure this. Over 20 turns, this is 2000% Melee each. The guest will be doing 60%, and the pet will be doing 40% per turn. This is another 100% Melee, and thus is another 2000% melee over 20 turns. In total, the Ranger and Warrior will be doing 4,000% melee, while in a FD armor. The Mage is assumed to be using spells by virtue of the spell slot and it's MP bar. This feature lowers it's weapon damage to 75% Melee. Normally it'd be doing 4 spell casts for 800% Melee and then 16 turns at 75% for a total of 1200% melee, for a grand total of 2000% Melee. A pet is assumed in the model, but w/o CHA it's value is 20%, so 20x 20=400 for a final total of 2400% Melee. But because for a Mage the use of the spell slot is assumed, if the Mage trains CHA the game's assumptions do not assume the Mage to use a Guest instead of a Spell since the assumptions don't change. This is absurd in reality. However, lets say we swap out 8 spells that represent the 8 elements in favor of 8 MP Guests that represent the 8 elements , which would be common sense. Now not having access to spells this means the player is at 20 turns of 75% (using wands in a FD armor) for 1500% Melee. Then the guest is 60% Melee and the pet is now worth 40% melee due to CHA being trained. This is the same 2000% as Rangers and Warriors. But because the MAge's player-side damage is reduced by 25% per turn for having access to spells as per the standard EVEN THOUGH SPELLS ARN"T USED in this model...the Mage who uses all MP upkeep Guests come in at 2000+1500=3500% Melee...500% Less the Rangers and Warriors. The reality is that a Mage using MP upkeep guests are not on par with Rangers and Warriors due to the drop in weapon damage. In order to catch up, the Mage must use an SP guest instead and choose all TOMES. I have mapped out several models in which the Mages chooses to draw mana from the tome ...and in every case I am only able to manage to get to 4000% Melee in 20 turns, which matches Rangers and Mages. This is the only BeastMage item-loadout that can catch up to BeastRangers and BeastWarriors on paper using standard assumptions and the model. The 3 massive caveats here are as follows, with one being bad for BeastMages and the other two being good for BeastMages. A.Bad- Access to an abundance of Tomes isn't a viable strategy, as their creation is rather anemic and several are premium B. Good- The MP bar does provide a ton of versatility and so if you can access spells, guests, etc via other items it can save a spot here and there C. Good and bad. The creation of the weapon with the compressed spell can give the player both access to a spell and a "bonk", but lacks MP regen. Also, these are a new idea and they have yet to have a pure damage option contained within them. For some this is a no-go while for others that's fine. So the MP upkeep guest is actually completely fine on paper because it's actually less damage than the alternative options. I used to think MP upkeep guests were bad and shouldnt have been created but once you sort of use logic and common sense and map out some scenarios it will show the opposite. Not changing my mind on this, don't forsee any viable arguments otherwise. ________________________________________________________________________________________________________________________________ Now, onto the real topic: I am seeing proposals to bump guest output back to 60%. On the surface, I was fine with this because I thought that came with 2 caveats: A. FS damage would be included B. If it meant an upkeep increase, a very minor would (5% to match the 5% damage) would be OK with me. However, in actuality, there seems to be a movement to use this as an excuse to further increase guest upkeep by even more than logical conclusions, much less just an amount to match the 5% bump in power. (As you've seen even in this thread, some are saying 60% guest output for 40% increase) The result here would be keeping guest output the same but doubling the upkeep, then claiming the style bonus just be a "smaller nerf to upkeep" in essence. And not only that, some people are wanting this while also killing the FS idea I'm sorry, folks, but the baseline for comparison when debating what CHA and guests should be is no longer the 21% upkeep and 60% output. It's 30% upkeep and 45% melee output+10% damage add-on in the form of FS which also boosts status power BTW So since the needle has moved, to me since staff has now put on paper that specific proposal, any further drastic interations to nerf CHA for me is off the table. And people need to understand what is really going on with these proposals to reboost guests back to 60%. Now: 60% Melee for 21% Upkeep Staff: 45% Melee for 30% Upkeep, but a FS mechanic that doubles damage (45->90%) at 22% rate which averages to 55% over time. So 5% damage Nerf for 9% upkeep nerf. The style bonus is FS mechanic. New players nerf proposal 1: Keep Guest output at 60% but Heckate-Nerf guest upkeep to 40%...so here eat this. Alternate extra nerf proposal 2: Keep Guest output at 60%, but this is actually some number lower and then FS brings this up to 60, but also 40% upkeep regardless. Na, I'll take staff's proposal. Thanks, but no thanks.
|
|
|
|