I just feel like reviver hive is made too complicated.
It's bad when you as a developer make something so complicated that even you as a maker can not control it.
Othervise it would be already fixed.
It has only one purpose - to revive you, and it fails to do that too often.
I'm sorry guys but there is an EASY fix for this by just using a simple if/then coding option:
1) Get rid of all the "for show" effects until you figure them out behind the scenes
2) If Agent has revive hive and agent goes down then agent gets revived
Stop trying to be cute and just make it do its job!
Also - if you want to track down a situation where it works 100% of the time...try to kill yourself while doing the raid - revive hive NEVER fails in this situation
Pride.
I have been installing, maintaining, and troubleshooting electro-mechanical systems since 1990 when I was an 18 year old in charge of $33M of equipment in the US Navy. I have seen all manner of problems, solutions, and methods of troubleshooting. I know that there is a tipping point in all troubleshooting/corrective maintenance activities where replacement becomes more efficient than continuance of corrective measures. I am certain that from inception of the system until now you have invested hundreds, if not thousands of man hours into this problem. Eventually every fix becomes another problem. Every move becomes the next weak point. All the while your problem is intermittent. Ghosts in the machine and all that.
While I appreciate your explanation and the history of this problem (which i am certain is a white-washed glossy version of the actual trouble this has caused you) might i suggest another avenue?
Replace the entire system. Seriously. Nullify the visual or interactive nodes and create and entirely new system off to the side.
I know this like I am making it simpler than it seems to you on the inside, but I assure you the exact thing that is often needed is a new set of eyes asking relatively stupid question and/or making equally stupid suggestions. We, as troubleshooters, have a tendency towards tunnel vision. We become so engrossed in fixing the problem as a mental exercise and a demonstration of our magnanimous superiority that we forget the simplest of facts: it is still broken. Admitting this is the hardest troubleshooting step to achieve.
We might be at the point where pride is the problem. The coders and devs are prideful of their idea and want to make it happen come hell or high water...but it is still broken. The troubleshooters have sunk hours upon hours into fixing the problem and they want to prove they can fix it....but it is still broken.
You should get new eyes on the problem and stop looking to add another layer of band aids, twisty ties, and bubble gum to the broken monstrosity. Start anew. It is the Chinese finger lock of techs. Trying harder will make it worse.
^
Exactly my thoughts. They just don't realise how simple function reviver hive has - to revive you if you are down and it is not on cooldown.
I am ok if it still fails if it's shooted by enemies, or if you aim poorly and throw it so there is an obstacle between hive and your downed mate... but why is it failing so many times without any obvious reason? It is because they are inventing the wheel at this point, and there is no need for hive to be that complicated.
If they are not able to fix after battle screens for weeks now I don't think they even work on hive problems any more to be honest.
My buddy stumbled upon a seemingly sure fix for when the revive hive is constantly not working so I thought I'd share for those having problems and also to point out the potential cause for the issues to the dev team. It seems if you unequip all mods including batteries, basically leaving the hive mod slots completely empty it starts working perfectly. When he has it constantly failing to work he did this and has no issues immediately following emptying the mod slots. It appears one of (if not THE) root cause for all the current issues are the mods for the revive hive.
Recently the hive repeatedly failed during the RAID for multiple player. This occurred at the end of a phaze on Razorback when no one was being shot and no status effect were in effect. It happened to multiple players reviving comrades as well as auto-revives. It was deployed then did absolutely nothing.