Doctor Archive
Thread: REZ still broke?
I've had mixed luck with rez as well. Sometimes it works on the first try and sometimes it takes several tries. I didn't have a chance to do extensive testing but some things I've thought about or noticed:
1. Is consent always required now for everyone? Before you could rez groupmates without getting consent. Only people you weren't grouped with and Jedi required consent. In several cases where my rez didn't work on the first try one of the things we did was grant consent even though we were grouped, so I'm not sure if that's what did it or not.
2. When the rez didn't work, I still got that windup bar and it filled up just like it does when it works with no error messages or anything indicating why it didn't work.
3. Another possibility I've thought of is maybe I was interrupted if I was hit by something while that windup bar was fillingup. I thought they said something about specials being able to be interrupted during windup phase. The times I had trouble were usually while there was still fighting going on.
4. On the consent issue, I think they may have finally fixed the consent list or at least done something to it. I noticed yesterday when healing my husband's Jedi he got the message that I was already on his consent list when he tried to add me. Before this he had to add me to the list after every log in even though I"m on his list multiple times.
5. We are now getting a rez timer, finally. When someone dies they get the message that they have 30 minutes to be rezzed and I think they get an update every 10 minutes.
padme1967 wrote:
I can rez but the stabilizer doesn't seem to do anything. I tried to remove dizzy and stun from myself and I didn't get a sys message but I did see an animation that I was injecting myself. I think the dizzy stun state I got was bugged though as it remained for over 15 minutes up to the time I logged. I tried traveling and it still wouldn't go away. I bugged it. Just wondering what the rate of success is on stabilizers and what if any sys msg we get?
Thanks
Stabilizers seem to work fine, assuming your not dealing with a bugged state effect.
SioBabble wrote:
What bothers me about rezz is that if you die and clone, your faction status is changed to on leave, but you have no option to change that status except to find a recruiter somewhere to take you off of leave. The option to change your status to heal, for wounds or a rezz, no longer exists.
So groupmates who died after you are SOL, and because decay is bugged in PvE factional combat (sometimes you decay, sometimes you don't) it's another case of the system griefing players.
Needless to say, this seriously blows, particularly in PvE factional combat where there is no possiblity of an exploit against another player. Heaven forfend we should geta microscopicedge on a novatrooper twice our level.
The one time I have used rezz since the CU, and the factional stars were aligned, it worked as advertised.
This was incorporated to help stop 'clone camping'. If this wasn't in place and you were SF when you died, you could be killed again and again while loading into the game. Imagine the decay from that....
I have been asked to rez several times Post-CU and it must be frustrating to the player-corpse because I have to ask:
Are you imperial?
Are you jedi or spec forces?
I'm a rebel on leave and cannot rez in those cases. So I haven't had the opportunity to test this out yet ![]()
Works for me, Neutral Doctor. The only time it doesn't is when someone is combatant, even after consent is applied.
This is the error I get if the person is combatant "Invalid Target".
I also found that a rez can be broken. It's one of those moves that requires "NO MOVEMENT" or other action during the "Rez Time". If you move or perform another action during the "Rez Timer" it will fail but give you no warning.
*"Rez Timer" - You will see the "Rez Timer" pop up in the middle top portion of your screen like a "System Message". Except that it looks like a progress bar that is filling. If anything interrupts this "Timer" the rez will fail & you will sit there & wonder why it failed.
Hope this helps.
Chek wrote:
This was incorporated to help stop 'clone camping'. If this wasn't in place and you were SF when you died, you could be killed again and again while loading into the game. Imagine the decay from that....
Again, why does this rule affect PvE combat? I can see the need for this in SF situations, where immature little snots actively search for ways to grief other immature little snots, but why should PvE combat be so affected?
Prior to the CU if you were on leave and sought to heal or rezz a combatant, you'd get the warning message and the option to change to combatant status. Why is this gone post CU? Now you can no longer buff a combatant when you are on leave, and that was explicitly permitted pre CU.
Rez seem's a little buggy . Timer generates and then no rez afterwards.
also - formerly when a jedi was rezzed - he lost little to no xp - now however it seems maximum xp is lost
You may need your target to give you /consent still. Had the same problems until they did that.