Honestly, I haven’t coded heavily in a while, so I don’t remember.
However, I never named my overlays with spaces. If you look at your script KENICHI is purple while the rest of name isn’t. So I’m assuming the spaces are the issue here, and the script mistakes it to be the same overlay (the kenichi standing behind, kenichi standing while looking up)
Only thing I can recommend to do is to reupload them, with same name but with no spaces and trying again.
I’ve gotten this error quite literally when the script recognized the “overlay create” command twice. For example, if you add an overlay to the scene by attaching it to the background line but also use the “overlay create” command later or if you have a goto/label that makes the code read the same “overlay create” code twice without deleting it somewhere in between, you may get this error. If renaming your overlay doesn’t work and you still need help, I would suggest sending more of your code starting from the background change :))
I think you should do ‘overlay create’ first, then make it ‘overlay moves to opacity 1’ (I’m pretty sure overlays are automatically ‘opacity 0’ so you don’t need that part). Also, if you want the overlay to show up immediately without it appearing slowly, do ’ overlay opacity 1 in 0’. The ‘in 0’ is the amount of seconds.
So when I read your comment, I actually found out where I was doing wrong and tried using ‘OVERLAY clear’ instead of ‘opacity 0’ for removing (yes I actually thought it’s a genius move to just make it invisible than deletion) and fortunately the warning was gone! Thanks again for the help, had you not say anything I’d just leave it exactly how it was XD
So last night I decided to name just one layer that was causing stress because I didn’t have the mood to rename all my layers and luckily for me it worked. Thanks again, Salnova. Really appreaciate for taking the time to help me ^v^
The fact that you set it to zero with the intent to clear it shows you understood the core concept behind adding and deleting overlays and makes it a very understandable error. I’m glad I could help you figure it out :D!