LoginLogin
Nintendo shutting down 3DS + Wii U online services, see our post

Triangle Ball

Root / Submissions / [.]

cakecatCreated:
Download:5Z5E83KJ
Version:Size:
You are a ball and you have to dodge the triangles! Challenge your friends to see who can get the highest score!

Instructions:

Press a button to start the game, and use the stylus on the bottom screen to move the ball on the top screen.

This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
yay thank you!! (This is mainly practice, I've never used SB before haha)

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
I got 19 on my third try

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
I got to ten on mine °^°

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
Oh shoot, 19!? Time to step up my game

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
oh. I got like 43 or something. I-I mean...! I got 19.5!!!!

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
Lies

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
n-no, I have proof, see!?

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
Beat 37, picture proof:

Well done! This is a pretty good first submission, even down to code quality and presentation. You only used GOTOs a few times :) This is one of those hard endurance games that I never manage to get that good at. My current best is 17. Since you're new, I'll give you some friendly tips to improve. SmileBASIC is not case-sensitive, and the typical style is to name everything in ALLCAPS NOUNDERSCORES. Shorter names are typical over longer ones (since the screen is so small) but don't worry about name length if it makes some names for things confusing or hard to read. I noticed all of your DEFs are named in lowerCamel but all of your vars are ALLCAPS, which is a bit weird stylistically. It doesn't really affect anything though. You have a lot of small DEFs for specific things (which isn't bad style) but your core code is in one big lump. Try to separate things a bit so it's easier to update your game (and easier for others to read the code) but don't go so far in the other direction where EVERYTHING has its own function. The result of the RGB() function is actually an encoded int value representing the color value, so you can pass it around as a value to any function that expects a RGB color. You could use this to replace getColor OUT C1,C2,C3 with a GETCOLOR() function that returns a single value, and tweak your custom graphics functions to accept a single argument for the color. Booleans are actually int-typed (as far as we know) so if you're storing them into a variable, that var should be an int (unless you're in some extremely specific use case where it being a real is important.) This isn't hugely important, though. This game is only one program file, but it does create a save file, with the very generic name SCORE. For this reason I recommend sharing the game as a project folder containing the program instead (and name it TRIANGLE_BALL so it's a bit less generic.) This way it will create its own folder when downloaded and people don't have to put it in DEFAULT and risk a file being overwritten, or create the folder themselves. You should be using VSYNC instead of WAIT 1 in your game loops. WAIT 1 just waits for one whole frame-time, while VSYNC syncs up with the next frame (in simple terms.)

Replying to:snail_
Well done! This is a pretty good first submission, even down to code quality and presentation. You only used GOTOs a few times :) This is one of those hard endurance games that I never manage to get that good at. My current best is 17. Since you're new, I'll give you some friendly tips to improve. SmileBASIC is not case-sensitive, and the typical style is to name everything in ALLCAPS NOUNDERSCORES. Shorter names are typical over longer ones (since the screen is so small) but don't worry about name length if it makes some names for things confusing or hard to read. I noticed all of your DEFs are named in lowerCamel but all of your vars are ALLCAPS, which is a bit weird stylistically. It doesn't really affect anything though. You have a lot of small DEFs for specific things (which isn't bad style) but your core code is in one big lump. Try to separate things a bit so it's easier to update your game (and easier for others to read the code) but don't go so far in the other direction where EVERYTHING has its own function. The result of the RGB() function is actually an encoded int value representing the color value, so you can pass it around as a value to any function that expects a RGB color. You could use this to replace getColor OUT C1,C2,C3 with a GETCOLOR() function that returns a single value, and tweak your custom graphics functions to accept a single argument for the color. Booleans are actually int-typed (as far as we know) so if you're storing them into a variable, that var should be an int (unless you're in some extremely specific use case where it being a real is important.) This isn't hugely important, though. This game is only one program file, but it does create a save file, with the very generic name SCORE. For this reason I recommend sharing the game as a project folder containing the program instead (and name it TRIANGLE_BALL so it's a bit less generic.) This way it will create its own folder when downloaded and people don't have to put it in DEFAULT and risk a file being overwritten, or create the folder themselves. You should be using VSYNC instead of WAIT 1 in your game loops. WAIT 1 just waits for one whole frame-time, while VSYNC syncs up with the next frame (in simple terms.)
I edited the game to use the Circle Pad to move the ball (the position of the ball is based on where the stick is on the X-axis, so it's similar to the touch screen control) and it actually made it harder to play. Oops.

Replying to:snail_
Well done! This is a pretty good first submission, even down to code quality and presentation. You only used GOTOs a few times :) This is one of those hard endurance games that I never manage to get that good at. My current best is 17. Since you're new, I'll give you some friendly tips to improve. SmileBASIC is not case-sensitive, and the typical style is to name everything in ALLCAPS NOUNDERSCORES. Shorter names are typical over longer ones (since the screen is so small) but don't worry about name length if it makes some names for things confusing or hard to read. I noticed all of your DEFs are named in lowerCamel but all of your vars are ALLCAPS, which is a bit weird stylistically. It doesn't really affect anything though. You have a lot of small DEFs for specific things (which isn't bad style) but your core code is in one big lump. Try to separate things a bit so it's easier to update your game (and easier for others to read the code) but don't go so far in the other direction where EVERYTHING has its own function. The result of the RGB() function is actually an encoded int value representing the color value, so you can pass it around as a value to any function that expects a RGB color. You could use this to replace getColor OUT C1,C2,C3 with a GETCOLOR() function that returns a single value, and tweak your custom graphics functions to accept a single argument for the color. Booleans are actually int-typed (as far as we know) so if you're storing them into a variable, that var should be an int (unless you're in some extremely specific use case where it being a real is important.) This isn't hugely important, though. This game is only one program file, but it does create a save file, with the very generic name SCORE. For this reason I recommend sharing the game as a project folder containing the program instead (and name it TRIANGLE_BALL so it's a bit less generic.) This way it will create its own folder when downloaded and people don't have to put it in DEFAULT and risk a file being overwritten, or create the folder themselves. You should be using VSYNC instead of WAIT 1 in your game loops. WAIT 1 just waits for one whole frame-time, while VSYNC syncs up with the next frame (in simple terms.)
Thank you for the tips, SmileBasic is kinda hard for me honestly, and it's unlike anything I've ever used, so it's really weird. But I'll try my best to keep getting better, I tried commenting the best I could.

Replying to:snail_
Well done! This is a pretty good first submission, even down to code quality and presentation. You only used GOTOs a few times :) This is one of those hard endurance games that I never manage to get that good at. My current best is 17. Since you're new, I'll give you some friendly tips to improve. SmileBASIC is not case-sensitive, and the typical style is to name everything in ALLCAPS NOUNDERSCORES. Shorter names are typical over longer ones (since the screen is so small) but don't worry about name length if it makes some names for things confusing or hard to read. I noticed all of your DEFs are named in lowerCamel but all of your vars are ALLCAPS, which is a bit weird stylistically. It doesn't really affect anything though. You have a lot of small DEFs for specific things (which isn't bad style) but your core code is in one big lump. Try to separate things a bit so it's easier to update your game (and easier for others to read the code) but don't go so far in the other direction where EVERYTHING has its own function. The result of the RGB() function is actually an encoded int value representing the color value, so you can pass it around as a value to any function that expects a RGB color. You could use this to replace getColor OUT C1,C2,C3 with a GETCOLOR() function that returns a single value, and tweak your custom graphics functions to accept a single argument for the color. Booleans are actually int-typed (as far as we know) so if you're storing them into a variable, that var should be an int (unless you're in some extremely specific use case where it being a real is important.) This isn't hugely important, though. This game is only one program file, but it does create a save file, with the very generic name SCORE. For this reason I recommend sharing the game as a project folder containing the program instead (and name it TRIANGLE_BALL so it's a bit less generic.) This way it will create its own folder when downloaded and people don't have to put it in DEFAULT and risk a file being overwritten, or create the folder themselves. You should be using VSYNC instead of WAIT 1 in your game loops. WAIT 1 just waits for one whole frame-time, while VSYNC syncs up with the next frame (in simple terms.)
But you are doing very well so far! This game is very amazing and one I will probably play on long car trips or stuff. I had a random Idea about making a few gamemodes like Hard, Super hard and easy, say super hard could be like 10 triangles with one hole moving very fast and another I had was survival where you get 3 lives to see how long you can go or have like triangles can come from any direction (say after going up they could move to the right instead) it would add a very cool effect and stuff. Though this is only if you intend on adding stuff otherwise if I may ask, do you have any other projects?.

Replying to:snail_
Well done! This is a pretty good first submission, even down to code quality and presentation. You only used GOTOs a few times :) This is one of those hard endurance games that I never manage to get that good at. My current best is 17. Since you're new, I'll give you some friendly tips to improve. SmileBASIC is not case-sensitive, and the typical style is to name everything in ALLCAPS NOUNDERSCORES. Shorter names are typical over longer ones (since the screen is so small) but don't worry about name length if it makes some names for things confusing or hard to read. I noticed all of your DEFs are named in lowerCamel but all of your vars are ALLCAPS, which is a bit weird stylistically. It doesn't really affect anything though. You have a lot of small DEFs for specific things (which isn't bad style) but your core code is in one big lump. Try to separate things a bit so it's easier to update your game (and easier for others to read the code) but don't go so far in the other direction where EVERYTHING has its own function. The result of the RGB() function is actually an encoded int value representing the color value, so you can pass it around as a value to any function that expects a RGB color. You could use this to replace getColor OUT C1,C2,C3 with a GETCOLOR() function that returns a single value, and tweak your custom graphics functions to accept a single argument for the color. Booleans are actually int-typed (as far as we know) so if you're storing them into a variable, that var should be an int (unless you're in some extremely specific use case where it being a real is important.) This isn't hugely important, though. This game is only one program file, but it does create a save file, with the very generic name SCORE. For this reason I recommend sharing the game as a project folder containing the program instead (and name it TRIANGLE_BALL so it's a bit less generic.) This way it will create its own folder when downloaded and people don't have to put it in DEFAULT and risk a file being overwritten, or create the folder themselves. You should be using VSYNC instead of WAIT 1 in your game loops. WAIT 1 just waits for one whole frame-time, while VSYNC syncs up with the next frame (in simple terms.)
I can't tell, does the game speed up as you get a higher score? It shouldn't be too hard to start the game out a bit slower and have it accelerate gradually as your score increases.

Replying to:Simeon
This is stupidly addicting haha My high score is 18 So, if anyone decides to challenge me, and does better (yeah right), then leave a comment below.
We all know those were coded results not from the author...

Just for kicks, I have video proof of my score of 59. https://www.youtube.com/watch?v=2AaTgN1iTIU While I was at it, I have a couple of "screenshots" you can use if you'd like.

Replying to:chemicalex
Just for kicks, I have video proof of my score of 59. https://www.youtube.com/watch?v=2AaTgN1iTIU While I was at it, I have a couple of "screenshots" you can use if you'd like.
Nice job! And thank you haha, I dunno how you record a 3ds honestly xD

Replying to:chemicalex
Just for kicks, I have video proof of my score of 59. https://www.youtube.com/watch?v=2AaTgN1iTIU While I was at it, I have a couple of "screenshots" you can use if you'd like.
Custom firmware along with NTR streaming. If you have CFW and are interested, you can ask me in chat and I can help you through it.

Replying to:chemicalex
Just for kicks, I have video proof of my score of 59. https://www.youtube.com/watch?v=2AaTgN1iTIU While I was at it, I have a couple of "screenshots" you can use if you'd like.
You work too hard.

This is fun. I got 1, 2, and then 30. ._.