search

Aelto / tw3-random-encounters-reworked

Add randomly generated monster contracts, bounties, ambushes and hunts to the game. Dynamically change the vanilla spawns for unique and varied playthroughs. Simulate an ecosystem and a food chain. Add dynamic events to give more weight to your actions
https://aelto.github.io/tw3-random-encounters-reworked
62 stars 13 forks source link

Changing mod version to other than 0 causes crashes, but setting it to 0 dissables the mod. #169

Closed DOOMOlivera closed 1 year ago

DOOMOlivera commented 1 year ago

If I change the setting 'mod version', the one you say I must not change, the game will crash when playing. But if I let that setting in 0, then the mod won't work. No random enemies will spawn, no ambushesh will happen, not even the startup notification where it welcomes you to the next gen update version of the mod will show.

When setting the general settings to default, the mod version will be set to 2.12 . But when the game crashes and I check the settings again, the mod version has been changed to 3. Setting the mod version to 3 right from the start doesn't fix the crashes, and by the timing of the crashes I think the game crashes the moment it spawns an enemy/an event happens... etc.

I've had a few crashes through the day, and I was able to encounter some monsters spawned by the mod, but now I can't play more then 1 minute without the game crashing.

Also, setting mod version to 0 will cause Geralt to say 'Ready for one hell of a ride', then the hud will dissapear and I will have to pause and resume the game to keep playing. This is fixed by changing the number of mod version, but as I said that will cause the game to crash. So until this is fixed I think I'll have to dissable the mod.

Atarashi-Daten-Shi commented 1 year ago

The mod is bugged completely still. Changing Any of the settings will cause the game to crash. It's best to wait for a hotfix. Atleast we got this ported to Next-Gen.

Aelto commented 1 year ago

Closing for inactivity and because it probably related to the next-gen update and script incompatibilities