Jedi Archive
Thread: BUG WORKAROUNDS
NOT EXPLOITS.
There's several bugs currently that have some workarounds that are useful-- I thought it'd be a good idea to have a comprehensive list of them, to help all-- many will be common knowledge among those who frequent these boards. This is by no means complete, but a work in progress... There are many more that I've come across on this board that I can't find now.
Any help compiling the list would be great.
- Target slides after knockdown: Put target on /follow
- Cannot Knockdown Recovery while knocked down: Best results personally have been not to use a hotkey; instead take the half a second to type in /kno and workaround lag this way.
- You heal/infusion your target rather than yourself: Replace your hotkeys with macros that run /forceheal self; or /forceinfusion self;
- Some modifiers on sabers are lost after crossing server boundaries: Unequip saber, open saber, remove all crystals/pearls, close window, re-open saber, put all crystals/pearls back in.
- Healing animation seems to 'root' you while healing others: Start moving before you hit the heal button.
- PSG's not working: (Not a bug, but advice) These decay quickly. Frequently check the condition of your PSG.
- "Cannot see target" message while you are on top of or next to target: Move to flat land, or ???????
- Some defensive mods are not applied correctly/are lost after traversing server boundary: Unequip/Re-equip your saber
The lag when knockdown is probably the one that will help me. Nice to see something positive on the Jedi forums for once.
But yes, useful info here.
Maelstrom_Raine wrote:
Hehe, too bad I like to Powerattack after I kd someone.. can't do that while following them sliding a mile
But yes, useful info here.
Me too, no workaround for them being outta range after a KD/slide though that I know of though for an quick powerattack
The "Cannot see target" or "Target out of range" when standing next to them one is awkward. Sometimes its just dodgy Line of Sight programming. Other times the target is not actuallywhere you think it is. From what I can work out (and this is mainly from NPC BH marks that do this a lot) - if lag affects you at the wrong time, or an NPC is running against a wall for a long period of time, the target is not actually at the place it looks like it is on your screen. Unfortunately, /follow seems to also be a client side command, and hence makes you move to the (wrong) position your client thinks the target is.
The only way I have found to counter this is to guess where the target is. For example, if it was moving North, and you were following, then you stop when you reach it and get that message, burst runNorth and you should find yourself hitting it again (often from like 80m away with a melee hit - go figure). You will then find the target suddenly warps the distance and is standing next to you again.
As I said - fiddly
Unfortunately following the BH won't fix the kd slide problem. I am already doing this with very little success.
Good post though, and these things may work for others. Try them out for yourself.