Sorry.
"Intellectuals solve problems, geniuses prevent them."
-Albert Einstein
Also. your "fix" is fine in a junk profile but not in the scale of profile i'm making. The reason, i have to block the code off in sections for different scenarios. It can't just be one long running mess of scattered ifs.
I'll explain it as simply as possible.
My profile does the following scenarios.
Scenario 1: Fresh game
Load new quest. starting in town. it does normal broken blade quest line and gets into the festering woods.
Once there it starts the walk through the zone. visiting every tile that can have a special event object or dungeon entrance. First entering CoA then entering HR then leaving the game. (doing all special events it encounters along the way before clearing the dungeons)
Scenario 2: Resumes Game
Resumes game from inside HR
Clears HR exits dungeon
depending on where you exit (where on the map you are of the 3 possibilities) it takes 3 possible paths to go back to CoA side and find the entrance to CoA
clear CoA exit game
Scenario 3: Resume Game
Same as scenario 2 but logs in inside CoA and clear it, then finds HR and clears it.
rinse and repeat.
because of this, it's a varying profile, it's not a set do this in this order profile. nested blocks of code are required.
Code:
if (in town){
use waypoint
}
// resumed game
while (in coA){
clear dungeon
exit
if (location1){
walk path 1 looking for hr
if (hr1 found) {
enter dungeon clear leavegame
}
if (hr2 found) {
enter dungeon clear leavegame
}
if (hr3 found) {
enter dungeon clear leavegame
}
}
// repeat for location 2 and 3 of coa
}
// repeat for if they resume game inside WR except coa is the target
// Normal quest line here do the starting quest and make way to festering woods
// walk to all the different tiles of the map and explore dungeons etc.
//
//
//The breaking apart the nested stuff into 3 different ifs will work for the standard quest part (fresh from new game) but it wont for the resume parts because those are inside a while (or if doesn't matter). The single while / if makes any of the code inside (working code thats used in the standard run) not work because it triggers that bug.
hopefully some of that made sense. so yeah there's a work around for "some" of it. but not all of it. hence this thread.
