Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Hi, I tested again with a clean setup.

I verified the Steam game files, deleted and reinstalled Didnapper 2, then installed only Overkill v0.16.1 again.

I also tested with a new/clean save file, not my old save. The same errors still happen.

Game version: Didnapper 2 v1.2.5 Steam version Mod version: Overkill v0.16.1 Title screen shows: Overkill 2 Mod (v0.16)

Video showing the issue: https://youtu.be/AQ-M4FpeMh8

Problems shown in the video / screenshots:

  1. Call Ally error When I use Call Ally and select any character, I get this error:

[PDX_EventCaller] The "RunEventPage" plugin command was called with "NaN" as event ID but this event doesn't exist.

  1. Chastity / Struggle TypeError When I use the Chastity / Struggle menu, I get this error:

TypeError: Cannot destructure property 'baseDiff' of 'undefined' or 'null'.

  1. Binding error I also get this message in the Chastity menu:

Failed to get binding properties: Binding None not found!

This does not seem to be caused by my old save file, because I tested with a new/clean save after reinstalling the game and the mod.

Please let me know if you need my logs from the www/logs folder or my save file.

Thanks for the video, I was able to reproduce the chastity struggle error but my game does not seem to ever do the call ally error. We are investigating. Your logs would be useful to us if you're able to post them.

I've just uploaded a new version that should fix the two issues you brought to our attention, thank you again for reporting. https://kombatwombat.itch.io/didnapper-2-mod-overkill-2/devlog/1524794/0162

(+1)

Thank you for the quick fix!

I haven’t tested it yet, but I will download the new version and test Call Ally and Chastity / Struggle again. If I still get any errors, I will post my logs from the www/logs folder.

Thanks again for looking into it.

(+1)

Thank you, I tested Overkill v0.16.2.

Call Ally and Chastity / Struggle no longer give me errors now, at least from what I tested so far. It looks like the update fixed the issues.

Thanks again for the quick fix!