>uninspired reskin
Yep. The epitome of development for sure.
The effort you're putting into this could've gone towards learning actual programming. Just saying.
The second set of GFILLs gets immediately overwritten by the first set when the loop ends. Try adding another WAIT 20 (which should be longer by the way, since 20 frames is only a third of a second) after the second set of GFILLs.
Also, you'll have to implement this cycle another way, since the loop isn't synchronous with the gameplay.
Remember:
If you want to compare (is A equals to B?) use ==.
If you want to assign (make A equal to B) use =.
Lines 25 and 26 should be comparing instead of assigning.
Are you copying this from somewhere or writing code without a prior knowledge of SmileBASIC's instructions?
A lot of the syntax you are using is wrong and you are not using the appropriate instructions. Try starting to learn SmileBASIC by developing small, basic programs on your own, then learning more advanced instructions as you go.
The game itself offers no tutorials whatsoever.
There are no step-by-step guides to making a game (and programming in general). Instead, you have to research and slowly get a knack for programming and software development. You can ask questions in this community if necessary.
You should start by reading the official e-manual...
http://smilebasic.com/en/e-manual/manual11
You should also read the electronic manual bundled with the game by starting the game, pressing Home and selecting Manual.
Afterwards, you can play around with various instructions and slowly start to get programming experience.
Raspberry Pi is mainly coded with C, if I recall correctly. You could probably port SmileBASIC programs as long as you can find equivalent instructions in C.
Have you tried running it? I'm pretty sure it'll throw an error at line 10 (If TIMER>7), 12, 15, 17, 20, 21, or 25-28, since the instructions specified aren't being used correctly.
If this code is being taken from another source, keep in mind that SmileBASIC can be extremely different from other implementations of BASIC, meaning copied code most likely won't work without proper porting.