Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

World Jungle Error Fix #270

Open
xenobyteOG opened this issue Aug 1, 2024 · 2 comments
Open

World Jungle Error Fix #270

xenobyteOG opened this issue Aug 1, 2024 · 2 comments

Comments

@xenobyteOG
Copy link

xenobyteOG commented Aug 1, 2024

I use the fix provided in this thread

#264

(Thanks kitsuneymg)

And I compiled a new EXE using visual studio after I downloaded the NET 4.0 SDK etc. Visual studio is free and you just loaded up the zip file downloaded of the app pre-complied files here and load the .sln file.

It still gives a warning error about world jungle after fix, that is why I am posting this, but at least it doesn't stop the app from working. If you really can't figure it out, let me know and I will email you the EXE until the author updates the app.

@Nundah
Copy link

Nundah commented Aug 8, 2024

I fixed it by deleting my campaign. To do this, start in the main menu, select your character, and choose delete. you will not delete your character, it will give you the option to delete your character or your campaign. Delete the campaign. The only issue I've found from this is that you have to replant the Thaen tree.

You can make a new character to test this if you think I'm trying to trick you into deleting your character.

@this-is-a-name1
Copy link

In debug mode I can see that injectable from all 5 world are appear in my save (in advanture mode). But this didn't happen in a new character save(only 1 world in advanture mode). As a workaround I just deny all injectable that came from the wrong world.
I add this code:if (!zoneEvents.ContainsKey(world)) {
continue;
} in RemnantWorldEvents.cs right before line 1277 if (zoneEvents[world].Any(we => we._name == injectable._name))
{
// injectable already exists
continue;
}
Appearently this solved the error message. But I can't confirm or deny whether the program work right after this modification. But at least the inject events still looks reasonable :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants