Hi there ,
Patch is working but on my character defensive mods such as mitigation from death are not working . I do not get any armor after any kill which still makes this unplayable . Please advise urgently
Hey there - does mitigation from death not work for you in multiplayer (Client or host?) or in solo? Or both?
How does 20 minutes of prior gameplay at all impact a single instance of an enemy attack?
You mention wanting a full picture, but in no way have you described what the additional context actually offers.
The previous gameplay would let us see whether the game's inbuilt oneshot/death-prevention mechanics triggered and then went onto cooldown/were on cooldown at time of death (which is normal), or whether they never procc'd at all (which would be unintended behaviour).
Read moreSet bonus on the Borealis set for Technomancer isn’t working. Not receiving 90% damage bonus.
Set bonus for Statue set for Devastator isn’t working. Damage granted isn’t working as described by the set bonus description.
Trickster Cyclone skill bugs out when knocked back as you activate the skill (on another players connection). You then proceed to get stuck when you walk. Only way to move is to dodge roll. Only way to fix is to quit to lobby and reload into the game.
Multiplayer connection is very inconsistent. Yellow and red bar connection. Skills incorrectly show uses left and when skills are usable (says no cooldown but still on cooldown). Please look into dedicated severs or try improve the net code.
Multiplayer high latency compensation and aim assist. I’ve noticed that when I join people in the US (from South Africa), even if the host connection is good (1 gig connection), the game seems to try assist by giving you aimbot aim assist where you...
Thank you very much compiling this lengthy list, I (and by the looks of it everyone else) very much appreciates it!
A few of these things will be covered in my known issues list tomorrow, for others I'm having the team check through our database (JIRA) if they have anything similar on file, or if they are able to reproduce the issue you've mentioned in particular.
As a final question - what language do you play in? I assume it's English as you mentioned US and South Africa but I wanted to double-check as our April 30th patch clarified the set description on the Borealis Monach in English, but other languages still need to be fixed as well. So knowing whether you're reading it in English or not-English will give me a better understanding of what issue you're seeing.
Just for reference, I spec 20% Resistance in my tree and use damage absorber for a total of 30% all the time and have rarely been one shot, maybe from the brood mother pre patch a couple of times, but usually because I was trying tank them and loads of adds.
I always presumed it was armour that would help mitigate the damage bug as it was physical attacks, can you confirm if certain attacks are maybe dealing anomoly damage? That might be where abit of confusion from the players is coming from.
Also, played some expos last night and didn't get one shot, tried to make it happen a couple of times but didn't
Appreciate the responses as always Toby.
Good to get some context, thank you very much! I'm actually talking to the team to see if I can pull together a survivibility guide to help explain some of the more nebulous mechanics, included which damage source does what. If I'm able to put that out, I think it may go a long way in explaining to people why they might be dying (perhaps because their build isn't ideal for the damage source).
Once everyone has an understanding of that, we can actually get a better understanding of what is a true issue and what is people being underspecc'd and not using damage prevention mechanics properly (because the mechanics are so hard to understand without a guide).
Read more"Supremacy: Progression" stuk at 99% & "Sybilla Flores" Lore entrie doesn't unlock
- What platform are you on?
- Steam
- What exactly happened?
- So I recently defeated Yagak solo on my devastator (I was waiting for the restoration to do this as my deva build was almost perfect and I knew I would have better chances with him) after I finished it, theoretically, my accolade section for "Progression" should complete as the one thing I was missing was completing all expeditions solo, unfortunately this didn't happen, the accolade "Supremacy: Progression" is stuck at 99% and nothing I do will fix that, all other accolades in this tab are complete. It occurred to me that this might also be related to other bug I found in the accolades/journals, basically, because of the Demo I think, there's one character lore entry that doesn't appear as unlocked, even though I did unlock it in the Demo, the entry is the one...
Thanks for the report! Can you get in touch with our support team - I believe they may be able to help look into your account specifically to help you with this in particular:
sqex.to/support
Ok folks, after some initial testing I have found that Resistance is key to survival for anomaly based attacks. Without confirmation from u/thearcan, that includes Monster melee, altered attacks, statuses, etc. My pyro feels like my Dev with just the addition of the CIRCLE OF POWER tier 3 mod. Earlier I was tight over my deaths but after this change it feels bomb! Please try it out.
Just to confirm - from your previous post (here) - since that post you essentially started using Resistance and in particular a Tier 3 Resistance Mod as a mitigator against damage and your survival increased?
Or put differently: Your build previously had very little focus on mitigating against anomaly damage and you were getting rinsed by anomaly damage? And then you included resistance into your build and you started to survive better?
This might be a long shot but, could it be it is triggering only after death due to latency? Possibly causing also that "invincible" bug where players have no life yet are able to move and act even though the healthbar is clearly depleted, as if the game kinda caught up late to the mechanic but whatever activated on death (disabled colliders?) stay as the game registered?
It's a long shot, but I wouldn't dismiss it as a potential reason here. I'll check in with the team about this - we are running latency testing to improve multiplayer testing at the moment too, so this will be worthwhile checking in on the high ping tests.
Edit: Actually this is a solo-run from OP so latency shouldnt matter as they are they host... I'll still ask the team to look into it.
How would the mechanic have proc’d on this specific expedition before this fight. It’s weak mobs 2 or 3 at a time that are easily dispatched by a competent player on t15 without being hit. Unless this guy was just standing there for the previous 20 seconds he wouldn’t have proc’d the mechanic. Most people on here have ran this run enough to see 2 seconds of it and can tell you the order of enemies that come out up to this point.
Yep, I very much agree with you - Given the spawns occurring at that early point on this particular expeditions, it's unlikely that the mechanic would already have procc'd in the time between expedition start and the recording start.
BUT: We would have to make the assumption that OP did in fact not procc the mechanic, but that would be an assumption.
Given the fact that OP is a glass cannon build with no defensive mods, it may not be out of the realm of possibility that the death prevention mechanic might have procc'd before, even from OP being hit by weaker mobs.
But this is all based on assumption, as I mentioned. Us seeing the full run, start to finish would allow us to specifically identify whether the mechanics are triggered as intended and then going into cooldown (and is that cooldown too long?) or whether they are simply not activating at the first opportunity.
Edit: Furthermore, without knowing OPs full build, we can't assume that...
Read moreThere used to be a mechanic like that. I tried saying that in my reply but it was ignored. You would take absolutely no damage for a period of time at a certain health parameter.
There used to be a mechanic like that. I tried saying that in my reply but it was ignored. You would take absolutely no damage for a period of time at a certain health parameter.
I didn't ignore you - what I said was that that mechanic exists but has a cooldown. So it's possible that in these reports the mechanics procc'd very shortly beforehand, went on their respective cooldowns and then the player was once again hit, while it was still on cooldown.
I've now seen 4 different videos people have posted after the patch showing this shit CLEARLY didn't work.
Lol, this is absolutely f**king hilarious now.
I talked a bit more about this here.
Would you be able to perhaps link me to one of those videos that are a full length expedition run that ends in this issue? The ones I've seen so far are too short to be able to form a complete picture of the particular situation.
one-shot kill mechanic
you actually get hit twice
That really does not matter, you guys are focusing on the wrong issue.
One hit or ten hits, the health bar should not just instantly evaporate like that.
You need to decrease enemy damage or increase player resistance. There is a reason why the players are saying that the game was the most fun when the golem mod was bugged.
I know you are not the one calling the shots, but you won't be able to logic yourselves out of this one. Players will complain until something substantial is done.
I talked a bit more about this here. That should help better frame things.
Read moreSo you are saying that unless you are at 100% health then its not considered a true one-shot. That is BS, as going all the way back to the demo, there has always been a mechanic to stop from being killed immediately. You would always go to VERY LOW health (depended on the actual level of character) and then die on next hit. I grinded that damn captain for FAR too long to realize that I couldn't just get killed immediately.
I have been patient and wanted this to work but it is getting to the point of bullshit excuses. It was not fixed and it used to work a specific way. I think the fact that it worked and now doesn't is what makes it worse. If it had always been like this, then it wouldn't be as big of a deal.
I probably have Xbox game clips from getting Leggos that I saved that would prove the mechanic worked a different way than it currently does. It consistently would get you down to a specific health number, stay on that number EVEN when shots would hit you a...
So you are saying that unless you are at 100% health then its not considered a true one-shot. That is BS, as going all the way back to the demo, there has always been a mechanic to stop from being killed immediately. You would always go to VERY LOW health (depended on the actual level of character) and then die on next hit. I grinded that damn captain for FAR too long to realize that I couldn't just get killed immediately.
Precisely. This is why I've been asking for videos of this issue occurring where we can see the full expedition run, not just the 20 seconds of the issue occurring.
To make myself clearer:
The one-shot kill prevention mechanics (plural) still exist in the game (just as you observed them during the demo), but they have a (short) cooldown. If they are on cooldown, players can be killed very rapidly.
Thats why I need to see the full expedition video of such reports - to determine whether there were previous ...
Read moreYou just gotta stand with full health and let them shoot you once and record it. Looks like they need an exact specific proof. People keep running around leaving enemies nearby and they keep coming up with excuses.
Please make sure that any such recording includes the full expedition run, not just the 20 seconds of the issue occurring. We'd need to see happens in the time before the issue appears.
Read moreI don’t know if this will help anything, but whatever seems to have been happening with damage before seems to still be happening.
Here is a video that I just captured (after installing the patch)
At the end I back out to the lobby and I’m still getting the “blood screen” (albeit without the spatter this time).
My first question is, is this how the game is supposed to act? Should I be getting insta-killed by a melee through a little shield, most of my health, and a couple stacks of Mitigation? If so, that’s fine. I’ll run more def mods.
My second question is, why am I still getting the “blood screen”? It makes me feel like something is still broken.
For context: this is a CT14 and all of my gear is lvl50. I run Mitigation from Death, one resistance node on the tree, and the borrowed time shield mod from the Chrono set.
I know I’m going to get shredded by all of the MLG analysts on here f...
Here is a video that I just captured (after installing the patch)
Thanks for the video - do you have a clip or recording of the full gameplay session before this?
We need to see what happened in the time before the issue occurred to determine whether the one-shot kill mechanic is working as expected.
Looking at the video in 0.25 speed, you actually get hit twice - the first attacking bringing you down to 600 health, the second attack killing you.
I don't have a longer piece, this is what Xbox records when you do quick share, fact is i am getting that red screen as well when i select character. So i got red screen, loaded in, started expedition, that's it, nothing fancy.
Okay - what would be helpful is to see the full 45 seconds previous to when this clip started recording - that way we can see if there were any other times a one-shot protection might have already procc'd and gone onto cooldown.
If you run into this issue again, could you please try to share a full clip, from expedition start, through to when the issue appears?
I mean most of the stuff I've seen mentioned by the community manager reads as double speak and self covering. We know they did stealth nerfs, we know they call them bugs when they get caught. I know they nerfed drop rates for like 4 days, why because for those 4 days there were new chests all over the place. I've since leveled two characters to max and helped a few friends, never has those chests come back.
SE is pulling a hard gasslighting on the player base in hopes no one calls them on it. PCF don't know what is causing the bug, the issue is due to not having a test live server base for real testing, and having to many teams able to alter the game at once. No team should be able to alter the game in real time, it should go through testing. If I sent a server update live without full testing across all programs and apps I'd be fired.
We have a staging environment for both the game and backend.
Yep - I'm hoping to share this later this week.
Tiago starting his line a second before you actually die is just a sync thing, right? Otherwise it opens a whole new can of worms. That was f**king rough, indeed.
Guess the ''one-shot kill protection mechanic'' u/thearcan mentioned few times is still bullshit I always thought it was, too.
If you pause the time at 0:21 you can see the health drop to 6202, then to 0.
So this isn't a true one-shot kill, 100% to 0%. Rather it's two hits in extremely close proximity.
I'm not denying the validity of this report and the one-shot kill protection may indeed need looking at as well since it may well should have indeed triggered here in some form. The audio triggering before the death occurs is also very unusual. Still, we're looking into it.
The team now have the video file and are trying to work through it to see what's going on, but what would help alot is if the OP /u/Loilen could share a longer piece of recorded gameplay since just before the expedition start, so we can see the full setup before hand.
Are you serious? Have you seen the video? The Xbox buttons? You guys are ridiculous !
Controller UI also appears on PC when playing with a controller. Apologies, I thought I had read that this was a steam version in one of these replies.
Its in UTC time, that's why this is literally 4 minutes after they finished maintenance.
And no, i didn't have any defense mods, not that any of that was going to help.
Its in UTC time, that's why this is literally 4 minutes after they finished maintenance.
Could you confirm whether you downloaded the patch? The patch released on Steam towards the end of the maintenance. The maintenance itself didn't resolve the issue, the patch does. Did you download that?
Steam can sometimes be a bit finnicky with downloads.
devtrackers.gg