Medium We need to talk about Neo Tokyo

An additional buggy animation in NT is Dunas' teleporting purple blast attack that blinds. When cast, the attack moves Dunas forward by a set amount. However, sometimes the hurtbox for Dunas will move in the opposite direction of the animation which can result in a similar situation as the above two examples. I can provide video evidence for this interaction if necessary.

 

To add on after several runs of Nibergen from an AM perspective, where I have roughly figured where the hitbox shifts to during its weapon cancel animation:
1) In bodies 1 and 3, during Nib's WCA animation, the hitbox shifts slightly higher. As such, one is unable to attack from below, i.e. standing in the clouds. There have been successful instances, yes. But just like how BMs can currently only hurricane successfully below sometimes (~10%) [a bowmaster would have to constantly shift around to figure out the spot, and whenever Nib moves, the spot changes; this might be a linked problem but I dont have enough experience to comment on], the success rate of hitting during Nib's WCA animation for an AM standing in the clouds is also ~10% of the time. I have yet to figure out what exactly causes the hits to be successful.
1.1) That being said, I have found success in these bodies standing on the left of Nibergen, where precisely because the hitbox shifts up, it doesn't affect a lateral Paralyse landing.
2) In body 2, during Nib's WCA animation, the hitbox shifts down gradually. As such, contrary to body 2, one (as an AM) can only attack from below, i.e. standing in the clouds, to successfully connect the hits. There have also been instances where a melee standing on the left of Nibergen would complain that the hits aren't connecting, for this reason. And, there is one specific period of time during the WCA animation where it shifts all the way down, such that an AM would only be able to connect a hit if they were to stand all the way at the bottom right corner; any further to the left and the hit would be unable to connect. Attached shows such an instance where the hitbox is majorly displaced to the bottom.

 

Whenever anyone says Nib is a boring fight point them to this post and educate them on the built-in damage optimization mechanics it presents

DPM flex thread when?

 

it should be nice if have any place that grind became a good place to farm exp since maps is nice xD

 

not sure when this was updated as i havent done nibergen in awhile, but glad there were some improvements made!

1) boss and pathing are shifted up so that characters arent blocked by clouds anymore if standing below
2) have noticed that there is generally a bigger range for the hitbox. that is, there is more leeway as to how far/close i have to be to nibergen to hit it now (from below). (in the past, you have to be more positioned to the right than now)
3) referring to my earlier post:

in body 1, the hitbox doesnt shift higher anymore. as such, my mages can now hit 100% of the time in body 1!
3.1) however, bodies 2 and 3 have not been updated. that is, in body 2, nibergen's hitbox during wca animation still shifts down; and in body 3, nibergen's hitbox during wca animation is nowhere to be found (i.e. it's worse in body 3 now). my summons can still hit in body 3, and the damage lines appear on the usual spot, but neither CL nor paralyse can hit at all.

attached shows (1): the boss' position and character path shifted up and (3): being able to hit in body 1 as the hitbox doesnt shift higher anymore

edit: also forgot to add (this has been a longstanding but rather negligible bug) that on my IL's client, i sometimes cannot see the paralyse lines nor the connection of skill to the boss. that is, while i can see my FP casting paralyse, i can't see the paralyse animation on the boss' head, and neither can i see the damage done by paralyse. however, it's totally fine on my FP's client where I can see the damage line as well as the skill connection to the boss.
rather small issue, just sometimes confused whether i need to move due to afk detection

 

illustration of above stated:

 

To add onto this, I feel like I have seen this elsewhere too where a f/p mage is using paralyze but I can't see their damage lines either.