[Arbitration host migration and Eidolon lure malfunction]

To preface this, I might be a bit salty as the last two hours of Warframe have been one annoyance/disappointment after another. So apologies for any snarky remarks or anything similar.

First the Eidolon lure bug I've been experiencing recently, and it's a pretty simple one at that: Eidolons (Gantulyst in my case) teleport away after loosing a synovia, despite the fact that there are charged lures present. Six charged lures, no less. And it happened thrice in a row. I'm rather new to Eidolon hunting so I'm unsure of whether this is a long-standing issue, is it a new thing, or mine was just a fluke. 

Either way, annoying, but no biggie at the end of the day.

Now, for the real deal: Arbitrations.

There are three different instances of three different bugs/weird things occuring in the span of less than two hours. First glitch was on an Excavation arbitration where we simply didn't receive any awards, except Vitus essence. As it's Excavation, you don't get a screen asking whether if you want to continue or leave, there just weren't any sculptures or endo awarded. But since we did get our Vitus essence, the arbitration was, of course, locked.

The second issue I experienced might be me not paying any attention, but I'm putting here anyway just in case. There was an Interception arbitration against corpus (Don't recall planet, but I do recall it was on top of a Nightmare node). I have Chroma strength and some weapon I don't recall. I join, wait a minute, nobody joins me. So I leave, only to see that the arbitration is now Defense against the Grineer on Lua. Again with Chroma strength and a weapon I don't recall. Since I don't recall the weapon to see if it was also the same, I can't for certain write this off as a glitch. But at the same time I, for certain, didn't start an expired arbitration that switched to a different one while I was still in the mission. Arbitrations don't refresh that quickly anyway.

Third issue occurs on previously mentioned Grineer Defense arbitration. And it includes Public Enemy number 1: Host migration.

Long story short, first person dies at wave 15, nothing special. Then the second person (Whom I've marked as the culprit in this situation) dies at the beginning of wave 19. He also turned out to be the host. The last person and I learn that he is the host after our culprit leaves right before we kill the last 4-5 enemies of the wave. We get a host migration, we load back in and... there are no enemies. It's just me, the other player and the operative. We are unable to complete the mission, as the game requires us to kill enemies, enemies that no longer exist. So by that point I was fuming and reported the player that left (Their name is Guilty-As-Charged or Guilty_As_Charged), told the other player the name of our culprit, more out of spite than anything else, and left. Of course, with no rewards whatsoever.

Yes, I realize the "culprit" might not have intended to cause us any trouble, but the point of time he left was a bit too close for me to not suspect something. I've been wary of people doing stuff like this ever since I got burned multiple times by people switching their choice of staying in a mission to leaving a split second before the timer runs out, leaving me alone to fend for myself (Which usually happens on Hydron, with unleveled frames and weapons. You can guess how well that goes). Since then I've learned that people are not above ruining the game for other players for no reason whatsoever. And you cannot report them either as per the rules, they have done nothing wrong. (The idea here is that people bait you to stay in a mission by picking the "Continue mission" option and changing it at the last second, before you can react.)

Again, apologies if I appear to be aggravated. And huge apologies to GuiltyAsCharged in case they didn't actually have any malicious intent. Otherwise shame on you.

[Maggor Towsun rogue cube]

There's a stray cube that shows up around the chest area on slender warframes, in this case Trinity's Strega skin.

Display settings are on the low preset, Dx11.