Hi, it's my first day of tinkering with Pico-8, so bare with me.

Is there a way to use a external text editor to code? I miss my vim key bindings.

Thanks!

This was driving me mad. Some tracks would play fine, others would have a clicking sound after all the notes.

The default instrument is 0, so right now you have to set the instrument of all empty spaces to be the same as the note before it (via shift-click or manually if there are instrument changes). I think the music code is switching over to the new instrument too early, and the change in height in the sound data is causing a pop.

Well this is my first test. Feels like the good old times....

Star Scrolly 0.1

Cart File | Forum Post |

	More cartridges by johnnyri

More Cartridges [View All]

 

Star Scrolly 0.1

by johnnyri

Cart #13255 | 2015-08-29 | Code ▽ | Embed ▽ | No License

3

I'm building a simple game to play around with Pico-8 and having a great time so far. Nothing special but I decided to try out the map editor and place a few collision-enabled tiles around the screen.

There are a few things that are confounding me at present:

1. the co-ordinate system in the map editor. Am I just missing the tooltip that tells you what the x/y is of a cel the mouse is presently over?

2. Drawing a map to the screen. The pico8.txt file says I can use the map function to draw regions of the map to the screen. I can then use mget to get a tile out of the map and fget to get flags. I gathered this much from reading the jelpi source.

However I can't seem to figure out how the map co-ordinate space is mapped onto the screen co-ordinate space. Jelpi's collision code is very simple but I can't seem to replicate it; my screen space is off from the map space and I can't figure out how they line up or translate from one to the other (ie: my player is in screen co-ordinates and I need to use a bare-bones AABB search along the X axis to find collision-enabled tiles.

I feel like I'm just missing some key concept here (could be that it's also pretty late).

I wanted to try some PICO-8 cartridges...

And I just bought this new mini gamepad...

So I thought it would be fun to get it working with PICO-8! :D

The gamepad is a small, keyring size bluetooth controller. It costs around £3 on Amazon.co.uk

It's really meant for Android and iOS, and has various modes of button configuration. However, when connected to my iMac it's seen as an iCade controller (as it is on iOS).

I used ControllerMate OS X app to remap the iCade controls to cursors+z+x+shift+esc. And it works great!

Here's the setup file: http://cl.ly/290U3s2z3I0w

Maybe there's similar software for Windows & Linux to use this little gamepad? Maybe PICO-8 could add iCade support so we don't have to use external software?

Anyway! That is my nice little PI-CO-NTROLLER for PICO-8

:)

If you want to try this, feel free to ask questions!

3D Dungeon 0.2

by AfBu

Cart #13244 | 2015-08-28 | Code ▽ | Embed ▽ | No License

16

Recently I started playing with raycasting and I immediately wanted to create a real game with it, so here is first preview of my 3D suqare dungeon.

V0.2 features:

• wall text system
• portal system
• ground/ceiling color can change in locations
• item system (food+gold)
• gui (health, gold, experience/level, compass)
  Notable bug: when you try to read text that is not defined it's id will popup on screen and game will be stopped.

V0.1 features:

• raycasting engine with dynamic rendering quality for smooth movement
• collisions based on tile flags
• 16x16 pixels textures
• 8x16 pixels transparent sprites rendered using simple (column based) z-buffer
• basic npc system that allows random movement of monsters around map

Controls: arrows for movement

Original 3d experiment thread is here.

[ Continue Reading.. ]

3D Experiment 0.3

by AfBu

Cart #13694 | 2015-09-04 | Code ▽ | Embed ▽ | No License

25

Simple ray-caster experiment.

It's not perfect, but it's kinda working and I hope it can serve as starting point for some awesome 3D games - especially I am thinking about some cool dungeon/rpg, that would be awesome!

Controls: arrows to move

Update 1.1:

• added fish-eye effect reduction
• added dynamic quality settings (when camera moves, quality is lowered)
• draw distance, step & quality setting can be adjusted in code

Older versions:

3D Experiment 1.0

by AfBu

Cart #13194 | 2015-08-27 | Code ▽ | Embed ▽ | No License

25

[ Continue Reading.. ]

Hi zep! Just a small suggestion, but I'm finding the low-resolution cursor movement really quite awkward to use when I'm so comfortable with existing graphics software on the PC.

Would it be possible (as an optional setting) to either:

a) detach the in-app cursor from the 128x128 grid by creating some special rendering code independent from the console display?

b) hide the in-app cursor and show the system cursor instead?

What are others' opinions on this? I suppose it's not a major issue for most people, and I completely understand if you don't want to do it, to preserve the style/feel of the console. :)

Tennis Galaxy 1.0.0

by JScott

Cart #13183 | 2015-08-27 | Code ▽ | Embed ▽ | No License

5

This is my first Pico-8 cart that helped me learn the system and tools. Despite that, it's decently polished and surprisingly entertaining so I wanted to share it with you. It doesn't have a title screen, a lesson learned for the next cart, so the controls are:

up/down - move the paddle
a - slow the paddle for more precision
b - continue to a new game

I also upload my carts to GitHub if anyone's interested in the code, which is probably the best part.

I didn't see this documented anywhere, and I had to work it out for my drumbeat cart, so I thought I'd save everyone else the trouble and publish what I know.

SFX:

A sound effect is stored in 68 bytes. Sfx 0 starts at address 0x3200, sfx 1 at address 0x3244, and so on.

The first 64 bytes (offset 0..63) store the 32 notes of the sound effect as described below.

Offset 64 is a byte that determines the editor mode: 0 for graph mode, nonzero for tracker mode. This has no effect on playback, just on the mode opened in the editor by default.

Offset 65 stores the playback speed. (Higher values correspond to slower playback, so "speed" isn't exactly the right name, but that is what is used in the editor.)

Offsets 66 and 67 store the loop begin and loop end times. A sound effect contains only 32 notes, but these times may be set to any byte value. All times past 32 simply play silence.

Note format:

A note is stored in 16 bits, two bytes little-endian.

Bits 0..5 store the pitch, ranging from 0 (C in octave 0) to 63 (D# in octave 5). The tracker mode editor can only enter pitches up to 60 (C 5), but it can display and play higher pitches.

Bits 6..8 store the instrument; the values are the same as in the tracker mode editor.

Bits 9..11 store the volume. Volume 0 corresponds to silence.

Bits 12..14 store the effect; the values are the same as in the tracker mode editor.

Bit 15 appears to be unused.

[b]Example code:

[ Continue Reading.. ]

I never used LUA before (I come from JS and Ruby), today a saw a bit about OOP here and since pico doesn't support metatables i'd like to know if this is the right way to OOP:

local player = {}

function Player.new()
    local self = {}

    self.x = 64
    self.y = 100
    self.width = 20
    self.height = 5
    self.color = 7

    self.get_x = function() --one way for method
        return self.x
    end

    function self.set_x(new_value) --another way for method
        self.x = new_value
    end

    function self.draw()
        rectfill(self.x, self.y, self.x + self.width, self.y + self.height, self.color)
    end

    return self
end

function redraw()
    rectfill(0,0,128,128,0)
end

function _init()
    player1 = Player.new()
end

function _update()
    local x = player1.get_x()
    player1.set_x(x + 1)
end

function _draw()
    redraw()
    player1.draw()
end

So... If there is anything wrong* there please tell me :), i know i could make a player.move method but i wanted to see getters and setters visually.

*I do consider anti-patterns as wrong.

Swirlthing

by Connorses

Cart #13131 | 2015-08-25 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

6

I had to make a workaround to prevent the square-root-of-zero bug from making PICO-8 freeze.

DISCLAIMER: I have little or no understanding of the math behind this, I just threw it together and chanced upon a cool swirly pattern. Yay me.

I'm curious as to how people look at the Pico8. While it is it's own thing completely unlike any other real console, it does share some similarities to quite a few of them, if changed somewhat still. I myself can't be helped to be reminded of how similar it's sprite capabilities and FPS being locked to 30 and color output are similar to the Atari Lynx and so I tend to think about games I would've loved to have seen on it (though the sounds on the Lynx is way better! lol) .

However, I think Pico8 also does a good job of feeling like a Gameboy Color or Palm Pilot OS3 type device as well, maybe a NGP?

Does anyone else think of the Pico8 as some kind of way to feel like your idea for some console-specific game to come to life or does everyone else kinda just shrug and think 'this is pico8, this isn't anything else at all'?

There's really no purpose to this question, just more of a curiosity about other people making stuff on it...

Hi,

I'm trying out the pico-8 amd64 linux build and can't seem to exit properly. Ctrl-q and super-q halts pico-8, but the SDL is still rendered on screen. I have to restart my window manager just to be able to do anything. Is there a way to get a verbose mode or some kind of logging?

Directories seem to be in order and I assume the file permissions are as well. If anyone has any information regarding this, it would be much appreciated.

Thanks!

Hello, anyone knows how "files" from system api works? I want to have all cartridge names in array or something like that...

• I tried to use it as function - it's a nil value
• I tried to print it - result is "false"
• I tried to iterate using foreach(files,print) - nothing happened

Am I missing something or this is not yet implemented?

Thanks.

function mchk(x, y)
 return mget(flr(x/8),flr(y/8))
end

function move(x, y, w, h, dx, dy, col)
 w-=1
 h-=1
 if dx < 0
 and mchk(x+dx, y) != col
 and mchk(x+dx, y+h) != col
  then x += dx
 elseif dx > 0
 and mchk(x+w+dx, y) != col
 and mchk(x+w+dx, y+h) != col
  then x += dx end

 if dy < 0
 and mchk(x, y+dy) != col
 and mchk(x+w, y+dy) != col
  then y += dy
 elseif dy > 0
 and mchk(x, y+h+dy) != col
 and mchk(x+w, y+h+dy) != col
  then y += dy end

 return x, y
end

As an exercise, I wrote a small general-purpose collision script and thought I'd offer it up for folks new to P8 or relatively inexperienced with programming.

This is purposefully not a one-stop solution, but it may get you going. It is probably more in the spirit of PICO-8 to come up with specified collision routines yourself. At the very least, there's some study value here.

Things to consider:

• This was built to collide bodies <= 8 pixels wide and tall. With some thoughtful fiddling you can get it to accommodate bodies of any size, but I kept it this way for brevity.
• It takes up 226 memory.
• This is made for colliding against maps only.

mail-monster 0.1

by flygfarkost

Cart #13105 | 2015-08-25 | Code ▽ | Embed ▽ | No License

12

Here is my LUDUMDARE33 jam entry. Everything was made from scratch and in less than 48 hours but I couldn't schedule my weekend well enough so I had to submit it to the jam.

You are the mail monster, pick up the mail without ruining the whole town! (You get a time penalty if you happen to destroy anything)

ARROWS TO MOVE+C TO JUMP

Here is the LD page: http://ludumdare.com/compo/ludum-dare-33/?action=preview&uid=290

The Ancient Immortal 0.11

by Elven

Cart #13098 | 2015-08-24 | Code ▽ | Embed ▽ | No License

4

My take on the Ludum Dare #33 "You are the monster" theme. It's a tower defense game where you play as an evil deity stuck on Earth. Grow your limbs to exterminate those puny humans trying to kill you! Survive until 2500 A.D. to win.

There are 7 finished monster limbs / parts and 20 human units divided into 7 eras and 2 game modes.

Many things are broken, and performance isn't that great (damn you projectiles!). Needs audio and more art.

I plan to optimize and polish it later on.