#How do I fix this?

15 messages · Page 1 of 1 (latest)

pine siren
#

We need a bit more info. Did this happen on a map you were playing or are you currently making a map. Does this happen in every map or just this one? The log.txt file has the most info about the issue so send it here.

You can find it by following these steps.

desert prismBOT
#

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.

quartz seal
#

I opened my map and I saw this.

coral nexus
#

yes

quartz seal
#

also there is no log.txt

coral nexus
#

in your Celeste folder

quartz seal
#

yay there is no log.txt

coral nexus
#

no way

#

unless your game doesn't have writing permission in its own directory

#

it managed to open, so there is a log

pine siren
# quartz seal yay there is no log.txt

If you're on windows and have file extensions disabled the file looks like it's named just log. If that's the case send that file here and enable file extensions since not having them on is a serious security risk imo.

pine siren
quartz seal
#

I have that

coral nexus
#

can you send it?

quartz seal