Hardcore Questing Mode [FORGE/FABRIC]

Hardcore Questing Mode [FORGE/FABRIC]

16M Downloads

Config Crash

GhostVamp opened this issue · 12 comments

commented

So, using the same modpack, with editmode=true game doesnt crash.
The second i change the editmode=false the game gives me this
http://pastebin.com/03fv3vcN
Any idea?

commented

ssp or smp?
On Oct 29, 2015 9:46 AM, "GhostVamp" [email protected] wrote:

So, using the same modpack, with editmode=true game doesnt crash.
The second i change the editmode=false the game gives me this
http://pastebin.com/03fv3vcN
Any idea?


Reply to this email directly or view it on GitHub
#45.

commented

ssp

commented

walk me through it step by step as detailed as possible
On Oct 29, 2015 9:55 AM, "GhostVamp" [email protected] wrote:

ssp


Reply to this email directly or view it on GitHub
#45 (comment).

commented

Start instance on HQM 4.3.2 - Everything goes as planned.
Change editmode=true to editmode=false
Open the same instance - Game gives that crash.

commented

I also get this when trying to create a world with editmode=false
http://pastebin.com/4KTkeTG8

commented

update to 4.3.3
On Oct 29, 2015 10:07 AM, "GhostVamp" [email protected] wrote:

I also get this when trying to create a world with editmode=false
http://pastebin.com/4KTkeTG8


Reply to this email directly or view it on GitHub
#45 (comment).

commented

Where could i find that? Curse only has 4.3.2.

commented

ah you are running 431 not 432 according to the log... (i mixed up the versions in my head)

commented

I tried both versions. None of them works.

commented

432 should fix the second log you posted?
On Oct 29, 2015 10:31 AM, "GhostVamp" [email protected] wrote:

I tried both versions. None of them works.


Reply to this email directly or view it on GitHub
#45 (comment).

commented

432 fixes it, but i think i found what's causing the problem.
I'm updating HQM from 423 to 432 and even if no question has problems, HQM cant read them on quest mode, only edit mode.

commented

Right. I have no idea what happened, but doing a fresh config install and then manually adding the quest.hqm file worked.
I'm totally lost on what happened.