What the hell is going on with scenarios and the bolster function???

[Boursk]

So I've been doing couple SC's now that I'm back after 3 years away and I can't help but notice there are some serious (like really) REALLY serious issues with the bolstering in some of them where you could be fighting players in their lower levels down to 16 as a level 35 for example.

So I did High Pass Cemetery just now on my DPS AM, started casting dots as usual and I was thinking to myself "Wow, these guys are dying really easily" so then I looked in my party first and saw a LEVEL 16 Witcher Hunter, with literaly no bolster at all.



I then looked in the scenario list and saw that the people I had been killing were literaly 15 levels lower than me with absolutely no bolster to help them out and I was absolutely gobsmacked how such a thing could be happening. I genuinely felt bad for killing them and anyone that is doing SC's at a low level like theirs.



The sad thing is I somehow forgot that this **** from 3 years ago actually existed, but I did not think it possible that it still could be a thing.

[Hargrim]

Bugs go here: https://github.com/WarEmu/WarBugs/issues?state=open

[Boursk]

Bugs go here: https://github.com/WarEmu/WarBugs/issues?state=open

Well yea there is no question that this goes in the bug tracker, but are you telling me that nobody else in my 3 YEARS of absence has noticed this and not said something about it?

These are low level players, possibly players that just have gone past T1 Scenario range and then they are met with this?

[Sulorie]

Bugs go here: https://github.com/WarEmu/WarBugs/issues?state=open

Well yea there is no question that this goes in the bug tracker, but are you telling me that nobody else in my 3 YEARS of absence has noticed this and not said something about it?

These are low level players, possibly players that just have gone past T1 Scenario range and then they are met with this?

It's a recent bug. Nobody had to deal with it unless there was a bug. Lower ranks are bolstered usually above max rank for a bracket.

[Boursk]

Bugs go here: https://github.com/WarEmu/WarBugs/issues?state=open

Well yea there is no question that this goes in the bug tracker, but are you telling me that nobody else in my 3 YEARS of absence has noticed this and not said something about it?

These are low level players, possibly players that just have gone past T1 Scenario range and then they are met with this?

It's a recent bug. Nobody had to deal with it unless there was a bug. Lower ranks are bolstered usually above max rank for a bracket.

It is not a recent bug, this was happening 3 years ago too.

[Boursk]

Something else I just noticed in the screenshot, how did Wulgard the chosen get 40k renown himself?

[Phantasm]

Sometimes ppl miss to read every patch notes, I get it. There was a sc bracket change week or 2 ago and its just a bug with triggering bolster on particular sc. Bugtrack it and will be fixed.
DPS AM at low rank is another question of balance issues, tho

[Sulorie]

It is not a recent bug, this was happening 3 years ago too.

And you had the impression, that this bug persisted for 3 years without anyone complaining about it, in order to get it fixed?
This issue is new since 1-2 weeks due to sc tier changes.

[Ysaran]

Something else I just noticed in the screenshot, how did Wulgard the chosen get 40k renown himself?

The bug was fixed and it is appeared again some weeks ago due to the tiers change. SC score count zone lock so if you get 30k renown from locking a zone your renown score is enhanced by 30k

[Boursk]

Sometimes ppl miss to read every patch notes, I get it. There was a sc bracket change week or 2 ago and its just a bug with triggering bolster on particular sc. Bugtrack it and will be fixed.
DPS AM at low rank is another question of balance issues, tho

I don't know about that, I've seen a couple SC's now where the bolster hasn't applied; Nordernwatch, High Pass Cemetry and Maw of Madness.

DPS AM is fine, gets smacked if even a semi-decent DPS class starts hitting the AM.

Nonetheless, I will post it to bugtracker yea.