2.0
- Game is now finished
- Instructions are now available
1.8
- Added boss attacks
- Added boss deaths
- Added new sprites
1.7
- Added boss intro
- Added score system
1.6
- Added death animation
- Fixed collsions
- Added soul hitboxes
1.5
- Fixed missing enemies
1.4
- Added more effects
- Souls now spawn
- Game Over can now be exited
1.3
- Fixed explosion crash bug
1.2
- Finished main menu
- Adjusted explosion particles
1.1
- Added a menu which still is not fully completed
1.0
- Our Pico8 game where the player has to fight through the 9 stages of hell
- Still WIP
Day 11 of the Pico-8 Advent Calendar 2018!
a battle between efficiency & exhaustion
~a winter classic~
Hey there folks, it's mid-December, and you know what that means: time to shovel the driveway! The snow's packed pretty heavy though - if it piles up too much, you'll have a hard time pushing it and probably just make a mess!
Make sure to check back on the calendar each day for a new gift!


I wanted to see the code from the following cart: https://lexaloffle.com/bbs/?tid=27636
I am unable to view the code from the bbs as previously.
Also, searching for "small text" from within splore results in "COULD NOT CONNECT TO BBS" even though I'm able to refresh other parts of splore such as featured, new, etc.
Thanks! (as a workaround, I'll just download the png)


Hello all,
I may be missing something but I thought we were able to look at the code of a cartridge hosted online via a web browser?!
I don't seem to be able to do it now and I don't have access to my own Pico8 executable right now to load the cartridge.
Am I making sense? I thought when playing a cart online there was the word [CODE] underneath that you could click on and view the code.
?

This is a simple game just using up, down and z to shoot. Try to dodge the oncoming grey blocks while collecting the red for life and yellow for ammo.
You can shoot oncoming blocks but, beware, you may shoot a useful ammo or health block!
The closer the blocks get the more points you score - how close will you let them get?


Controls: Left, Right
Get past the traffic herd to escape and win!
Hit z/x/c to restart after win/loss
Taffic World!!! Evade the cops and escape!
This is a simple but playable prototype of an idea I had about crashes and traffic management. I started it in the recent ludum dare but didn't have enough free time over the weekend to get something done so I figured I'd just finish it up through the week.
Basically, crash other cars, cause pileups, and stall the cops until you can get through the gridlock. There's only one level and it's very simple right now... if there's enough interest I may expand on it.
Possible full-fledged game of this would be something like infinity lanes rather than just 15 and various driving floats and food trucks and such that you can visit somehow. Basically a literal traffic world made of only lanes and driving endlessly in some one direction. Not sure how it would work exactly but I figured this simple first stab gives an idea of some of the mechanics around causing accidents.


Chrome 71 (December 2018) implements the new autoplay audio policy for the Web Audio API, which affects the Pico-8 web player. The BBS is OK because it implements a "curtain" that the user clicks on to start the player, which does the Web Audio enable interaction. But this breaks the exported web player as of Pico-8 0.1.11g: If I export a game to its own page then load the page, Pico-8 starts immediately and is disallowed sound. No interaction enables sound after this point.
One fix is for the exported web player to implement a curtain similar to the BBS. I don't know if that meets everyone's needs but would resolve the issue for the exported page. I assume we can work around this by implementing our own player curtain.
Interesting side note: This appears to affect stat() calls regarding sound as well. I have a cart that paused on stat(24) != 0, to wait for music to finish playing. The web export with sound disabled never gets past this point. I added a timeout for the pause to get around this, though I still don't have sound in this case.


Hey all, wanted to introduce my latest PICO-8 project: ZUBGUBBLERS!
ZUBGUBBLERS is my take on a minimal party game for 2-4 players heavily inspired by the classic game Qix, Splatoon, with additional inspiration from Frank DeMarco's Seam of the Vultures. I wanted to avoid using sprites for the most part and just leverage lines, boxes, and fills.
The goal is to paint as much of the background your color by the time the game is over. You do so by holding button 1 (Z) to expand a box around your player. Releasing the button paints the background your pattern; however, you can also hold a direction and dash (X) into other players. If another player dashes into your box while you are expanding it, the background is painted their color!


I notice that the YouTube field of the BBS profile only accepts alphanumeric characters, and whatever is entered becomes a link of the form www.youtube.com/<alphanumericfield>. I'm mostly ignorant of how this part of YouTube works, but my understanding is that not everyone can reserve a youtube.com/<alphanumericfield> URL. You need a certain number of followers, have qualifying channel art, etc. Everyone gets a www.youtube.com/channel/<randomlyassignedalphanumeric> channel URL, but I can't enter that into my BBS profile and get a working link.
There's some history with G+ URLs that I've forgotten the details of. It looks like anyone can reserve a www.youtube.com/c/<alphanumericfield> URL. At least I have one, not sure how. But I can't enter that in either.
I think the YouTube profile field needs to accept more values and/or provide hints in the profile form on how to link a profile to a channel.




If I type this:
Look at my `inline code` please. |
I get this, which I'm just going to let the BBS handle, so it might look right to anyone reading this after it's fixed:
Look at my inline code
please.
The second backtick isn't closing the inline code.
As an aside, I personally would prefer it if inline code were simply a monospaced font, and not inverted as it is now. It makes using inline code very ugly and hard on the eyes. :/
I do like the old-printer-paper code block format though. :)

