0 comments
First larger game (sitting at 8190 tokens atm). Goober's in the Mix is a metroidvania in a dungeon setting. You play Goober the goblin and need to investigate a disturbance in the dungeon. Constructive criticism welcome as well as token saving tips.
Music by Cody Loyd.
Post your win screens.
I'm working on a top-down space game, which has an option to toggle on planetary orbit indicator lines (mostly for checking things are where they're meant to be but I might include it in the actual game, don't know yet).
This results in circles being generated using the circ() function, sometimes with some large values for the circle radius (some planets can be orbiting thousands of pixels out)
Anyway, this worked fine before I upgraded to the newest Pico-8 version - I'm not sure what version I was on before but I've tested it with 0.2.0i and it works correctly and the orbit lines are drawn in full and in the correct place, even for planets that are thousands of pixels out from 0,0 where the star system is centred.
On the Pico-8 0.2.1b though, something is going quite wrong - any circles that are more than a few hundred pixels in radius are becoming very corrupted - circles have gaps in the area around y=0, and the top and bottom of the circles are very strange and... not circular...
I tested in 0.2.1 as well and that seems to be the point where this issue started. So I'm trying to figure out if it's a bug or if it's due to something that's changed there?
In this screenshot, the yellow line should be part of a circle and it's... not. The planet's orbital radius is 2226, so the raw circle will be circ(0,0,2226,9).
To clarify further I've made a test cart. This shows that circle radius values above 900 seem to be where the problems start, and the distortion that appears when the radius is increased beyond this.
Use the arrow buttons to pan the view around, and X and O buttons to increase and decrease the radius of the circle.
So I guess, I'm just wondering if this is intended behaviour in line with changes to Pico-8 limitations in 0.2.1 onwards, or is it a bug? (I'm hoping it's just a bug as my entire game is built around big circles...)
this game is a clone of one of the mini-games of "Lazy Jones", an old C64 game which is probably the first game ever to feature the concept of mini-games.
the game is very simple but that's what makes it so great. basically it's like snake, you have to build a wall in a garden without hitting plants. the longer the wall, the higher your score.
the code is only around 100 lines so if you're a beginner it might show you that it's possible to create a simple game without lots of code or extravagant graphics (in fact i like their simplicity).
have fun
This is the post Game Jam version of https://emuuuu.itch.io/wooltergeist
Hi, friends!
I've just finished my first ever video game!
I just want to thank this entire community for existing and being so helpful and friendly. I discovered Pico-8 in April; at the peak of COVID-19 hitting my hometown, and in the depths of a massive depression brought on by isolation/lack of work/personal losses from the pandemic. It's been a lifelong dream to make a game, but I never thought I'd ever actually accomplish it, and making a little progress on this project each day feels like one of the few things that has really kept me going. So, thank you all!!!
Special thanks to @Liquidream for leading me here in the first place, and being kind enough to do some playtesting and providing lots of helpful feedback along the way. Also thanks to @MBoffin for their zine, which got me started, and for feedback in the forums when I was trying to figure out managing game state.
Also, I have a resprite with (better?) music up on itch.io:
https://ridgek.itch.io/killer-kegs
I think I'm here to stay! On to the next one!
ive made a surprisingly functional chess port over the course of the last 2 days
i tried doing this in turing like half a year ago but couldn't get check detection down
this time it actually worked
arrows to move, hold x to fire, z to summon Mr. King Duck to shit all over everything (bomb)
Hi everyone! I've been working on this forever and it's finally at a place where I feel ready to show it. Things I still need to create/tweak before I'm actually done:
add title screen
add a death animation (right now the game just resets instantly when you die)
add a simple intro
(possibly) add an easy mode
Kosmo Duck is an endless, caravan-style shmup with an eye toward fast play sessions that only last a couple of minutes, coupled with a (hopefully) addictive scoring mechanic.
Let me know what you think! Thanks!
Hey folks! First post, here.
I just started learning Lua this summer, and the use of tables has been a big hurdle to me. I seem to have the basic concept worked out, but something really weird is happening to my one project.
Long story short, I'm making a racing game that is fairly code-intensive when it comes to the graphics. It was working just fine, until the other day when I started working on a level-select feature. I changed one of the level parameters from a solo variable to a part of a table, so that I'd be able to group the various parameters into nested tables and swap them with a simple level index, but suddenly, the performance took a nose-dive. I don't mean dropped frames, I mean it slowed down to a fraction of the acceptable frame rate, seemingly down to 5 frames a second or less.
I changed that one variable back to a standalone variable, performance jumped back to normal. Changed it back to an entry in a table, and the game slogged back down to a few frames a second.
I know there's a lot I still don't know about using tables, but does anyone know of any hard limit that would abruptly cause performance to suffer this drastically? All I changed was this:
(in _init:)
stage={addr=0}
spire=1
(in _draw:)
spr(5,64+rel_x,56-(spire*8))
for y=1,spire do
spr(6,64+rel_x,64-(y*8))
end |
Vs:
(in _init:)
stage={addr=0,spire=1}
(in _draw:)
spr(5,64+rel_x,56-(stage.spire*8))
for y=1,stage.spire do
spr(6,64+rel_x,64-(y*8))
end |
Any help would be muchly, muchly appreciated. Thanks!
Have been lurking for a long time and finally decided to try and teach myself some game dev stuff. Good opportunity to have my kids learn as well. My seven year old son and I put this together while following the tutorial from the awesome Nerdy Teachers. Hope to keep tweaking it and learning more!
The Cat's Meow
You are a kid named Lily, who has been hired by Muffie to get her café business started.
The café is almost ready to open, but she needs an interesting menu to draw in a crowd.
She requests you to find three exotic coffee beans to give her drinks a unique flavour.
Each one of these coffee beans lie at the end of tough gauntlets.
Can you brave the challenges and make her dream a reality?
After you've beaten the game, why not give the other modes a go?
Controls:
Z/C - Jump
X - Run
Arrow keys - Move
Music used:
- Chopin's Nocturne (Op.9, No.2)
- Sonic 3 Chrome Gadget
- Katy Parry's E.T.
- 8-bit Guy Junk Keyboard Theme
Special thanks:
- Nerdy Teachers (introduced me to pico8 in general)
- PrincessChooChoo (helped me with the sine wave code)
- The Pico8 Discord
Fun Facts:
- All sound and graphics resources were used up 100%
- Ending image was stored as a text string
Changelog:
BONK!
The second game by Gooey Studios
This is a very simple snake clone, left to turn left, right to turn right, collect the apples. If you hit your tail the game crashes (on purpose) and the score is shown.
I really wanna get it under 280 characters but I'm not sure I can really get it any further, so if you're up for it, I'd love to hear from you about how I can go further :)
265 chars (with a lot of help from remcode and jadelombax!)
d={}u,w,x,y=0,0,4,4
d={}u=0w=0y=4x=4
cls()::_::b=btn()w+=(b%2-b%4\2)/50
x+=1.5*cos(w)y+=sin(w)*1.5if(2<pget(x,y)or u<1)u+=1circ(l,m,2,0)l=rnd(99)m=rnd(99)
if(pget(x,y)>1)print(u)()
add(d,{x,y,2,u})for e in all(d)do e[4]-=.1pset(unpack(e))
if(e[4]<0)e[3]=1
end
circ(l,m,2,3)flip()goto _ |
Property descriptions
d = tail table u = score w = snake direction x = snake x pos y = snake y pos l = apple x m = apple y |
Hi friends, does anyone have a hacky JS workaround for preventing pinch/zoom on itch.io in iOS? I just uploaded my first Pico-8 game there and it's more or less unplayable. (I don't own an Android device, so I don't know if this is also a problem on there.) Looks like the exported JS from 0.2.1b already employs a few workarounds to prevent touch gestures, but this doesn't do much when it's in an iFrame because you can still pinch and zoom on the parent document.
A simple binary clock that I made. You can toggle a digital clock with the Z key, can toggle a legend to help you read the clock with the X key, and you can adjust the various colors with the arrow keys.
"Hotfoot is a frictionless platformer with the objective of completing each course as fast as possible. Use the slopes to gain speed and zoom off to victory! Test your time against the creator's!"
Made for the GMTK Game Jam 2020, in 48 hours.
<hr>
Hotfoot on itch.io
HOT GRILL demo font
TIP: Holding forward on a slope will give you additional speed, but will negate speed off a slope!
Hey @zep, not sure if this is a bug or intended, but I just realized that, in a fresh cart, sfx 0 is speed 1, while all other sfx are speed 16.
Is there some reason for this?
Seems like this is something that might lead to confusion at times. The user will probably figure out what's different pretty quickly, but still... I thought I should at least put it on your radar as a possible mistake.
As an aside, "Speed" really isn't the right term here. It should be "(note) duration", or something similar. I dunno, I don't have an audio background so there's probably a more concise term.
