#Really weird XML bug

22 messages · Page 1 of 1 (latest)

old yew
#

So uh, I've had this problem with this map and exclusively this map.
Whenever I open Celeste, this happens to all the custom tilesets in this map, but it goes away if I open the XML folder and simply save it once, no changes needing to be made.
I'm wondering how to fix this since it's honestly really annoying and if it's repeatable by other people then that'd be a problem for the final release of the map.

image.png
gusty vector
#

send log.txt

gusty ridgeBOT
#

There are two types of logs; crash logs and log.txt.

Crash logs are generated when you see an "Oooops! :(" crash handler screen. They contain extra information which regular logs don't.
To access those, there's a button that says Open log file folder, which should take you to where they're stored. Make sure to grab the latest one!

For more subtle issues, non-crashing problems or other miscellaneous stuff, log.txt is checked. To find it, do the following:

  • Open Olympus.
  • Press the Manage button in the Installations panel on Olympus' main menu. (it's to the left)
  • Press Browse to open the Celeste folder.
  • Look for the file named exactly log.txt inside that folder. Do not grab error_log.txt or look into the LogHistory folder as those are not the log.txt you're looking for.

Your username may sometimes show up in those logs. If you're concerned about that, remember to censor it before uploading. Every text editor should have a replace function, commonly opened with Ctrl+H.

old yew
gusty vector
#

i don't think this is good

image0.jpg
old yew
#

I see

gusty vector
#

neither is this

image0.jpg
old yew
#

idk about the first one in the log but the autotiler thing makes sense considering how the bug's manifesting

gusty vector
#

id check this first crash

#

what is this sjtfi mod

old yew
#

it's a helper from a canceled collab iirc, I should probably disable that

gusty vector
#

check if the issue persists then

#

else id look into that

old yew
#

ok

#

the issue persists after disabling the old helper, it seems

tiny sage
old yew
#

ahhhhhh I see

#

will fix tomorrow after I sleep, ty

#

honestly I didn't even remember that I used a custom xml for my other coretober-related project since I only used vanilla tilesets w/ a funky colorgrade

tiny sage
#

yea in general "this file isn't working even though i know it's in the right location and it starts working again if i hot reload it" is a telltale sign of a file path conflict

old yew
#

gotcha

tiny sage
#

basically

  • mod A xml loads
  • mod B xml with the same filepath loads and overrides mod A xml, causing the map to try to use mod B xml even if it belongs to mod A
  • saving mod A xml will trigger a hot reload and override it again with the "correct" file, and then it works again