Thargoid invasion - Next target systems?

I only did this once or twice, but I just blocked the first one in the contacts list and this seemed to do the trick.

But it's an annoying workaround since I also want to have that CMDR unblocked soon after. So that when he also leaves the instance and comes back, he might come back to the instance I created a little earlier. He could be a Hydra killing ace for all I know, we need all hands on deck. Or he could be wonderfull person that I don't want to create instance problems for.

I don't remember exactly now, but I think once at least another CMDR joins the new instance, it's safe to quit a second time to menu to unblock, and then when joining again you will be in the new instance still. Will need to test this with the first opportunity.
If it helps. I was in Awara yesterday and was also having rubber-banding issues. So if it was me you blocked you’re safe: I am very far from a Hydra killing ace!! 😂
 
I don't remember exactly now, but I think once at least another CMDR joins the new instance, it's safe to quit a second time to menu to unblock, and then when joining again you will be in the new instance still. Will need to test this with the first opportunity.
I don't think you need to quit to the menu to unblock, can't you do it from the contacts history panel?
 
I don't think you need to quit to the menu to unblock, can't you do it from the contacts history panel?
Nah, the option to block is there, but not to unblock. Here's how the menu looks after blocking a CMDR:

Screenshot_0038.jpg
 
Who do you block, out of interest? Every other CMDR in the instance or just one (or two)?
I only did this once or twice, but I just blocked the first one in the contacts list and this seemed to do the trick.
If it helps. I was in Awara yesterday and was also having rubber-banding issues. So if it was me you blocked you’re safe: I am very far from a Hydra killing ace!! 😂

IF an instance gets bugged, i try a relog or a low wake then wake back.
If i keep getting the bugged instance, i block a single random commander in that instance then i relog again.
Usually i get a good instance, sometimes an existing one, sometimes a new one.
Then i go back to menu (no need to Quit, a simple Esc or P is enough, and i unblock the commander from the Social menu)

The need to block someone to switch instance comes from the fact that some commanders dont realize the instance is bugged and keep staying in that instance and keep it alive & bugged.
 
Hmm, looks like if a hydra killed far away from the port/station (>30kms?) the instance cannot be completed.
This Thargoid war is full of annoying bugs. ;)
FDevs, we need an update and we need it now.
 
Muruidooges closing soon, followed by a quite nice-looking progress gradient from which around 12–13 Invasions plus that one Alert are projected to finish. Great job to those at HIP 21991; it is exactly where it needs to be to finish in good time, while I also note that it must finish this cycle to count for anything. Nihal returns!

Top targets at 00:20 13th February 3309:
Muruidooges Invasion 94% — Hadad 18 Ly, 4 ports, 7321 Ls outpost attack
Nu Guang Invasion 82% — Raijin 19 Ly, 5 ports, 43 Ls planet attack, 44 Ls starport + 1039 Ls outpost damage
H Puppis Invasion 70% — Hadad 25 Ly, 3 ports, 320 Ls planet attack, 568 Ls outpost damage
HIP 21991 Alert 66% — Taranis 26 Ly, 1182 Ls starport
Orong Invasion 40% — Oya 27 Ly, 2 ports, 1044 Ls outpost attack, 9 Ls planet + 17 Ls outpost damage
Cao Tzu Invasion 38% — Taranis 21 Ly, 3 ports, 2225 Ls planet attack
Minawara Invasion 34% — Oya 23 Ly, 3 ports, 412 Ls planet attack
Hyades Sector AV-O b6-5 Invasion 30% — Taranis 23 Ly, 1 port, 37 Ls planet attack, 22 Ls planet damage
HIP 6913 Invasion 24% — Oya 20 Ly, 4 ports, 2255 Ls planet attack
Bi Dhorora Invasion 22% — Hadad 18 Ly, 3 ports, 1856 Ls planet attack


Regarding blocking a name temporarily to achieve for yourself a different zone—I have been doing it from Social; less convenient than if one could do it from the Comms panel, though definitely more convenient than having to exit necessarily. Either way though, this is something I should have added to the Feedback thread! Clearly the block-feature enables the notion of getting a fresh zone, while also clearly not being intended for that, thus justifying an actual feature to get a fresh zone explicitly.


Hmm, looks like if a hydra killed far away from the port/station (>30kms?) the instance cannot be completed.

Surely this is one of the more easily-solved situations, at least! When I have room to choose the general trajectory while circling an Interceptor, I have been aiming it in the direction of the port, using the compass direction to do it.
 
Surely this is one of the more easily-solved situations, at least! When I have room to choose the general trajectory while circling an Interceptor, I have been aiming it in the direction of the port, using the compass direction to do it.
Circling? 5 Condas with 6 shards each making Hydra sht its pants and running away. :ROFLMAO:
 
AFAICT the "fix" added for interceptors fleeing makes them turn around and head back if they reach 60km.
It shouldn't affect the scenario completion, if it happened then it more than likely would have happened regardless of the distance.
 
AFAICT the "fix" added for interceptors fleeing makes them turn around and head back if they reach 60km.
It shouldn't affect the scenario completion, if it happened then it more than likely would have happened regardless of the distance.
When was the fix applied? Three days ago we fought a hydra at ~120km from the port.
Even 60 is too much. If it stays there nobody would be able to find it. They need to turn it back at 20km.
 
They don't just go out to those extreme distances on their own, someone has to kite them. Usually it's a cmdr because NPCs don't survive that long, but occasionally it's a bugged HE seeker that continues off into infinity.

Something makes them kite away.
I've seen it quite a lot last weekend and they were chasing nothing - no npc, no cmdr, nothing visible anyway.
 
Victories in Muruidooges and Nu Guang! For the remainder of the cycle we should be fine with the Alert in HIP 21991, 5–6 more Invasions, and we are almost certain to have a few systems reaching 33% at which any surplus activity can be directed. Kaurukat returns!

Top targets at 09:00 13th February 3309:
H Puppis Invasion 80% — Hadad 25 Ly, 3 ports, 320 Ls planet attack, 568 Ls outpost damage
HIP 21991 Alert 72% — Taranis 26 Ly, 1182 Ls starport
Cao Tzu Invasion 42% — Taranis 21 Ly, 3 ports, 2225 Ls planet attack
Orong Invasion 42% — Oya 27 Ly, 2 ports, 1044 Ls outpost attack, 9 Ls planet + 17 Ls outpost damage
Minawara Invasion 38% — Oya 23 Ly, 3 ports, 412 Ls planet attack
Hyades Sector AV-O b6-5 Invasion 32% — Taranis 23 Ly, 1 port, 37 Ls planet attack, 22 Ls planet damage
HIP 6913 Invasion 26% — Oya 20 Ly, 4 ports, 2255 Ls planet attack
Bi Dhorora Invasion 24% — Hadad 18 Ly, 3 ports, 1856 Ls planet attack
 
IF an instance gets bugged, i try a relog or a low wake then wake back.
If i keep getting the bugged instance, i block a single random commander in that instance then i relog again.
Usually i get a good instance, sometimes an existing one, sometimes a new one.
Then i go back to menu (no need to Quit, a simple Esc or P is enough, and i unblock the commander from the Social menu)

The need to block someone to switch instance comes from the fact that some commanders dont realize the instance is bugged and keep staying in that instance and keep it alive & bugged.

I'm having to block the Richards who deliberately sit in the docking pads. Had one yesterday who just sat there in the large pad of a planet port and wouldn't even answer direct messages. Either they AFK'd or were just sitting there laughing. Meanwhile the other large pad left is being used by CMDRs with damaged, ailing, and dissolving ships, there are murderflowers and Scouts taking pot shots, and so on.

Perhaps they were perusing the mission board, but to sit there continuously for more than 30 minutes is definitely leading me to the conclusion they did this deliberately. Blocked.
 
Perhaps they were perusing the mission board, but to sit there continuously for more than 30 minutes is definitely leading me to the conclusion they did this deliberately. Blocked.
If they had a large ship with lots of cargo space (>80T), they were probably waiting for the mission board to flip so they could get completely full.
 
If they had a large ship with lots of cargo space (>80T), they were probably waiting for the mission board to flip so they could get completely full.

Doing that is even worse, as it blatantly ignores the impact on the CMDRs who are shooting at the goids and being shot at. But I'm not buying that as an explanation - if waiting for a board to flip, they had ample opportunity to respond to a DM with an explanation.

Nope. Blocked.
 
Having the station services menu open means the comms panel isn't visible / DMs aren't shown.
See "Doing that is even worse, as it blatantly ignores the impact on the CMDRs who are shooting at the goids and being shot at."
No wish to further derail this excellent thread, so I'll shut up about it now.
 
Victories in Muruidooges and Nu Guang! For the remainder of the cycle we should be fine with the Alert in HIP 21991, 5–6 more Invasions, and we are almost certain to have a few systems reaching 33% at which any surplus activity can be directed. Kaurukat returns!

Top targets at 09:00 13th February 3309:
H Puppis Invasion 80% — Hadad 25 Ly, 3 ports, 320 Ls planet attack, 568 Ls outpost damage
HIP 21991 Alert 72% — Taranis 26 Ly, 1182 Ls starport
Cao Tzu Invasion 42% — Taranis 21 Ly, 3 ports, 2225 Ls planet attack
Orong Invasion 42% — Oya 27 Ly, 2 ports, 1044 Ls outpost attack, 9 Ls planet + 17 Ls outpost damage
Minawara Invasion 38% — Oya 23 Ly, 3 ports, 412 Ls planet attack
Hyades Sector AV-O b6-5 Invasion 32% — Taranis 23 Ly, 1 port, 37 Ls planet attack, 22 Ls planet damage
HIP 6913 Invasion 26% — Oya 20 Ly, 4 ports, 2255 Ls planet attack
Bi Dhorora Invasion 24% — Hadad 18 Ly, 3 ports, 1856 Ls planet attack
May I suggest any CMDRs fighting at Taranis prioritise Hyades Sector AV-O b6-5 above Cao Tzu? Hyades Sector AV-O b6-5 has one remaining port so this week is our last chance to effectively defend it (I am assuming it would lose the last port this tick even if any progress over 33% was retained) . its only 3.3 LY from Cao Tzu so if Hyades Sector AV-O b6-5 finishes, the party could head to Cao Tzu knowing if it doesn't complete, we get another go next week with some progress already started. I've been in Hyades Sector AV-O b6-5 killing scouts most the week (having read Alek's suggestion to prioritise) and i can stack missions for both systems quite easliy. feel free to join me :)
 
May I suggest any CMDRs fighting at Taranis prioritise Hyades Sector AV-O b6-5 above Cao Tzu? Hyades Sector AV-O b6-5 has one remaining port so this week is our last chance to effectively defend it (I am assuming it would lose the last port this tick even if any progress over 33% was retained) . its only 3.3 LY from Cao Tzu so if Hyades Sector AV-O b6-5 finishes, the party could head to Cao Tzu knowing if it doesn't complete, we get another go next week with some progress already started. I've been in Hyades Sector AV-O b6-5 killing scouts most the week (having read Alek's suggestion to prioritise) and i can stack missions for both systems quite easliy. feel free to join me :)
I hope we can defend both, Cao Tzu and AV-O! Let's fight!
 
They don't just go out to those extreme distances on their own, someone has to kite them. Usually it's a cmdr because NPCs don't survive that long, but occasionally it's a bugged HE seeker that continues off into infinity.
They do. Sometimes a hydra just runs to the black that you can hardly catch up using perma boost in Krait.
Another issue I noticed when I bump it at boost speed sometimes it's thrown at 8-10km away.
 
Back
Top Bottom