Sirus ground degen
|
Can anyone help me understand why i got shock and bloodcloud debuff despite not touching any ground effect, nor being hit by anything? Is the damage from those red burning things larger than the visual effect?
And how comes that two doses of healt flask did not have any apparent effect? Lastly, since i failed the fight now i need to respawn the conquerors to attempt Sirus again. I spawned the Hunter influenec but now it is asking me to complete 7 maps under his influence before being able to fight him....does it really takes that much now? wasn't it 3 influenced maps to fight a conqueror? Do i really need to complete 28 influenced maps (+ the attempts to spawn them in the beginning) to re-attempt Sirus?  Last edited by Jackkal#5957 on Jan 29, 2022, 8:09:44 PM Last bumped on Jan 30, 2022, 3:44:55 PM
|
|
|
Regarding your second question, the consistent 3 maps was just for the storyline parts. Once you've finished that and challenged sirus for the first time, you have to do 5, 7, or 9 maps (randomly chosen) to fight a conqueror. Worst case scenario is indeed 36 maps before another sirus attempt, but it's rare that all 4 conqs will demand 9 maps.
The dude drops great stuff so a large time sink is part of the cost of fighting him. It's not too bad if you do other stuff incidentally while getting conqs down. Украина в моём сердце
|
|
" all of this is changing in 6 days |
|
|
Are you on predictive? Looks like a desynch to me the server clearly thinks you are stood in an area
Lifeflask doesn't have an effect for the same reason, its active but your degen is so rapid that it isn't actually recovering you any life all its doing is slowing the rate you degenerate at. Again it looks like lag, server still has you in zone even after you flamedash out. |
|
" Yes i'm on predictive but, as i was keeping the latency plot on top right of the screen, i couldn't see any lag spike. Usually i see them when desync happens. Moreover, i didn't walk over the red flames, why would the game think that? |
|
|
when on predictive, your position on server is slightly different then on client. Game thinks you walked over the flames because on server you have walked over the flames.
IGN: Eric_Lindros
CET: Timezone |
|
" Don't know how GGG's code works under the hood but with pseudo 3d like this if you take your vector when you are initially moving and carry it on for like a 100ms spike you end up stood on the edge of a red zone, if no correction or validation then takes place on the server you are stood in it until sufficient movement occurs that it recalculates. on predictive desyncs happen all the time you just don't notice because most are totally irrelevant but this time it got you IMO, if you lag alot you'll see a bad one when you rubber band backwards but your positions usually slightly incorrect most of the time. I've not played on predictive for years because lockstep is without a doubt the best thing they ever added to the game. |
|
" Yes. Your latency was consistently less than 50ms... you really should be using lockstep mode. - here's my sig
|
|
|
OK, thanks for the answers
|
|
