Por favor no ignores los comentarios que pongo. Espero que escuches y entiendas, porque es algo que vale la pena comprender. Los derechos de autor protegen la propiedad intelectual de todos los creadores de contenido original, por lo que es importante el entenderlo y respetarlo. Cuando crees tu propio contenido, vas a querer protegerlo como propiedad tuya, y estas leyes ayudan en eso.

Vuelvo a repetir porque es un mensaje importante. No esta permitido distribuir contenido protegido por derechos de autor, tal como la serie de Mario. Esto aplica a archivos de imagen (texturas), texto y demás. Por favor eviten subir archivos de este tipo. Estarán evitándole problemas a SmileBoom y a ustedes mismos.

Maybe you could use SPCOL with the cross-hair sprite? I can't really help with SPCOL. I'm rather inexperienced with sprite collision. Sorry!

Is your name Raymond? Because if so, you might want to remove any personally identifying information. (You should use your nickname, instead.)

Only if they have a single return value! Using the examples I left previously, this is how you'd call each one. FUNC 2,3 ...for instructions with no return values. A=FUNC(2,3) ...for functions with a single return value. FUNC 2,3 OUT A,B ...for functions with multiple return values.

No esta permitido distribuir programas con contenido protegido por derechos de autor, tal como la serie de Mario. Esto aplica a archivos de imagen (texturas), texto y demás. Por favor eviten subir archivos de este tipo. Estarán preveniendo problemas que podría tener SmileBoom.

Not quite.

COMMON DEF FUNC(FOO) ... RETURN BAR END The COMMON specification allows a function to be called from a program slot other than the one it's in. It's common (ha!) to find it in libraries, engines and such.

There are three main types of functions... DEF FUNC X,Y ... END ...has no return values. Doesn't have parenthesis. DEF FUNC(X,Y) ... RETURN A END ...has a single return value. Has parenthesis. DEF FUNC X,Y OUT A,B ... END ...has multiple return values. Doesn't have parenthesis, but haves OUT.

Strings follow a different saving process and use a separate file, but the process is similar. Let me know if you want an explanation for it. Loading the data back up is also a similar process. It's pretty much the same as saving, but backwards. Let me know if you want an explanation for it as well.

DIM SAVARR[3] 'Let's assume I have 3 variables to save SAVARR[0]=HP SAVARR[1]=MP SAVARR[2]=EXP SAVE "DAT:FILE1",SAVARR Note: If you want to save an array... If it's a static array (fixed length), you can just accommodate it in the same save array. If you have a dynamic array, you'll want to create a separate file for it, although there is a semi-complicated workaround.

You need to create a DAT file that will contain all these variables. It's a straightforward process. 1. Declare an array that will fit all the stuff you will save. 2. Fill this array with said stuff. The order is not important, but you must remember it. 3. Call the SAVE instruction. Specify DAT file type and the array to save.

That being said, the following that it brings can be a bit troublesome, specially since it don't seem to understand the essence of SmileBASIC and its community. It's not particularly problematic, since it seems to stay in your posts, but I digress. I just wanted to say that we have no problem with your posts. However, keeping your art to a single post might actually be something worth trying!

(cont.) This community has absolutely no problem with people posting their art. We've had many artsy posts, and we'll most likely continue to get them. Some people may think that your posts are the elephant in the room, since they usually attract a lot of attention. However, I can tell you that attention is well deserved and doesn't bring any negatives by itself.

Hello there. I wasn't going to say anything originally, but seeing how some of the comments here seem awfully defensive about something that doesn't seem to happen, I guess it's worth leaving a comment about.

Easy! Just use CHKFILE("[FILETYPE:]PRGNAME"). It returns TRUE if the file exists, FALSE otherwise. Specifying the file type is optional, hence why it's in brackets. The file type can be either TXT or DAT. (DAT includes graphic files.)

Siempre me impresionas con tus habilidades gráficas! No puedo esperar!

I just used Google Translate to get a transliteration. I don't know Japanese. Sorry!

The best place to start is probably the official e-manual. You can check it out here: smilebasic.com/en/e-manual/manual11 Aside from that, you can probably pick instructions that interest you from the reference manual and play around with them. A lot of people learn to code like this.

It only becomes a problem when people replace the sprites and backgrounds with copyrighted content and then distribute them. So to anyone planning on doing that: don't. Anyways, I don't see why this program still gets so much attention, what with Super Mario Maker officially releasing on 3DS soon.