You could do this by adding a separate element to the page with your loading text and `position: fixed` CSS, and then removing that element once the game is loaded.
Sean
Creator of
Recent community posts
This looks like an issue within butler itself, so unfortunately I can't help debug it much. Some things you could try:
- unzip + rezip the files and try uploading again
- rezip the files from the original folder and try uploading again
- rezip the files using a different archive tool (windows has a built-in one, but you could try a third party one like 7zip)
If the issue persists, you'll probably have more luck reporting it via itch support or their github issues.
it can be any supported CSS colour value, so all of these would be valid: red, #FF0000, rgb(255,0,0)
I'm not sure offhand why individual codepoints would not be working on import. Some Qs that could help identify the problem:
- Are the codepoints that aren't working part of the standard character set, or are you working in a certain extended range?
- Do the codepoints work when starting from scratch and doing an export + re-import without editing anything?
Without knowing more about this issue, one thing you might be able to try as a workaround is starting out with the characters in a different range that you've confirmed is working for export/re-import, and then remapping them back to your intended range via the font data manually afterwards.
To clarify the environment variable fix, what you should need to do is:
- Get an API key
- Go to the itch settings page for API keys
- Click "Generate new API key" -> A new row in the table will appear with source "web"
- Click "View" on this row
- Copy the revealed value
- Open a mac terminal
- In the terminal, run `export BUTLER_API_KEY=abc123` with "abc123" replaced with the copied key from step 1 -> this will temporarily set an environment variable
- From the same terminal, run the gui-butler application (I think on mac this is just `open app-name-or-filepath`)
- Click "login" -> the app should now show your games
The reason this is necessary is that on mac, the underlying butler command-line tool is refusing to communicate with the GUI app for the interactive login process, and providing an API key directly allows you to skip the typical login process. If the fix works for you, you can try setting up the environment variable in a more permanent way so you don't have to remember to do it manually (e.g. using a simple shortcut script or the system environment variables for your OS).
RE running the butler commands directly from command-line: You shouldn't need to do this to use the app, and I can't help debug it much since it's just the first party tool provided by itch, but if you're having trouble running it at all you could:
- try running `butler --version` and make sure you're on latest
- if you're not on the latest version, try running `butler upgrade`
- try running `butler diag` to make sure your device is able to connect to the necessary APIs
Hey there! The fixes/workarounds roughly summarized here would be:
- Try replacing the copy of butler that ships with the app with a manually downloaded copy
- Try starting the app from the command line with the environment variable `BUTLER_API_KEY` set to a manually generated API key
lmk if neither of these work for you, or if you have more specific info about your issue
it looks like the error here was that it's failing to load audio files due to missing codecs. for context, this game uses mp3 for all it's audio files, which is supported on every major browser. if you're using linux, this may be an issue on your device you can resolve by adding the proper codecs, but if not, unfortunately i'm not sure what would be causing the problem.