You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am pretty sure this is a hosting issue my end, but I'm writing to find out what produces the following console error message and under what circumstances?
File main.lua does not exist on disk.
I can't see it in the repo.
I can host locally on MAMP/Apache, but the error appears when I transfer my working files to my web server which is running Caddy. I need to figure out what is wrong so I can address it properly.
Thanks!
The text was updated successfully, but these errors were encountered:
I have managed to set more a specific MIME type directive for .love files on my server, which gets the default nogame.love working ...but custom games are still not working.
I think I need to know exactly how the wasm might fail, so i can make sure i have everything in place.
The g file is fetched, so it seems to be some request after the fetch that is failing.
OK, managed to track it down. I was doing some love.window stuff in love.load rather than love.conf
That resulted in the "File main.lua does not exist on disk." error
Moving the window setup to love.conf has everything running OK.
So, I'd like to suggest better error messages for this scenario.
gingerbeardman
changed the title
What prints "File main.lua does not exist on disk"?
Window setup in love.load results in weird error "File main.lua does not exist on disk"
Feb 9, 2025
Hi,
I am pretty sure this is a hosting issue my end, but I'm writing to find out what produces the following console error message and under what circumstances?
File main.lua does not exist on disk.
I can't see it in the repo.
I can host locally on MAMP/Apache, but the error appears when I transfer my working files to my web server which is running Caddy. I need to figure out what is wrong so I can address it properly.
Thanks!
The text was updated successfully, but these errors were encountered: