Problem with using smuggler grenades. It seems to cause an error that forces me to reload the game

[Kitbees]

 

[Gedan]

What enemies were you trying to fight when this happened? I've been trying to replicate it but have thus far been unsuccessful.

 

[Theron]

Anything, in my experience. Happens with both a converted save (Zil Male, Milodan) and a new one (Gryvain Techie).

 Version: 0.9.020-PUBLIC#2544 Message: Cannot read properties of null (reading 'getClassName') Stack:
TypeError: Cannot read properties of null (reading 'getClassName')
    at e.value [as Implementor] (https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:9869635)
    at e.value (https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:10177988)
    at o.value (https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:10030632)
    at Object. (https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:10022739)
    at https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:12107781
    at s (https://www.fenoxo.com/play/TiTS/release/main.d13d09cd.js:1:10359767)

If it got picked up by the automatic crash reports, it's possible it got fixed by someone else.

 

[Sam_Cinders]

Had to make an account but can confirm this is literally any time you use the Smuggler's grenade power at any time in the game, particularly against multiple enemies such as the Black Void pirates or the Gold Myr captain & daughters - same critical error, "getClassName" and etc.

 

[Animefan666]

Had to make an account but can confirm this is literally any time you use the Smuggler's grenade power at any time in the game, particularly against multiple enemies such as the Black Void pirates or the Gold Myr captain & daughters - same critical error, "getClassName" and etc.

According to the patch notes, this has been fixed. Update to v0.9.021 and see if it persists.

 

[Sam_Cinders]

According to the patch notes, this has been fixed. Update to v0.9.021 and see if it persists.

Cheers, was checking for updates yesterday and was still 0.9.020, and with all the unanswered threads, wasn't quite sure it it got picked up on.

And yes, it's been fixed - cheers, devs & patchers.