In Discussion Class/Skill [Feedback Request] Skill Changes and Balancing

To be honest I'm kinda through with it, I respect Tim giving his reasoning for it, but he haven't addressed many points that have been repeated again and again in my thread, on top of 110 votes that diagree with this nerf over 64% which means majority of the community is against this nerf.

At this stage I really ask myself is the nerf changing bucc for the better of the community? or for how they wanna see it played? is this server for the players or for the admins idk what to say me and many in game are just tilted over it

My bigger concern is as you said if I decide to make another character now just to have it patched with no announcement completely changing the gamestyle again I know I will have hours of my life wasted yet again and what I learned from this even if the majority of the community is against something proven by vote and comments and smegas in game, admins will ignore it and find justification for their nerfs

 

@Tim

 

Bucc rg was pretty bad before the nerf. I'm curious what tims potion setup and mob clear rotation looked like. My bucc is 11.2k on mw10. I would usually cast mw20 before entering rg. On gizer, I would not consistently get 20 bees. On vl buff and vl card I would get 20 bees most of the time. Conversely my dk would fill clear rg on gizer in 25-30 min. With the changes and already having the ring on bucc, I can't imagine ever doing bees on bucc again.

 

Keep 2hbw slow but let them break cap

 

protest by stop voting for server and stop donating. hell, quit the game even.
but don't quit the forums, keep letting them know how much you hate this.

 

Just remove the cap entirely. It will allow Crushed Skull + shield to be much more viable. It's extremely unsatisfying hitting a damage cap in a game like this because it is essentially wasted DPS and stats caused by a flawed and seemingly pointless game mechanic.

 

Why did you have to give super transform a 3 minute cool down? Every other job had a buff but for some reason you decided to nerf buccs? So even when it’s maxed there will be a 1 minute window where we can’t use our main attack. I’m just wondering what the point was other than try to make all the buccaneer players quit?

 

I cannot agree more. Ive been arguing for limiting multi clienting for years. It promotes anti social behavior and harms the game in ways we never would have foreseen when we first thought to allow it. So many issues caused by something we wanted for convenience. My solution is to limit it to 2 accounts so you can still trade between accounts or leave a shop mule up on another client or bring a single 2nd account to a boss run. Its harmful convenience

 

Harshly disagree. I like having multiple characters online not just for bossing, but also for socializing.

 

I've decided to give my feedback even though I never do that, as a senior developer in a tech company i get many requests for new features and changes and as my product manager always says "we have to give the customers what they want or else they will stop paying and move to rival company" and i think that here in Royals it should be the same concern, you have totally changed classes to the point that even the people that support the change say "just adapt to the new play style" and that's only prove of what an extreme change you made, players look at this and it make them worry "today its bucc that is totally destroyed and in phase 2 it will be more classes, this is a game with a small community and every player that leave leaves a mark in the community people are sad that their good friend are leaving until the moment they find themselves alone in a server that used to be full with friends and now its all strangers. I think the staff should consider more what the community of players actually wants. And one last thing - anni event was delayed for that super bad balance patch, you worked hard for something no one wanted and far more than that ruined the game for many players, you could have invest all that hard work in pink bean and that for sure would make this game better.
I don't want you to think i hate you or something I still love you a lot and appreciate all the hard work you do even when its bad

 

To frame it bluntly, it's shit. Bucc wasn't even that good in RG to begin with, now it's just painful. You wander around, trying to corkscrew the mobs in place when ST is down (charged bubble makes it harder). For 60s, either Barrage + DS or straight up spam DS which feels horrible and slow. I've managed to catch 20 bees in both runs (both on VL buff) that I did after the nerf, but felt like it was rather lucky bee spawn. Not going there again until some solution to AoE damage during ST downtime is presented.

 

Strongly agree. I understand multi-clienting is basically one of the core pillars of Royals but it is massively out of control to the extent that it is genuinely harmful to the game. I don't think it should be removed as it's already considered an essential feature with massive components of the game already dependent on it like a significant part of the economy for example, but definitely limited to maybe 3 windows at most.

 

I like the direction of this change, but I'm also against this nerf — which left me with Decidophobia when voting. (In the end I voted in support, but that doesn't mean I agree with how the change was implemented.)

Rather than forcibly restricting this issue through rules, it's better to limit it through game mechanics — as many people have said, VL's 1-hit-kill mechanic effectively forces players to use only one client, and Sair's complex rotations make duo-att very difficult (though partially possible).

So the direction of this Bucc change is toward limiting multi-client play — but DPS needs to increase significantly to compensate for the higher mechanical demand. There's also the long-standing call that "VL income should at least be comparable to mage farming."

However, if the assumption that "limiting multi-client" is the goal is true, I can't understand why Hero was changed in such a straightforward DPS-boosting way. Perhaps the GMs simply changed Bucc/Hero based on their own understanding of the classes, rather than with any genuine intention to limit multi-client play.

 

So I played some more dk and have a couple of feedback points to add.
Baby zerk + sacrifice:
-you can hit pretty high damage if you high roll stab in baby zerk
-i almost killed myself at ephenia adjusting my HP
-i think sacrifice should be adjusted to always stab or cost a flat amount of hp to adjust to the new zerk layout.
Beholder changes:
-the extra WA is nice but taking it from beholder and adding it to dragons blood is kinda annoying
-its an extra skill to cast and the 160 timer is at an awkward place
-beholder doesn't regularly buff you so you can be without noticeably the accuracy buff so you're better off just using a basket
-make the beholder buffs just one buff that is active when beholder is summoned, delete dragon blood and put the attack back in beholder
.
.
.
Also delete hero

 

SoonTM in phase 2

I still didn't try the new DB properly, and I do think it's uhh.. well, if there weren't any discounts I wouldn't have bothered putting points in it.

Beholder is a buff we can't rely on as it's temporary, even if it's on for 20 minutes, I'd rather use a basket as well.

I think that the accuracy buff would be viable if beholder is perma activated in the 20 minutes time it's on, and that would actually be a meaningful buff to drks.

 

I want to bring I/L Mage to boss fights, so hope there's some changes in phase 2.
The core philosophy behind is by increasing the mechanical difficulty and introducing a skill combo system to boost damage and team utility, reward active play while preventing multi-client abuse.

1st job :
Magic Armor : Rework into a charge-based "Debuff Immunity" (excluding seduce)
Lv 1-5: 1 charge (240s-210s CD)
Lv 5-10: 2 charges (210s-180s CD)
Lv 10-20: 3 charges (180s-120s CD)
------------------------------------------------------------------------------------------------------------------------------------------------------
2nd Job :
Slow : If it doesn't currently, please allow it to affect bosses
------------------------------------------------------------------------------------------------------------------------------------------------------
3rd job :
Seal : Allow it to seal boss skills for 20 seconds.
with a long cooldown: 10 mins at Lv1, 5 mins at max.
------------------------------------------------------------------------------------------------------------------------------------------------------
4th job :
Blizzard : Applies 10 stacks of a "Freeze" status to monsters.

Chain Lightning : Deals significant bonus damage to "Freeze" targets. Each attack consumes 1 stack of freeze.
The previous rule of dealing damage to two nearby monsters simultaneously changed to one nearby.

Ice Demon : Rework into a single-target lingering DoT skill. Upon hitting a monster, the effect moves slowly across the target for 3 seconds, ticking for damage once per second. It also deals bonus damage to "Freeze" targets. The skill will have a 10-second cooldown.

Infinity : Grants an additional +30 TMA during its duration

 

I always think this, but I find it strange to delay the start of an event just because they don’t want to apply a patch during it.
If delaying it by a week would allow them to apply the patch at the same time, I could understand that, but if it’s going to be delayed by a whole month, it would be fine to wait until the next event.
Even a child could understand that.

Or, if we start work after deciding to implement a feature alongside a specific event, would it be difficult to change the target event partway through?
If that’s the case, wouldn’t that mean the estimate for the development period was off from the start?



Although, since this is likely a skill adjustment to make PB more fun and balanced, the order of those steps won’t be reversed.
However, I imagine most people are worried whether it will actually be fun as it stands now.

 

Thanks for the response, it is appreciated.

A few things that came to mind after reading it.


I feel that there’s a big flaw in the philosophy you’re trying to adhere to and the result of it. A big part of a Buccaneers kit, you name yourself, is the utility; most of these things are gained by transforming. Meaning for 1 minute you’re a broken Swiss Army Knife. Just hitting a different part until transformation comes back online isn’t good game design. With this, I'm not advocating that we return ST back to no cooldown, but I do think it needs some kind of redesign so that you aren't just "macro spamming " 75% of the time and have more of a feeling of agency when you actually do transform. (because right now it's a 75% of the time spamming class, but if you do fix the mobbing, range, and stance issues, your transformation doesn't per se add more. So either keep it like this and sometimes you're a broken Swiss Army Knife, or with the changes, transformation doesn't have enough agency).



Also, the part about mobility, while on paper it looks pretty decent, in practice, Buccaneers effectively have the or one of the slowest speeds in the game at the end game. If we ignore mobility skills, most people will already have reached max speed, or near it, so they are on the same level as being transformed. Outside of that, every other class can mount and be the same speed or faster than a transformed Buccaneer by a lot at that point, meaning that mobility wise, not transforming is actually optimal, making the ST nerf a buff to our overall mobility.



A possible direction to address the mobbing issue is buffing either Corkscrew or Backspinblow (preferably Backspinblow, because it promotes the usage of different moves) to hit more mobs at the 4th job. This could be added in as an extra effect by putting points into Dragonstrike at the level 10,20,30 mark. Leaving the skill identity the same during the lower-mid leveling process, at the time when Dragonstrike and Barrage are maxed, stun mastery can't really come into play, because you'll mostly be fighting mobs that are not affected by it.


Another option would be to make Dragonstrike have less end lag so you can reposition and spam Dragonstrike a bit more, while boring it can do the trick.

Hopefully, the issues will be resolved.

 

As a level 200 night lord I barely use avenger during content. I mostly use it in RG. If you are a level 170+ NL doing ranged LHC the avenger buff will help a little bit. The avenger buff is very very minor. You will barely notice it while doing content. If you experienced how bad Nightlords are in rose garden the avenger buff is justified imo. (With this buff nightlords still suck in RG)

I do understand that you are also asking for bowmaster mobbing buffs.

 

i agree.