3.70 star(s) 95 Votes

FearCore

New Member
Jun 14, 2019
1
1
I will let you know when we know more
i have a fix, i got the error too. so i went into debug to figure out the problem. this short of it is that the game tries (and fails) to dispose of a nil value.
WARNING: this fix does not fix the underlying problem just prevents it from cousing a crash and might have unintended consequences. though from what i see there is no problem currently with it.

how to do:
go to "Pokemon Hentai Version 0.519 A\Plugins\Customizable Level Caps" and open "main.rb"

go to line 157, should look like this:
Code:
156 else
157        $viewport1.dispose
158        $currentDexSearch = nil
159        $close_dexnav = 1
160        $game_switches[NavNums::Dispose] = false
161        pbSEPlay("GUI menu close")
162        return
163 end
simply ad this piece on "$viewport1.dispose" add "if @viewport"
long of short, it checks if the value is nil and makes it do nothing if it is. now the line should look like this with this piece added:
Code:
156 else
157        $viewport1.dispose if @viewport
158        $currentDexSearch = nil
159        $close_dexnav = 1
160        $game_switches[NavNums::Dispose] = false
161        pbSEPlay("GUI menu close")
162        return
163 end
this worked for me at least, though do give me feedback on it.
 
  • Heart
Reactions: blubbervink

blubbervink

Well-Known Member
Oct 15, 2018
1,255
408
i have a fix, i got the error too. so i went into debug to figure out the problem. this short of it is that the game tries (and fails) to dispose of a nil value.
WARNING: this fix does not fix the underlying problem just prevents it from cousing a crash and might have unintended consequences. though from what i see there is no problem currently with it.

how to do:
go to "Pokemon Hentai Version 0.519 A\Plugins\Customizable Level Caps" and open "main.rb"

go to line 157, should look like this:
Code:
156 else
157        $viewport1.dispose
158        $currentDexSearch = nil
159        $close_dexnav = 1
160        $game_switches[NavNums::Dispose] = false
161        pbSEPlay("GUI menu close")
162        return
163 end
simply ad this piece on "$viewport1.dispose" add "if @viewport"
long of short, it checks if the value is nil and makes it do nothing if it is. now the line should look like this with this piece added:
Code:
156 else
157        $viewport1.dispose if @viewport
158        $currentDexSearch = nil
159        $close_dexnav = 1
160        $game_switches[NavNums::Dispose] = false
161        pbSEPlay("GUI menu close")
162        return
163 end
this worked for me at least, though do give me feedback on it.
I will forward it
 

Renootje

New Member
Aug 30, 2018
12
2
Needs a certain level of affection. Guess you missed out on some.
i missed everything after the ship. I talked to her at the ship and then she sayd something about bringing something to asha and from there on out i cant find her annymore. What did i do maybe someone knows i completed the hole event list at an older version and then updated to this version i only needed to do her missions.
 

blubbervink

Well-Known Member
Oct 15, 2018
1,255
408
i missed everything after the ship. I talked to her at the ship and then she sayd something about bringing something to asha and from there on out i cant find her annymore. What did i do maybe someone knows i completed the hole event list at an older version and then updated to this version i only needed to do her missions.
I dunno. Check the affection list for seras in the guide
 

slykoru

Newbie
Feb 20, 2017
33
39
Man, I didn't check the guide when I started playing the game, guess I'm just completely locked out of Sera's content since I didn't think to check if she randomly had new dialogue about a fight? RIP
 
  • Angry
  • Sad
Reactions: bobob23 and Sossse

SINtax EroRR

Active Member
Game Developer
Jun 21, 2017
507
2,299
Man, I didn't check the guide when I started playing the game, guess I'm just completely locked out of Sera's content since I didn't think to check if she randomly had new dialogue about a fight? RIP
Exhausting all dialogue and double-checking an NPC's options is a common feature in RPGs. You make it sound like you've never played one before.
 

Lewyn Collins

Engaged Member
Nov 16, 2021
3,113
3,679
Exhausting all dialogue and double-checking an NPC's options is a common feature in RPGs. You make it sound like you've never played one before.
Well to be fair, most people won't just speak to every single npc, much less check it twice. In pokemon specifically, npcs only have one dialogue. If they are trainers, they have 2: one before the fight, another after the fight. So it makes a lot of sense that this person missed those events.
 
  • Like
Reactions: forcedtosignup43

SINtax EroRR

Active Member
Game Developer
Jun 21, 2017
507
2,299
Well to be fair, most people won't just speak to every single npc, much less check it twice. In pokemon specifically, npcs only have one dialogue. If they are trainers, they have 2: one before the fight, another after the fight. So it makes a lot of sense that this person missed those events.
...That would make sense if Seras was just a common NPC, but she's not. She's an important supporting character who is also a romance option. So I personally do not agree with you. Even in the olden days of Chrono Trigger people would know that regular Townsfolk ≠ Named Characters.
 

Lewyn Collins

Engaged Member
Nov 16, 2021
3,113
3,679
...That would make sense if Seras was just a common NPC, but she's not. She's an important supporting character who is also a romance option. So I personally do not agree with you. Even in the olden days of Chrono Trigger people would know that regular Townsfolk ≠ Named Characters.
Oh no, I agree with you. And that's how it is in most RPGs. However in pokemon, even the named characters tend to have only one dialogue when you speak to them. This happens to all rivals, gym leaders, antagonists... And while I agree that any rpg player (like me) should know better than not double-checking an npc, pokemon has always been an exception to this. That's why I understand what happened to that one guy. He probably forgot that in a fangame, things could be different.
 
  • Like
Reactions: forcedtosignup43
3.70 star(s) 95 Votes