Visual issues with Trace Beam effects and Encounter threat level after the 2.15.0 Update
HPWUrobert
Posts: 719Moderator › admin
Trace Beam visualization and Encounter threat level of many Encounters do not correspond to their Registry threat level classification after the 2.15.0 Update. We're looking into why this recent change is not behaving as intended. We'll provide more details in a follow-up once we know more.
Below is an example of an Encounter whose beam and Encounter threat level do not match its Registry threat level:
Post edited by HPWUrobert on
Tagged:
79
Comments
For many traces the "cast" screen shows threat level that is one level higher than the one shown in the registry. For example Seamus Finnigan is "HIGH" in the registry and "VERY HIGH" on the "cast ebublio" screen.
Most foundables are affected by this bug. Crystal Ball is one exception (MEDIUM in both places). There may be others.
@Hiti1 pointed me to a related post - https://community.harrypotterwizardsunite.com/en/discussion/8075/incorrect-threat-levels
I just updated to 2.15. The first emergency flare I saw turned out to be the tank of brains, which is actually severe. The severe flares I clicked on were actually very high, including Tonks.
its not a bug, its that they are lazy, this is how they 'fixed' the threat clock being wrong (showing everything 1 threat level higher).
So, now: medium= yellow, high= orange, severe & emergency= red
Firenze is showing as a red beam. Puking Pastille Display as orange. It seems everything is stepped up by one flag level.
Same problem, tried posting with a few pictures of a trace but it went into review.
I have seen yellow (high) stream traces that are not actually a streamed trace at all. Have also seem a few that were orange streamed (severe) but were actually suppose to be yellow streams. And worst of all is seeing ones that are showing red (emergency) streams that are not emergency traces but suppose to be orange.
Doesnt appear to be affect all streamed traces but might be affecting the ones that were fixed from stating the wrong threat level and are now showing the stream for the wrong threat level instead.
This is going to be a real problem when I pop a barufios, and look for 5 red beams to place my 5 trace charms on. If only 1 in 5 of those red beams is actually severe, it’ll be really hard to effectively farm field guides and XP.
Please fix this ASAP.
Just popped a trace charm on a red beam and got a severe. Sigh.
The same goes for everything. Beam reflects the incorrect severity we've been seeing in 2.14.
If they don't fix it soon, a lot of people are going to be quite angry about wasting trace charms.
I’m just going to quote PARRYHOTTER:
“This is going to be a real problem when I pop a barufios, and look for 5 red beams to place my 5 trace charms on. If only 1 in 5 of those red beams is actually severe, it’ll be really hard to effectively farm field guides and XP.
Please fix this ASAP.”
Ok, maybe the problem is that the rarity of some traces ON THE MAP is WRONG, they doesn't match their descriptions on the exploration page... Ex: Omnioculars appears as VERY HIGH on the map, but they are HIGH on the exploration page; the Mirror of Erised appears as SEVERE on the map, but they are VERY HIGH... please, fix they rarity ON THE MAP...
@Drakonite - the problem is the rewards are still the same. Tank of Brains shows up as a red beam, but you still get rewards (wiz xp, family xp, field guides) as if it were an orange beam.
From what I could tell, Oddities were the only thing NOT effected by this new bug/change.
So, which part is broken now? And what was actually the intended change? The beams all showing a higher threat level than what the registry says? The threat level being indicated by the beam and threat meter in the encounter? Or the rewards being given for successful returns not matching the encounter threat level? But instead, still matching the registry threat level?
Way to break the game even more. Severes are reading as if they are Emergency, yet still giving the same rewards as Severes have always given. Now we have to engage in a foundable, check if it actually an Emergency (new players are s.o.l., since they might not know which are true Emergency and which are Severe, falsely reporting as Emergency), back out, then use a trace charm.
Way to further waste all of the players time. Your ineptitude and failure to bug check is at an all time high!
Great. You have just made trace charm into a piece of junk since red flares are nor really red flares. Only safe to use on oddities. You have turned something desireable into something frustrating. Who field tested this change? Trace charm FUBARed for a third time.
This seems to be quite the series of unfortunate events. I too was affected by this problem earlier today, but this hasn’t been a recent problem. Several weeks ago I TC’d a red flare only to get a (as it was then a bunch of) orange flares appear. To further frustrate, the origin trace also was thereafter only a severe despite still showing the red flare and even though I’d already been in to the trace once and seen it was actually an emergency-level foundable! Most of the time, happily, the TC worked as intended, but not being based in a particularly populous area, losing the rare sighting of an emergency was a tough break!
(The irony of being driven by the game’s feature construct to think “Hmmmm an emergency... you just wait there while I pop off to make more emergencies and then I’ll be back to clear you up” is not lost on me!)
@SS1951 “Who field tested this change?”
I think you know the answer to that question already!
Seriously @hpwulola, @HPWUrobert
Why dont you just shut down the game. Ever since May its just been one bad decision and bad update after another. you clearly have no interest in making a great game.
Bad update, bad decisions, no poi sync.. why even bother with the game... If this was on the roadmap, its understandable why Fazes left.
I understand the idea behind the new flares (not linking it to the severity level, but the level on the threat wheel), but you really really really should have made sure that it was still possible to make a distinction between an emergency level foundable and a severe level foundable. This makes finishing the registry much harder and makes the TC (again) more difficult to use. Why not change it back to the way it was and give those medium-high foundables a green flare. Or leave it as it is now and give the emergency level foundable a black or another appropriate distinguishable color? Please don't leave it this way.
@hpwulola @HPWUrobert @HPWUTeam can you fix this yesterday? Or just tell us to stop playing, either works for me.
So the bug was:
Foundable threat-level visualization is inconsistent with its Registry classification2.15 'fixes' this bug:
Fixed an issue with threat level visual effects on Traces that appear on the MapThe initial bug was that encounter threat level doesn't match registry threat level. E.g. "very high" in registry shows as "severe" within encounter and "severe" in registry shows as "emergency" within encounter.
The bug 'fix' did not fix the bug. Instead it changed the map visualization, aka beams, to match the in-encounter threat level. So anything with encounter threat level "high" and lower is non-beamed, "very high" is yellow beamed, "severe" is orange beamed, and "emergency" is red beamed. However these threat levels don't match the registry (and since rewards are based on registry threat level, the map visualizations now don't match the rewards).
So we still multiple issues:
The fix was unnecessary: if encounter threat level was fixed to match registry, than none of the beams would have changed. By changing the beams, it doesn't fix the registry vs encounter threat level inconsistency and it creates new bugs: foundables of same threat level having different beams and traces with the same beam giving different rewards.
By the way: Can we go back to the old foundable threat level classification (i.e. low, medium, high)? The new classification (i.e. medium, high, very high) doesn't add anything except make discussions more confusing with multiple levels of highs.
(Sorry if this is a duplicate post, I'm having difficulty getting the post to show up so I'm clicking post again...)
So the bug was:
Foundable threat-level visualization is inconsistent with its Registry classification
2.15 'fixes' this bug:
Fixed an issue with threat level visual effects on Traces that appear on the Map
The initial bug was that encounter threat level doesn't match registry threat level. E.g. "very high" in registry shows as "severe" within encounter and "severe" in registry shows as "emergency" within encounter.
The bug 'fix' did not fix the bug. Instead it changed the map visualization, aka beams, to match the in-encounter threat level. So anything with encounter threat level "high" and lower is non-beamed, "very high" is yellow beamed, "severe" is orange beamed, and "emergency" is red beamed. However these threat levels don't match the registry (and since rewards are based on registry threat level, the map visualizations now don't match the rewards).
So we still multiple issues:
The fix was unnecessary: if encounter threat level was fixed to match registry, than none of the beams would change. By changing the beams, it doesn't fix the registry vs encounter threat level inconsistency and it creates new bugs: foundables of same threat level have different beams and traces with the same beam giving different rewards.
By the way: Can we go back to the old foundable threat level classification (i.e. low, medium, high)? The new classification (i.e. medium, high, very high) doesn't add anything except make discussions more confusing with multiple levels of highs.
I made mistake in my previous suggestions: I said to give the medium-high a green flare, but I meant the high foundables that now have gotten a yellow one and previously had none. (Mistake is due to the fact that I still have the old severity levels in my mind)
Yeah this is ****, this has to go to the old low/med/high/severe/emergency system.
Severe cannot be red emergency when emergency is red emergency. And you simply cannot change the rarity of already collected fragments from a whole year, it breaks the effort put in and it breaks the game
I don't mind giving a new beam to the lower level less commons (whatever they are called now) but using the same beam for severe and emergency is a bad change. The rewards are very different and so are the priorities like using a trace charm.
Lol... Looks like I might prestige one of my dragon pages to gold soon..
I want to add my voice of displeasure to this change. On the aesthetic side, this drastically increases the number of flares showing up, which makes it harder to see and pick out individual ones when clustered together. On the usability side, being over-saturated with higher flares makes them less meaningful, and it's much less "exciting" to find an Orange or Red flare. On the programmatic side, all the required fragment counts and reward levels were set with the pre-existing severity levels in mind, and now they no longer match up. On the experience side, longer-term players have to try and completely re-learn which fragments are found with which flare colors.
This is a (poor) solution in search of a problem. Flares exist to draw your attention to a "rarer"/more challenging/more rewarding fragment when it shows up on your map, and diluting this makes the whole experience worth less.
PLEASE do not push this bugged update. Those of us who have not downloaded it do not want to deal with this level of dysfunction. Seriously guys, now that you have a reputation for recurrently messing things up wit h EVERY little change, have you considered that you might lose players en masse? How about testing "fixes" and "updates" before releasing them on us like a pandemic, huh?
Adding to the poll to revert the change to beams to prior to 2.5. It is very important to differentiate between severe and emergencies especially when the rewards for the field guides are so different (8 and 20!).
Glad I'm not nuts in being confused why Moaning Myrtle is suddenly a severe...
Was just coming to also report this. I have had yellow streams which were in fact NO stream foundables, which can also tell from how many fragments total needed as well as the field guides given.
Have had orange streams that should be yellow streams as well as red streams that should be orange. This last one is the most frustrating being I like to use my trace charm on red (emergency) streams and now I have to first give a look at what it is to make sure suppose to be a red stream.
Two images are from same trace, showed orange stream and said severe, but is actually a yellow streamed trace. Which you can tell by number fragments needed as well as guides it gave in 2nd image.
Please sort this as I much preferred the bug that was fixed where it just said the wrong threat level verses showing the wrong stream color.