An arcade-ready remix of Mountains of Demise 2.
Difficulty has been balanced for maximum "arcadeness" (and profit if you really want to put it in your arcade).
Among differences from the original game are:
- intro loops
- Time for an Epic Quest (title theme) replaced with Mountains of Demise 3's title theme
- coin system
- no passwords
- option to disable continues
- service menu
To insert a coin, use the Tab key.
To access the service menu, use the Q key.
Original game below:
Here's my entry for ludum dare #38
All you have to do is taking the red flag on the opposite side of the island. If you success another flag will appear on the other side, and so on. Your time is refreshed each time you take a flag.
If you capture 2 / 5 / 10 / 15 flags you will unlock permanent skills.
If you reset the cart your skills and hi-score will be reset too.
commands are : <left> and <right> to run, <up> to jump and <up> again to explo-double-jump ( need unlock )
Please tell me your best score. have fun
Dungeon Generation API
This is a highly commented, thorough dungeon generation API that uses BSP (Binary Space Partitioning)
The generation in the demo is slower than needed, as it tries very hard to create interesting dungeons. Because it is generic, it can be used to create dungeons made of pixels, tiles using pio8 map, or something else.
DEMO
Usage:
genesis(width,height,max_depth,pathfn,renderfn,min_size) -> rooms, tree
Generates a dungeon using the BSP algorithm.
The width and height are arbitrary units that can be used for pixels, the pico8 map, or something of your own creation.
local rooms, tree = genesis( map_width, map_height, depth, on_path_render, on_room_render ) |
max_depth (int)
How deep the BSP tree gets. The greater the number, the more and smaller rooms are generated. For large maps, a higher number is useful, smaller maps, a lower number works better. The program will begin to decrease depth automatically if the process is taking too long. (decreases every second)
pathfn (function)
it is called with (x0,y0,x1,y1) where the coordinates make a line from two points, the line is always vertical, and horizontal. it always goes from center of a container to another center of another container. It is guaranteed to go from left to right, or top to bottom.
function on_path_render (x0,y0,x1,y1) line(x0,y0,x1,y1,6) end |
renderfn (function)
it is called with (x0,y0,x1,y1) where the coordinates make a rectangle called on your own by iterating over rooms and calling room.render() on each used to render tiles to the map, or to pixels.
function on_room_render (x0,y0,x1,y1) rectfill(x0,y0,x1,y1,3) rect(x0,y0,x1,y1,6) end |
min_size (int) (default: 8)
minimum room size before the room is not added to the rooms array, default is 8.
The program will decrease the minimum size automatically if it is taking too long to process, which is usually only the case when the minimum size is too high.
returns
A tuple of rooms and the tree. rooms contains data about each room in the map, and the tree contains traversable tree of containing cells primarily used for calling rendering functions.
Rendering
Assuming you have created something like the on_path_render and on_room_render functions above, you then iterate over the rooms and traverse the tree to render the map. In the demo, we use these functions:
function render_rooms() foreach(rooms, function(room) room:render() end) end function render_paths(node) if (nil == node.lchild or nil == node.rchild) return node.lchild.leaf:render_path(node.rchild.leaf) render_paths(node.lchild) render_paths(node.rchild) end |
Full Example
function _init() -- since we are rendering to pixels, -- we use the screen resolution local map_width=127 local map_height=127 -- define how deep our binary trie goes -- the higher, the smaller and more rooms you get -- for smaller maps, you should use a smaller number. local depth=6 -- declare how the paths are rendered function on_path_render (x0,y0,x1,y1) line(x0,y0,x1,y1,6) end -- declare how the rooms are rendered function on_room_render (x0,y0,x1,y1) rectfill(x0,y0,x1,y1,3) rect(x0,y0,x1,y1,6) end -- get our room and tree tables from -- the generator local rooms, tree = genesis( map_width, map_height, depth, on_path_render, on_room_render ) -- now we have our rooms and tree (technically trie) -- but they arent going to render themselves. -- to do this, we need to iterate over the rooms -- and the paths by themselves. -- create a function that will render all of the rooms -- by calling the render function on each of the rooms, -- the rooms themselves will then call the on_room_render function render_rooms() foreach(rooms, function(room) room:render() end) end -- create a function that will recursively walk down the tree -- and render paths between each container cell and -- rooms. which creates our hallways. it will end when -- it reaches the "bottom" of the tree, where a node does not -- have children. function render_paths(node) if (nil == node.lchild or nil == node.rchild) return node.lchild.leaf:render_path(node.rchild.leaf) render_paths(node.lchild) render_paths(node.rchild) end -- with our functions defined, we can now render the dungeon. cls() render_paths(tree) render_rooms() end |
Github
https://github.com/MattMcFarland/dungener
Installation
You can install this into your cartridge by copy and pasting all of the code from index.lua within the Github Repo.
When a cartridge exceeds the 65536 code size limit, PICO-8 0.1.10c crashes instantly when loading the .p8. It looks like an unchecked strcat() call that overflows past the allocate string size. Here is the Linux backtrace:
==4197== Invalid write of size 1 ==4197== at 0x4C2EA80: strcat ==4197== by 0x4A74D3: codo_load_pico8_cart_from_file (in /home/sam/pico-8/pico8) ==4197== by 0x4A753F: codo_load_pico8_cart (in /home/sam/pico-8/pico8) ==4197== by 0x40B9F1: load_cart (in /home/sam/pico-8/pico8) ==4197== by 0x4086B9: move_boot (in /home/sam/pico-8/pico8) ==4197== by 0x409E86: codo_main_update (in /home/sam/pico-8/pico8) ==4197== by 0x45EE76: codo_main (in /home/sam/pico-8/pico8) ==4197== by 0x57852B0: (below main) (libc-start.c:291) |

My Ludum Dare 38 game.
This is my first pico-8 game, and as such I had to cut about 3/4 of the intended features.
Please excuse the abhorrent collision detection and the rushed pixel-art.
If you do play and finish it, I hope you find that the slow walking speed wasn't too much of a waste of your time.
Protip: Try to avoid facing another object while dropping your current object.
Controls:
Arrow keys to move.
X/Y/Z to start pulling the item in front of you.
X/Y/Z to stop pulling.
This is a little fire experiment I've started playing with. It uses basically the same lookup table setup as https://hackernoon.com/pico-8-lighting-part-1-thin-dark-line-8ea15d21fed7 , although that may not have turned out to be absolutely neccessary.
What I'm happy with:
- controls
- performance
- overall look
What could use work:
- sound could respond to player actions
- smoke could drift a little more interestingly
What might be fun to add:
- setting other things on fire
- scorch marks or some other permanent trace
Thoughts are more than welcome!
Hello, all! Here's my entry for Ludum Dare 38! I'm glad that PICO-8 makes it so easy to iterate on little game ideas like this.
This is a game about cells and cell masses. Ride the currents to eat other cells, or just enjoy life as a floating, amorphous blob. Enjoy this as a maze game or just as a screensaver.
Use arrows to shift weight in current, or to traverse walls when stuck to them.
Move away from walls or press Z to dislodge yourself into the current.
This game is also posted here on Itch.io.





3 comments












