I translated the pico-8.txt into Portuguese so my niece could read it. I hope it is also useful for the community.
https://github.com/humbertoraposa/pico8/blob/master/pico-8_pt-br.txt

I decided to create a user defined language for pico8 in Notepad++.
I used the same color scheme as pico-8.
For those who don't know what this is, it changes the colors of text in Notepad++ depending on if the text is a command, a string, an operator (+ - = * /), or other keyword. Basically it makes Notepad++ look the same as typing inside of pico-8.
..Get Notepad++..
https://notepad-plus-plus.org/
..Download..
NP++ pico-8 user defined language xml
(Or you can copy and paste the Hidden Text into a text editor and use the file extension .xml.)

i thought i'd give an early preview of the falling sand game i'm working on:
there's not much to it yet; the only kinds of particles are air, soil, and sand, but i plan to add more and also have some more optimizations in mind. it took some work and a bit of luck to get to this point :)
controls
(while not holding o)
up/down/left/right: move cursor
x: place atom
(while holding o)
up/down: select setting
left/right: change setting
edit: shoot, does this web player also have bugs re: _update60? i'll try to alter the cart to make it work
edit: okay, seems fixed

The game isn't done, but I'll be working on it slowly but surely.
Use up/down to move your ship. Use Z or C to start the game or restart after crashing.
Speaking of which, the point of the game is to not crash.
This game mostly started as a demo sort of thing, but I'll make it more like a game as it goes on.
Current features: parallax map-based scrolling (Single or double map), palette trickery, a spinning spaceship, automatically generated levels/obstacles
Planned features: music, more levels, and enemies.
Changelog:
V0.5- initial
V0.7- Automatically generated levels/obstacles added

How much time do I have in _update()? Does the PICO-8 throttle the CPU at all, or do I have the native CPU's full processing power to execute LUA script on a single core?
This is an interesting question because my approach to solving problems changes entirely; given that it's a memory constrained environment with possibly a lot of CPU, I would avoid caching solutions to computable problems.
Can someone explain if the PICO-8 has any CPU limitations?
I am not asking how fast _update() ticks. I am investigating how many instructions I can fit in 30hz.

The Verge did a quick review of PocketCHIP and while most of it seems to focus on the complexity of Linux as an OS, they do talk about Pico-8. But it's less about Pico-8 as a platform and more so just talking about how using it on the PocketCHIP is quite difficult and unfun. Although, if the buttons are really that "clicky" then I can see how some games will be difficult-ish.
http://www.theverge.com/circuitbreaker/2016/7/19/12227806/pocketchip-review-portable-linux-computer
But I'm not buying it...I'm stoked to get my PocketCHIP and pretty much plan to use it as a Pico-8 handheld device only. I know it's a full Linux PC and that's cool but P8 is primary function for me, everything else secondary. We'll see but I can also tell that I've spent a lot more than $50 on crappier products (or even just for dinner this week).
And hey...Hug Arena pic! Woot!

Movement
I learned how to move an "object"/"pixels" around the screen while working through the Pico-8 Zine paddle game example. It seems to work well and I was quickly able to move the paddle back and forth. Very satisfying.
While looking at the source of other games I noticed they used a pretty similar approach. One thing they did use that seems more segmented is to use Tables to create key/value pairs for attributes of an object.
Coming from web development this looks suspiciously like an object...
The Hero
In this case I created a hero table and set some starting attributes:
-- hero
hero = {}
hero.x = 58
hero.y = 100
hero.sprite = 0
|
So the hero will use sprite 0 and start at x 58 and y 100 which is the lower middle of the screen.
[h2][b]move_hero()
update 2: so i guess the bare skeleton of the flow of gameplay is implemented. right now the three opponent players just discard a tile at random after they draw. you might as well do that too, since I haven't yet begun the process of implementing any of the actual rules of mahjong. (I'm sitting at 3309/8192 tokens right now, but my code is pretty messy.)
[b]update:

Hellou,
I think this is a very useful for everyone, who want create procedural maps.
Press Z key few times for smooth 'caves'.
EDIT: example is now as class.
How to:
... cave = TCellular:New() cave:Generate(128,116,0.6,4,5,5) ... function DrawMap() for xm=1,cave._w do for ym=1,cave._h do if (cave:Map(xm,ym)==0) pset(xm,ym,0) if (cave:Map(xm,ym)==1) pset(xm,ym,7) end end end ... |
I made this bit of code for creating a parallax effect for side-scrolling games. It uses three layers of infinitely repeating maps. I've set it up so that all the code is in a self-contained section that can be copied and pasted below your own code, with just an initialise, update and draw function needing to be called from the respective functions in your game.
More complete instructions can be found in the header of the code.
I hope somebody finds it useful!
:)

This is a little mech game. Its heavily inspired by one of my all time favorite old DOS games: BattleTech: The Crescent Hawk's Inception
It's little more than a proof of concept at this point, but I have big plans for it. I suck at sprite design so that's going to be my biggest hold up in getting this finished. The sound design is going to be interesting whenever I get around to it, too.
Thanks to @otemoto_stinger and his Grand Prix game I was finally able to get the background to move with each step. I also cribbed what little enemy code i have in this game from him as well.
BuzzKill is a classic arcade style shooter. Stop the onslaught of killer bees using your smoke and fireballs.

Features
- 10 levels of tough, bee-killing action
- High score saving
- Unlockable endless mode
Controls
- Arrows move left/right
- Z shoots fireballs
- X blows smoke
Gameplay
You must clear all bees, hives and honeycombs to advance levels.
Attacking uses power. The more power you have, the faster your shots. Stop firing to regenerate power. Keep an eye on your power meter.
Blow smoke to freeze honeycombs, slow bees and block shots. You can only shoot honeycombs when they're frozen.





1 comment





