[Fixt] Using ranged kinetic force (unarmed) deletes equipped melee weapons

[AerShiana]

Just what the title says. I've tested with the quarterstaff, steelestaff, and shieldwall staff, and if you ever use the ranged attack option with Telekinetic Warrior, any staff you have equipped is completely lost.

 

[Fenoxo]

What. the. fuck.

And it's only with staves?!

 

[AerShiana]

That actually made me go back and test. Seems to happen with any melee weapon. Not ranged though, those seem to stay put. I tested it with each staff, a beat stick, and the arc sledgehammer. All just vanished and lost to the void the instant I use a ranged kinetic warrior attack.

 

[Theron]

There was a similar report in the Feedback thread. It seems like refunding the perk then taking it again solves it. Did you take Telekinetic Warrior in last week's patch?

 

[Fenoxo]

This one might not be a quick fix, because unlike my other recent bugs, my code appears error free...

 

[AerShiana]

There was a similar report in the Feedback thread. It seems like refunding the perk then taking it again solves it. Did you take Telekinetic Warrior in last week's patch?

I did, as last week is when I made the new character. Resetting the perk, taking third eye, then resetting again to telekinetic warrior did not fix it for me. Also I've tweaked the title of the thread to properly match the issue

 

[Fenoxo]

Okay, we solved it. So telekinetic warrior works by unequipping your weapon and swapping in a rock, then swapping it back to normal, right?

Well when I tell it to unequip the ranged slot, what it does it look at the slot I provided, determined what type of item it is, and then try to run the unequip routine for that kind of item - but rocks are special case. It's one item that's used as a default for both ranged and melee - so when telling it to unequip an empty ranged slot - it looks at the rock, sees that it is tagged as a melee weapon, and attempts to remove your melee item instead of the ranged item spot I indicated.

Anyway this should be fixed next patch. Big shout outs to Geddy for helping solve this one.