Hello there this is my first project in Pico-8. I always thought it would be fun to attempt to make a simple calculator for myself. the '=' button performs clear screen operations for now though maybe I can update it later with a proper dedicated button. anyway I hope you all like my little project!
0 comments
I was testing out various PICO-8 cartridges in the new version, including my own Rain Gif cart, and I discovered that when I chose the built-in "Save Gif" option, it would report that a GIF was saved to the desktop:
...but no file would appear.
On further testing, I discovered that on manually saving an image, it throws an error:
I'm not sure why this would happen - I've already checked whitelisting PICO-8 in my virus checker and that changes nothing. (And besides, I can save files and use the audio exporter just fine.) I'm running Windows 7 (yes, I know...) and installed PICO-8 yesterday using the installer download.
I'm loving PICO-8 with one exception: I'm not crazy about Lua. I've read the Lua documentation for OOP, but the table thing is so different and I can't find examples for what I'm trying to do.
I'm almost finished something I'm working on, but the larger the program gets the more I miss being able to separate the logic into objects (the way I'm used to anyway).
Long story short, I wanted to do the following:
Entity Class:
- x, y, width, height, speed, etc
- function update()
- function draw()
Player Class(that inherits from the entity class):
- score, weapon, power, etc
- function update(overrides but calls super function from entity)
- function draw(same)
Enemy Class(that inherits from the entity class):
- extra variables
- overridden functions calling super functions Entity class
SpecialEnemy Class(that inherits from Enemy/and then from Entity obviously)
- extra variables
- overridden functions calling super functions from Enemy class
I hope that makes sense. It looks like Lua doesn't really have a natural way to do multiple inheritance. Anyway, does anyone have any tips for how to implement something like this? Right now, I everything is just procedural.
Thanks.
In my qsort() thread:
https://www.lexaloffle.com/bbs/?tid=38679
If you click the "Code" button on the embedded cart and scroll down to qsort() or iqsort(), you'll see a line near the top of each function that says, if l then, but the line inside the cart is actually if l<r then, so if anyone grabs the code for the function, they get a corrupted version of it.
I'm guessing this, and possibly other, reserved HTML elements are not being escaped properly...?
Hi all, I'm working on a single-screen platformer in the vein of Bubble Bobble and Snow Bros., but with a lite-rpg twist. Let me know what you think! Only 8 levels now but there will be at least 16 in the final.
This is perhaps a bit off topic, or maybe not.
I just deployed a rough, first version of an online pixelart drawing app: https://pixla.nu/?ps=DyIAIQESCSIBIIICIRILIoEgAg8iACENIgACNiIBAAACCyIAIAF3AHALIgAHAncAAgoihAcAcAcCCiKEBwBwBwIKIgAHAncAAgoihAdwAHcCCiKDIHAAcAsigyB4gHALIgAHAXcAcAUiBBEAEAJ3AHALEQIAAAF_EUUR
It's meant to be limited in features, a little bit like pico-8 actually. The canvas size is fixed to 32x32, and the palette is fixed to the (original) pico-8 palette. Left button draws, right button picks up the color under the mouse.
Perhaps the most special thing is that the pixels are saved in the URL, so the images can be saved by simply bookmarking the page. The links are also easily shared on social media, and the preview includes the image.
If it's not clear from the screenshot, I can't draw. So I hope some people with some pixel art skills will find the tool fun and useful. Please try it out, and let me know of any problems or feature requests you might have!
Oh, the name of the site is in swedish. "Pixla nu" means "Draw pixels, now!", where pixla is the verb form of pixel and nu means now.
Bolygone Explorer
Doc
Comments
Learning Pico8 here is my first cardridge.
Idea comes from an old book about computer & graphics : Graphisme Scientifique sur Micro Ordinateur by Robert DONY (1986)
Hi all,
In preparation for an upcoming game jam, I've quickly recreated Cannonhead Clash, an Atari 2600 homebrew game that I first published almost a year ago. This version has quite a bit missing (no menus, no AI opponent, etc) but I hope you enjoy it regardless.
This game is a two player game where you try to hit the opponent with one of your bombs. By holding down either button, you charge your shot- the longer the charge, the further the bomb goes. Your bombs can destroy terrain, too, so keep that in mind!
If you'd like to see the original 2600 version you can find it here.
Changelog:
Version 2.0:
- Added title screen
- Added CPU opponent
- Added scoring
- Fixed infinite charging bug for Player 2
- Fixed bug where walk sound/animation would not play if left/right was held during the death animation
Palmix Wave Ver0.1
Invaders from the Pamix system are attacking the Earth! Clear the menace aboard the Space Fighter!
Palmix Wave is a vertical shmup with a set play time of 2 minutes (A la caravan game mode). In the game you will encounter many types of enemies included a miniboss and a final boss. You will also find powerups that will make the space ship faster and shoot more bullets. These powerups will also give you a brief invencibility time.
This is also like my formally first try (like no sfx or music) of a completed game in Pico8. I began with a shmup tutorial but in midway I wanted to try the ECS game programming pattern. With a quick search this ECS Pico8 ECS engine came up https://www.lexaloffle.com/bbs/?tid=30039. After a few tries I finally got the pattern and I liked it very much (code is not that pretty). Hope you like it!
A while back I posted an implementation of an in-place dual-pivot quicksort, which is the default sort algorithm most standard libraries offer these days. I've since tweaked it a bit to save a few tokens, and today I wrote up a sample cart that does some primitive testing as an example of usage.
This includes both a general 221-token qsort(), which can accept a custom comparator function (defaults to a less-than comparator for ascending order), and a tweaked 199-token iqsort(), which inlines the comparisons as simple "<" operators, producing a smaller and faster sort in return for the sort order and index not being customizable.
See tab 0's header comment for more details.
(Side note: I realized while implementing comparators that you could sneak in shuffle functionality just by sorting with a random coin-flip comparator. Handy.)
Edit: WARNING! Do NOT grab the function from the "Code" flyout on the embedded cart below! There is a bug on the BBS right now that deletes a "<" comparison! Click the "Cart" button to download the .p8.png version!
Feel free to use it in any way you wish. I didn't invent the algorithm, and the implementation was inspired by looking at several other people's implementations (which in turn were inspired by other people's implementations, and so on). I'm not going to claim any original work here. I just did some grunt work tidying it up and applying ducktape where needed.
Please let me know ASAP if you find any bug. I think it's solid, but I know I'm not perfect.
I couldn't resist making a cursed PICO-8 cart after someone sent me the What's Your Alex Jones Conspiracy Theory post on reddit by /u/dreggmuffin.
Given the subject matter "mad libs" is almost a double entendre.
(Press z/O button or x/X button to get a new conspiracy theory that you'll use to exploit the patriotism of your listeners!)
Cactus blocks are falling for some reason. You, a little frog named frog, have to jump and dodge out of their way. Set them up in lines in order to clear them off of your land.
-Pull them with your tongue while they're green and falling.
-Turn them into dust once they're dry, yellow, and set on the ground.
Just be careful using that tongue of yours. Getting squished is easier than you think.
.png)
-Raise your acrobatics game by upgrading your jump height and tongue length every time you clear 3 lines.
-Collect all the eyes and uncover the mystery.
-But most of all we hope you have fun!
Pullfrog is a game created by Joven Paul and Mario Carballo. Made in Pico8 over the month of June 2020. We had a ton of fun making it and we learned a lot. If you have any feedback about it, feel free to let us know! We want to balance it just right so all kinds of players can enjoy it.
-Thanks for playing
On 0.2.1, trying to INSTALL_GAMES with 0.2.1 gives me this error.
INSTALL_DEMOS seems to work fine, though.
Might this be connected to the 0.2.1 release notes saying:
"Fixed: Crash when INSTALL_GAMES / INSTALL_DEMOS without a writeable disk"?
Platform: macOS Catalina, 10.15.5
I'm working on a big project for PICO8.
Around the end of 2018, I learned about the scalability of multi-carting and continued to research and create it to this day.
We were able to give each of the four carts a role, rather than just being a data bank .
Cart 1: Title/Ending/3D dungeon scene
Cart 2: Platformer Scene
Cart 3: Cooking Scene
Cart 4: World Map Scene/Important Item Riddle Solving Operation
Because of these many factors, an hour or more of play is a must.
Data saves are automatic.
(Position when resume, growth and LIFE, possessions, time, status of NPCs helped, farmland, important items, roots, history of roots removed, history of enemies removed, and other things for cart-to-cart interaction).
Most of the game system is complete. I'm currently assembling the map for the later areas.
If anyone is planning an original, reasonably large game, PICO8 will be used as a prototype. It looks like they will progress the production and do the actual product in another game engine. I've seen some of those opinions. (Not my project.)
So sometimes what I do seems like a waste of time or laziness in choosing a development environment.
I don't see a lot of things planned in PICO8 from start to finish. It's not much.
Is it because of the scarcity that I am still developing? I don't think that's the only reason.
I'm not great at asking questions and such. Still, I've been able to implement a lot of features in the game because people before me have been posting and discussing their work repeatedly. Thanks for leaving the information, very grateful to you.
(I think the English translation is unnatural because it is a long sentence.)
Hey, I decided to make a batch script to automate compiling PICO-8 cartridges into .p8.png, binary, and HTML. Instructions are in the batch file and there's an example using Celeste included.
https://gist.github.com/FayneAldan/2ded1a13af0e2676ec259a12a702ae96
As of 0.2.1, mouse handling does not seem to work in HTML exports, though touch controls (and emulated touch controls with chrome dev tools) seem to be working.. It's fine in pico-8 and bin exports though, and in the BBS.
This is a simple typewriter style text box, like we see in many RPGs and Adventure games.
I was looking for examples of text boxes like these and only found complex and robust examples. They are excellent! But I thought it would be useful to have a simpler more "noob friendly" system.
The code is very commented, so anyone should be able to follow along and understand what it is doing. Also, this system is very simple but versatile. It can easily be expanded or customized if you know what you are doing.
After updating to 0.2.1, exports of my cart are failing to load. I've deleted just about everything from it to make a minimal reproduction here, but I have no idea what is going on.
For both HTML and bin exports, the pico-8 splash appears, and it hangs after "booting cartridge"
In the included cart, both the comment at the bottom and the init method are required. Deleting the init method, or any more from the comment will allow the cart to load. O_o
18 
|
Hi All! PICO-8 0.2.1b is now up on lexaloffle, Humble, itch.io, and for PocketCHIP. This update started as a continuation of 0.2.0 bug-fixing work, but I also relaxed my position on API minimalism just enough to add some new features :D
UPDATE: 0.2.1b is now live and fixes the print() bug, and a few other things. See the changelog below for details.
Ovals
You can draw ovals (technically, ellipses) both when running a cartridge, and when using the shape tools in the graphics/map editors. Ovals are specified by their boundary rectangle, and follow the usual draw state rules.
pattern={[0]=
…,∧,░,⧗,▤,✽,★,✽,
ˇ,░,▤,♪,░,✽,★,☉,
░,▤,♪,░,✽,★,☉,…,
∧,░,⧗,▤,✽,★,✽,★
}
function _draw()
cls(1)
for i=0,31/32,1/32 do
local x=64+cos(i+t()/8)*48
local y=64+sin(i+t()/8)*44
local w=8+cos(i*2+t()/2)*6
local h=8+sin(i*3+t()/2)*6
fillp(pattern[i*32])
ovalfill(x-w,y-h,x+w,y+h,
(i*32)%8+8)
end
print("pico-8 0.2.1",40,62,13)
end
|
Serial I/O
To make it easier to set up workflows for getting data in and out of carts during development, some new serial() channels are available. You can turn a file on your host machine into a binary stream, or drag and drop it into the running cartridge to do the same. From the manual:
Additional channels are available for bytestreams to and from the host operating system.
These are intended to be most useful for UNIX-like environments while developing toolchains,
and are not available while running a BBS or exported cart. Maximum transfer rate in all
cases is 64k/sec (blocks cpu).
0x800 dropped file // stat(120) returns TRUE when data available
0x802 dropped image // stat(121) returns TRUE when data available
0x804 stdin
0x805 stdout
0x806 file specifed with: pico8 -i filename
0x807 file specifed with: pico8 -o filename
Image files dropped into PICO-8 show up on channel 0x802 as a bytestream:
The first 4 bytes are the image's width and height (2 bytes each little-endian, like PEEK2),
followed by the image in reading order, one byte per pixel, colour-fitted to the display
palette at the time the file was dropped.
|
Drag and Drop
On a related note, you can also now drop .p8.png cartridges into PICO-8 to open them. If there is a cartridge with unsaved changes, it will prompt before continuing. You can also drop .png files into the spritesheet, by first selecting the sprite that should be the top-left corner location.
API Changes
add() now comes with an optional 3rd parameter: an integer that specifies the location in the table that the new value should be inserted at. Similarly, a new variation of del() is available: deli(tbl, index) ("delete by index") allows deleting from a given location in the table rather than by value.
split() is also new. It complements the common strategy of storing data as strings. From the manual:
split str [separator] [convert_numbers]
Split a string into a table of elements delimited by the given separator (defaults to ",").
When convert_numbers is true, numerical tokens are stored as numbers (defaults to true).
Empty elements are stored as empty strings.
split("1,2,3") -- returns {1,2,3}
split("one:two:3",":",false) -- returns {"one","two","3"}
split("1,,2,") -- returns {1,"",2,""}
|
Binary Storage
It is now also more efficient to store 8-bit binary data in the source code section, by encoding it as a binary string. The .p8.png format stores uncompressable sequences as a raw block of data, effectively allowing cart authors to choose how much of the code section to trade for raw binary storage.
Binary strings can be encoded by escaping characters that can't appear in the source code. For example:
0 should become "\000" (or "\0" when not followed by another number), etc. To make this easier, previously invisible characters C1..C15 have font entries, and also unicode replacements when copying and pasting. I'm working on a snippet for converting between data strings and raw binary data, to make this process easier. UPDATE: here's the snippet.
HTML Touch Support under iOS
Touch controls for HTML exports is now a little smoother, and works when running from inside an iFrame (including itch.io game pages). I removed the mobile buttons menu by default (the buttons along the top: fullscreen, sound, close) as they aren't very useful and are messy, but they can be turned back on in the options near the top of the exported html.
Changelog // added 0.2.1b
There are many other bug fixes in this update, but I haven't gotten around to replying to the BBS threads yet. For now, please check the complete changelog:
In the web player here on the BBS which currently says it's version 0.2.1, it appears print() now displays numbers as hex:
EDIT: oh wow I didn't realize v0.2.1 was out for real and not just in the BBS web version; I downloaded it and tried running the same cart (#xmasfish) and figured out how to reproduce it so I have corrected the title and description since my first report wrongly said the issue was with tostr()
as you can see here, it only displays as hex when x,y arguments are given to print():
