How to stop Kuva Siphons from being silly

[Xarteros]

A fairly simple fix IMO. We've all had Kuva siphons that have bugged out and had Kuva spawn somewhere outside the map/in the terrain. Or, when it spawns barely a meter away from the Siphon and gives you less than a second to react. A simple fix:

Make each Kuva cloud take the same amount of time to reach the Siphon, regardless of how far away it spawned. Let's just use the example time of 10 seconds. If the Kuva spawns very close to the Siphon, you have 10 seconds to react to it and snag it, but it will move very slowly. If the Kuva spawns on the other side of the map, it would travel very fast, but still only take 10 seconds to reach the Siphon.

Any Kuva that doesn't reach the Siphon after 10 seconds is deleted, and that Siphon arm is reset. This means that Kuva that gets stuck somewhere will eventually just be removed, and you get a new one from somewhere else. DE could also make the server send back data from Kuva that got deleted from bugging out, so they can just hone in on the glitches to the exact coordinates and fix them promptly. It's a win-win-win-win-win-win. Everybody wins.

Again, that 10 seconds is just an example. It should be whatever is considered fair, with reflection taken from the average time it takes for Kuva to reach a Siphon.

[Licitaqua]

1 hour ago, Xarteros said:

A fairly simple fix IMO. We've all had Kuva siphons that have bugged out and had Kuva spawn somewhere outside the map/in the terrain. Or, when it spawns barely a meter away from the Siphon and gives you less than a second to react. A simple fix:

Make each Kuva cloud take the same amount of time to reach the Siphon, regardless of how far away it spawned. Let's just use the example time of 10 seconds. If the Kuva spawns very close to the Siphon, you have 10 seconds to react to it and snag it, but it will move very slowly. If the Kuva spawns on the other side of the map, it would travel very fast, but still only take 10 seconds to reach the Siphon.

Any Kuva that doesn't reach the Siphon after 10 seconds is deleted, and that Siphon arm is reset. This means that Kuva that gets stuck somewhere will eventually just be removed, and you get a new one from somewhere else. DE could also make the server send back data from Kuva that got deleted from bugging out, so they can just hone in on the glitches to the exact coordinates and fix them promptly. It's a win-win-win-win-win-win. Everybody wins.

Again, that 10 seconds is just an example. It should be whatever is considered fair, with reflection taken from the average time it takes for Kuva to reach a Siphon.

i would not be oposed to this idea, but having kuva spawn far enough away from the syphon would cause it to move far too fast for some players to hit, you would have to increase teh time to something that would give it a decent speed while far away but still not too fast you miss it

[Xarteros]

22 hours ago, Licitaqua said:

i would not be oposed to this idea, but having kuva spawn far enough away from the syphon would cause it to move far too fast for some players to hit, you would have to increase teh time to something that would give it a decent speed while far away but still not too fast you miss it

Well, to be fair:

23 hours ago, Xarteros said:

Again, that 10 seconds is just an example. It should be whatever is considered fair, with reflection taken from the average time it takes for Kuva to reach a Siphon.

Kuva shouldn't be spawning more than X meters away. I think sometimes it just randomly spawns a few tiles over, which is just not a good plan in general. I think that this is where half the spawning glitches come from.

As an optional fix, make the Kuva cloud slow down as it gets closer to the siphon. That way, if it's super far away it speeds closer, but rapidly slows down when it's actually getting near the Siphon.