A cart I wrote to experiment with the 0x808 serial port. Arrow keys adjust the frequency and volume of the sin wav being written to the port. A graph of the samples written each frame is displayed to the screen.
Revision 1:
Added some enhancements:
Added several waveforms besides sine which can be cycled using 🅾️❎
Tuned to C4 = 256 Hz rather than A4 = 440 Hz to have a nice 12 cycles per frame synced initially
Updated graph to distinguish between points and the lines between them and added a zero line
Displaying the min and max of current waveform (useful for testing that new waveforms stay in range)
3 comments
I've found that even with my small collection of gamepad/controllers being hooked up to various devices, that the default mappings on gamepads differ widely. It made it hard to me to know which button to label as which in my games.
So if you just plug in your gamepad and boot up PICO8, which buttons map to which keys?
Naturally, it's gonna vary but based on my own controllers and a very unscientific survey on Twitter, I've come to accept that the B button on a gamepad maps to Z on keyboard, and A button maps to X on keyboard.
Like so:
Obviously, you can remap the buttons and all that jazz but out of the box, this seems to be the common config. This is how my Buffalo gamepad is when plugged into my Windows machine...and gotta say, it makes sense. The B button is left of the A button, just like the Z key is left of the X key on my keyboard.
What have you found with your various controllers and gamepads? Maybe this thread can serve as an index of controllers and how they map to PICO8 by default. Just make sure to outline the brand of controller and the device you're using it with.
6 comments
the current version of PICO-8 (0.2.5) for Windows has white window title bars:
the white title bar is distracting, no matter if app colors are set to light mode or dark mode in Windows settings.
this mockup made in Microsoft Paint shows the Windows title bars in dark colors from the PICO-8 palette:
and here is a much more coarse hand-pixeled mockup of how the colors could look like:
- Inactive window's title bar (right)
- background: PICO-8 color #0
- foreground: PICO-8 color #6
- Active window's title bar (left)
- background: PICO-8 color #1
- foreground: PICO-8 color #7
4 comments
バージョン 2 - VERSION 3 - FINAL
YOU FOUND OLD GAME CARDRIDGE: CELELEC 1981
GAME FEELS EMPTY, AND HAS N0 BUGS
9 comments
Over the past few weeks I've been working on Celia, a TAS tool for PICO-8 based on picolove, and it's finally ready for its initial release
Celia comes with 2 tas tools, one that should work for any PICO-8 cart (with some caveats, in the repository readme), and one that's more specialized, built for Celeste and mods. The tas tool code is layed out in a way where you can extend it to create tas tools for specific games, enhancing the normal functionality, so it also doubles as a tasing "framework" (api documentation coming soon).
Celia is based on my personal fork of picolove, Which has much better compatibility with PICO-8 carts than other forks, from what I've seen.
I'd love to hear any feedback, bug reports, and feature requests/suggestions. In addition, if you make a tas using Celia, feel free to post it here, I'd love to see it!
As a demonstration of the tas tool, I made a tas of Get Out of this Dungeon by @Insanus, which you can check out here [youtube]00JR6MZk_ZA
4 comments
Zaag is pretending to be a lost 1980s vector arcade game. Blast the zoids and cleanse the Tau.
How to play
As an arcade game, Zaag of course asks you to dodge and blast enemies. Classic arcade difficulty.
Controls
Your blaster has an initial charge up time, so focus on staying alive at the start of each Tau. Look at the tail of each zoid to get an idea of their speed and direction. Your tele is ready immediately, but has a long cooldown.
If using a game controller, use the D-pad instead of the joystick. You don't want to hit tele or flip by accident.
Two player mode
10 comments
3 min score attack Shooter!
|
|
How to Play
-
X or Z Button : Shot
-
Power-up 2 levels.
-
Closer to the enemy, can fire shots faster.
-
Destroy your enemies faster,get a bonus of up to 12x.
- Time expires when 3 minutes elapse.
enjoy!
Credit
KENJI MIZUTA(programming, music compose, and other)
twitter ID:@suidengetsu
8 comments
A game about escaping a dungeon, one room at a time.
Arrow keys to move and aim
z/c jump
x/v fire(ball)
Tips
- Progress is saved whenever you enter a new room or defeat a boss, so if you get stuck you can come back later
- You can reset the current room, toggle music, or reset your whole progress from the menu (press p or enter)
- You can hold x, press the arrow keys to aim your fireball, then release x to shoot
- You may find a room too difficult to beat right now. Please take a break and come back - I know you can do it!
Features
- 24 carefully designed rooms to overcome, with
18 comments
While HELP is indeed informative it is missing some commands that are used in Pico-8. I'm not going to mark these as errors, @zep, as they may just be overlooked. This includes:
goto count setmetatable getmetatable rawset rawget rawequal rawlen assert . Likely there are others.
While not required for help it would be nice if there was HELP for these single-key shortcuts:
? # @ % $ \
If you ask for help on do it does not give a code example which is odd as all the other commands do.
Further the HELP could also appear if you are one-character to the right of the command.
pset(4,8)
Where the cursor is on the ( Pressing CTRL+U does not give help on it.
Should also work if the cursor is directly on the ) which is linked to that same command.
0 comments
I just discovered that you can use W for next sprite and Q for previous sprite in the map editor. I think it would be really neat if instead, you could use WASD to move the sprite selection around. It would be super helpful to avoid moving the mouse back and forth, click to select a tile, place a single one, switch tiles again. As far as I know, ASD don't have any current uses so it would work pretty nicely.
1 comment
Orbital mechanics puzzle game developed for the A game by its cover 2022 jam.
A tutorial and binary downloads can be found at itch.io
This is the first game I have developed, so let me know what you think.
4 comments
In my code, I used menuitems as a way of interaction with the game.
When you run it, if you go to the command line, set items.planks to true and go back to the game and pause, press level 1 and then press move, it shows an error, about trying to call _superyield with flip().
I don't know if this is something bad or not, as I don't understand yield(), _superyield and flip() since I never used any of these.
The error:
The code (tried to remove the useless stuff):
function _init()
menuitem(1,"level 1",level1)
items={
planks=false
}
end
function _draw()
end
function level1()
menuitem(1,"move",move)
end
function move()
return true
end
|
1 comment
The first release of another finished hobby project. I mostly wanted to play around with rendering from the screen buffer, and it turned into a short little fishing/memory sequence game.
You have to guess a fish's lure and bait preference, and once your hook is in the water, you need to attract the fish by moving your rod either up, down, right, left or shake with O.
Each fish type has a unique sequence it needs in order to bite, that you have to press in the correct order.
This is where the guessing comes in. Press buttons until you see a heart icon over a fish, that means you guessed the first button. Now you can guess the next button. If you fail, the fish shows a X over it instead. Start over with the first button again, and keep guessing. The most rare 5-star fishes have a sequence of 5 buttons to press!
Once you have caught a fish, it is permanently unlocked in the fishdex and you can read what bait/lure and sequence it has.
Then take your knowledge to survival mode, and see how long you can survive.
3 comments
OK, I know we can use ternary conditions in variable assignments. But - as far as I can tell - they can't be used in calculations. Having logical statements be used as a value operator in a calculation can be used in many circumstances, would be readable and possibly pretty token efficient.
How might this look?
(a > b) would result in a 1 if true, 0 if false.
something like "pset(100+100*(a > b), 200, 7)" would prevent the use of a bunch of ternary assignments, local variables or if statements.
So what do you think? Useful? Doable? Worth it?
13 comments
Hello!
Welcome to the universe where the Humanity is the invader!!
Annihilate all the astronauts before they colonize your planet!
We are three web developers apprentices in Ada Tech School in Nantes (France), we created this project in two weeks.
So please be tolerant, it's not perfect but we're proud of our work.
1 comment
(v00 11-17-22)
TO LOAD THIS PICO-8 CART, in immediate mode, type:
load #pickapoint^^ This version is for examining and learning from. The way I will mostly code from now on.
TO LOAD THIS PICO-8 CART, in immediate mode, type:
load #pickapoint_shr^^ This version is for use in your own code. It's a lot smaller in size. If you use CLIPBOARD to copy and paste, be sure to press CTRL+P prior to pressing CTRL+V to paste and after CTRL+V as well.
0 comments
Hello.
@zep, could you please add a hotkey like CTRL+W to turn on and off word-wrap for code ?
For instance we have this one line which extends beyond the screen:
However, if you press CTRL+W then it would wrap around the screen like so, showing the ∙ at the beginning to let you know it is a wrapped line and you can navigate the area and easily edit all 4-lines. When done, press CTRL+W again to return it back to a full and single line that scrolls off the edge of the screen.
Ignore the color changes above, this is just me putting that character in front of the code to show what it would look like.
Now I know this isn't perfect, I mean Pico-8 only has 32-characters across using a 3x5 pixeled font. Yet I think this will help some of us work on large lines.
It could also be that you do not see this word-wrap except for lines that do exceed 32-characters AND the cursor must be on that line in order to access it.
2 comments
this is where i dump my less good cartridges
i am doing this
- because i want to publish even my less good cartridges
- i also don't want to clutter the BBS, so i put them in the same thread
2022-11-17: Welcome!
i gave up on PICO-8 years ago when i buyed it since i got overwhelmed fast.
now i rediscovered PICO-8 and wanted to try it again, so i did.
this is my first PICO-8 cartridge i ever made.
2022-11-20: Welcome! — special edition
11 comments
