Invector integration errors with new Invector 2.5.3 update

[62qBruv]

I've just updated my Invector controller to 2.5.3 and now the Quest Machine integration has failed. It is a compile error so my game is at a standstill. The problem is with the InvectorInventorySaver.cs script and the following error message appears:

Assets\Pixel Crushers\Common\Third Party Support\Invector Support\Scripts\InvectorInventorySaver.cs(84,55): error CS1061: 'vEquipArea' does not contain a definition for 'currentEquipedItem' and no accessible extension method 'currentEquipedItem' accepting a first argument of type 'vEquipArea' could be found (are you missing a using directive or an assembly reference?)

Three error messages are shown which relate to 3 errors in the same script. I can continue with play mode if I comment out the lines that throw errors, but that defeats the purpose of the integration I should think.

I have tried this with a clean install of Invector and Quest Machine in a new project - same problem as soon as I install the integration files.

I use: Invector Basic controller v. 2.5.3; Invector Melee controller v. 2.5.3; Invector Shooter controller v. 2.5.3 and Invector AI controller v: 1.1.1

I use Quest Machine v. 1.2.8

Unity 2019.4.1f1 on Windows 10

Please can you help me to fix this - I'm really stuck. Thank you.

EDIT: Just noticed that I updated Invector AND Quest Machine at about the same time so I don't know if this is an Invector update problem or a Quest machine update problem.

[Tony Li]

Hi,

You can download an updated integration package from the Quest Machine Extras page.

It was nice that Invector 2.5.3 fixed the misspelling in their variable names (Equiped --> Equipped), but it broke everyone's code that was written on top of Invector's code. The updated package should get you running again.

[62qBruv]

Hi,

You can download an updated integration package from the Quest Machine Extras page.

It was nice that Invector 2.5.3 fixed the misspelling in their variable names (Equiped --> Equipped), but it broke everyone's code that was written on top of Invector's code. The updated package should get you running again.

Wow! You are the best. Thank you very much, it's all working again.

[Tony Li]

Glad to help!