NEW IDEA
So, this is my contest entry: Whack-A-Color for the CSE
It shows you random color to look for, and then shows a 3x3 screen of different color squares. You must "hit" the square that is the color shown before the game starts. To hit the color, you will use the numpad. eg: if the color is on the top right, hit the [7]. For every color you "hit" you get one point.
Oh yeah, and there is a timer. :D
Scoring: The scores are displayed once the timer runs out, they are color coded, so RED<=5 points and so on.
(http://i.imgur.com/3PI1EJb.gif)
The top right is the color to hit, and the bottom right is your score. Scoring is as follows:
BLUE = 5
GREEN = 10
ORANGE = 15
RED = 20
Yellow = 25
PURPLE = 30
Download here. (http://www.cemetech.net/programs/index.php?mode=file&path=/84pcse/basic/games/WhackAColor.zip)
OLD IDEA:
[spoiler]
So, this is my contest entry: Hyper Hues for the CSE
It displays 12 squares (may become 9) that are all the same color, except one that is a different shade of that color. You must press the corresponding key to guess the color within a constantly shortening time span, and for every color you get right, you get 1 point.
Scoring: The scores are displayed once the timer runs out, they are color coded, so RED<=5 points and so on.
Screenshots:
(http://i.imgur.com/1OB1ECy.gif)
Did I forget anything? ???
I hope not :P
[/spoiler}
Yeah, for what platform is it? Alos sounds like a cool idea :D
LOP, its for the CSE.
Anyways, I just changed the name to Hyper Hues
Sorry for the double post but I got the screenshot up, and I just changed the name to Hiper Hues. (Misspelled on purpose)
Screanie:
(http://i.imgur.com/qlV7Au7.gif)
I am having a little trouble with graphics as you can see, but that will be solved using sourcoder!
By the way you are aware that your game isn't 4x3, 3x3 nor 3x4 in resolution, right? :P That bottom rectangle should be taking at least 33.33% of the entire screen height. (Unless of course the tiny rectangle height is caused by a bug). In your case it looks more like 2.9x12. Basically it should be blocky like the GIF on the front page.
Quote from: DJ Omnimaga on April 30, 2015, 04:11:33 AM
By the way you are aware that your game isn't 4x3, 3x3 nor 3x4 in resolution, right? :P That bottom rectangle should be taking at least 33.33% of the entire screen height. (Unless of course the tiny rectangle height is caused by a bug). In your case it looks more like 2.9x12. Basically it should be blocky like the GIF on the front page.
Yeah, I know, as I said I have the engine down, I just need to work on my graphics.
(http://i.imgur.com/1OB1ECy.gif)
Graphics are set, the side is for time, that will be implemented soon.
Green means that I got a score between 10 and 5
EDIT: Well, I guess it didn't' show the green screen at the end. It shows a color once you lose that corresponds to a number that is your score.
since the CSE does have rectangle abillities does that mean it's semi-normal speed? :trollface:
Quote from: Unicorn on April 30, 2015, 04:15:01 AM
Quote from: DJ Omnimaga on April 30, 2015, 04:11:33 AM
By the way you are aware that your game isn't 4x3, 3x3 nor 3x4 in resolution, right? :P That bottom rectangle should be taking at least 33.33% of the entire screen height. (Unless of course the tiny rectangle height is caused by a bug). In your case it looks more like 2.9x12. Basically it should be blocky like the GIF on the front page.
Yeah, I know, as I said I have the engine down, I just need to work on my graphics.
(http://i.imgur.com/1OB1ECy.gif)
Graphics are set, the side is for time, that will be implemented soon.
Green means that I got a score between 10 and 5
EDIT: Well, I guess it didn't' show the green screen at the end. It shows a color once you lose that corresponds to a number that is your score.
Why not display the score in binary? That would allow you to have a lot higher scores.
Binary as in...
Don't show any code, just give an example.
Well, you have 4 (or 3 would work too) pixels, and you display the score in binary over these pixels: one would be off-off-off-on,
two would be off-off-on-off, etc. This basically allows you to have 16 scores instead of 4
Yeah, or just colorcode the score in hex.
So you take 16 colors and let them correspond to 0-F.
Then you can easily do a table which show which color is what.
0x0
0x1
0x2
0x3
0x4
0x5
0x6
0x7
0x8
0x9
0xA
0xB
0xC
0xD
and so on
This would save you alot of space as it only needs one or two squares.
Oh, I see...
I think the way I am doing it should be ok for now.
Anyways....
After some thought, I think this game would be tooooo easy. So, instead off trying to hit the different color, you will have to hit one certain color the entire game, essentially a wack-a-mole. If you miss a "mole" you will either loss a life or a point, I still have to decide.
That seems like a nice idea actually. What kind of controls do you plan to use?
Same as the first idea, the numpad.
Cool to hear. I think it would be perfect because it would almost be like a touchpad. :)
I like touchpads, I'm gonna do my coding in SC from now on.
bump.
So I changed the name and idea again!
It is now a Whack A Mole type game, and instead of moles, you hit colors! woooo!
Screenshots coming!
Name: Whack-A-Color? Something else?
How about "Whack-A-Walrii"? :P
Poor walrus :(
O.O O.O O.O O.O O.O O.O O.O O.O O. O.O
Just no.
Whack-a-color seems nice to me actually, but it would need to always be one specific color I guess. Whack-a-Walrii wouldn't work since it's 4x3 :P
Next thing you know, all the games are kill the walrii!
Anyways, I put a description in the OP,so that explains anything. I might just put both game together if I have time...
If you just use the numpad from 1 to 9 you could use the 4th column to show the color you must hit. That color could change every now and then, but faster and faster as the game progresses and the color could become closer and closer to the rest over time to increase difficulty.
Ok, thats a great idea. Thats going to happen.
Update:
.Color changing added
.Timer decresing set
Next
.Better color changing (maybe two colors at once?)
.Showing scores
.Highscores
.Quitting
.Lives intergration
Thats all! This will hopefully be done by wednsday or earlier depending on how long I spend on the computer tomorrow.
New Screenie!
(http://i.imgur.com/AdCHiPC.gif)
Scoring done!
Whats left:
.Better color changing (maybe two colors at once?)
.Highscores
.Quitting
.Lives integration
The number is testing stuff.
Looking good! :D
Thanks! :P
I'm currently working on lives...
Bump!
Lives are done! I may add certain colors that if you see, and hit, you get an extra life.
You currently have 5 lives, and missing a color loses a life. I need to make life colors, for the sidebar, and then, well, the display aspects of the game are done!
Also:
[spoiler]
(http://i.imgur.com/nnevYcG.gif)
The number is the lives, of course. ;) I'm hitting the wrong keys to lose the lifes.
[/spoiler]
WHich color do you need to hit?
The color show in the top right hand corner, and the color shown when you first start thr game.
I'm also thinking that hitting a tan would give you a point, and hitting white, would subtract one. What do you think?
That could work, as long as hitting the wrong color doesn't give a point as well lol. I guess it could be like those rhythm or reflex games. (although of course slower due to the xLIBC BASIC limitations)
Well duh. I never actually though that I woud say xlibc basic limitations. :p
But yeah, a reflex type thing where the color only appears for a short time.
Bumpity bump bump!
So, update!
The color now randomly changes and it changes more often as you get a higher score.
screenie:
(https://usercontent.irccloud-cdn.com/file/IAYlkdjG/Whack-a-Color.gif)
I'm gonna make one showing the keys using jstified.
So, the todo list.
Update (stuff done):
.Better color changing
.Quitting
.Lives integration
Todo:
.Highscores
.White and Tan score +5 and score -5
.Other suggestions?
Thats all! Updated screenshot maybe tonight.
Looks awesome, hope you finish ;)
Nice progress. :D By the way have you tried experimenting with alternating between both screen sides? Because it's possible to get rid of the entire flickering.
What flickering? When you lose? Thats just a emulator error, its really inverting colors.
Woop! I feel the rage starting! I just need to implement highscores.
^ I just need to make it say YOU WIN or WIN or something and I am done :P
For me it shows the color of your score.
So you have a guide to see how high you got? I have a score in 8-Bit binary if you die before you win.
Yeah, everything's in the readme! :) I do want to make a side program so people can check the score on call when the contest is over. ;)
That would be cool :). Couldn't you save it to a var and have the user display it?
The flickering DJ Omnimaga was talking about was the flickering to clear the screen. You can just buffer the next screen to GRAM without updating the LCD iirc.
Oh, I think I understand. The flickering when the squares are drawn? Or is it when you lose? That flickering is an emulator error, it is supposed to invert to colors a few times.
YEah that's what I meant. When the screen turns white before stuff gets redrawn, that is. Basically you gotta redraw the stuff on the other side of the screen, then once you are ready to display it, the last square to be drawn also updates the LCD. Disregard this if on the real calc there's no flicker, though.
Ok, I might do that...
Ybmitted a playable version, now working on the extra points and deflickering.
Glad to hear. I'll give it a try later to ensure it works.
Great! Hopefully I can get the extra points and subtracting poits done tonight. Oh yeah, and highscores. O.O Almost forgot about that.
By the way, when substracting points, you died if they reached zero, right? Also, how are they represented?
You die when your lifes hit zero. The points, or scores are displayed on the sidebar and on the end screen. The highscore will be the first color you see when you start the game.
Ok thanks for clarifying. Also nice touch to display the highscore that way :)
Thanks, I'm thinking on the right,a black color to signify quitting, and on the left, the highscore color, with an inverted rectangle that switches between each colro using the arrow keys.
Welp, High-scores pretty much done, as soon as I get the comparison display done when the game ends. Here's a screenie showing that my highscore is less than or equal to five, but greater than zero.
(http://i.imgur.com/3PI1EJb.gif)
So, flickering, end screen, and maybe score adding and subtracting coming tomorrow.
Nice to see an update. Good luck getting rid of the flickering. :)
Thanks!I actually only got highscores and the end screen working, due to time constantes, but I might be able to get flickering done if I wake up early. Anywyas, submitted most recent version.
Just so you know
@Unicorn , the last version you submitted doesn't work properly. Some code was corrupted and replaced with spaces, while in-game you either die instantly after the screen flashed through many colors, or you get an ERR:Syntax. The 1st version worked fine, but I didn't try the 2nd. The issues I ran into were in the 3rd.
Tested on Doors CSE 8.2. Should I downgrade to DCSE 8.1?
Quote from: DJ Omnimaga on May 31, 2015, 08:55:41 PM
Just so you know @Unicorn , the last version you submitted doesn't work properly. Some code was corrupted and replaced with spaces, while in-game you either die instantly after the screen flashed through many colors, or you get an ERR:Syntax. The 1st version worked fine, but I didn't try the 2nd. The issues I ran into were in the 3rd.
Tested on Doors CSE 8.2. Should I downgrade to DCSE 8.1?
Maybe, I'll check it out soon, I just threw that together really quickly. I know the second has problems with highscores.
EDIT: I fixed it, the file didn't send to jstified correctly, so I thought it worked fine. Anyways, I'm sending a fixed version now.
This deserves a double post. I decided not to worry about extra scoring options, and just fixed one square not registering and sent it in. Sorry for all the clogging of your inbox. :P I think I sent in about 6 emails with the game. *.*
So yeah, I'm done.
Bump.
So there's a download link here. (http://www.cemetech.net/programs/index.php?mode=file&path=/84pcse/basic/games/WhackAColor.zip)
Yeah I noticed the 4 versions. I picked the latest one for judging but of course if there were any issues then it's good that there were other versions as well, since older ones worked too. I'll most likely start judging soon. I was taking a small break from stuff in general to cool down from stress from the previous weeks.
Great!
I just noticed some bugs with displaying the previous highscores at the end of the game, but now its to late x.x
Ah sorry to hear. D:
Quote from: Unicorn on June 05, 2015, 04:26:34 AM
Great!
I just noticed some bugs with displaying the previous highscores at the end of the game, but now its to late x.x
shhh, dont tell, you'll get a lower score :P
But the bugs don't effect gameplay at all! so it really doesn't matter. ;)
Though i'd imagine you'd get less points if your programs contains a lot of bugs :P though i guess its not that bad
Yeah, I guess. The bug is really hard to notice, and its probably something really dumb like storing 10 to a variable for two scores :P.
Oh i hate it when that happens, you release a program and like one sec after you find a really stupid bug <_<
Yeah the main issue is if the bugs affect gameplay. Of course, tho, if the bug affects in-game points but are easily noticeable, then that could affect the score a bit, but such bugs will probably affect score much less than install issues, install difficulty, overly large file size:content ratio and speed problems.
All that talk of speed reminds me, I should really try to use the xlibc getkey for it. Its noticibly faster right?
If your game runs faster than 9 FPS, then it's better to use xLIBC getkey, because BASIC getkey only registers about 10 keypresses per second. If you play some ultra fast games on monochrome calcs, you will notice that some keypresses get missed when holding down arrows or DEL. I also bet that xLIBC getkey is faster.
Yeah, it would be nice to have the keypresses register fairly fast. I'll implement it later if I can.