"Oh My Blob!" is a turn-based puzzle action game where you play a knight fighting against a horde of different kinds of blobs.
Controls:
Arrow keys: Move/Attack
Z/X: Skip a turn (or "start game" in the menu)
Levels 1-28 are complete, 29 needs a bit of adjusting, after that it just ends unceremoniously with a glitchy screen.
I'd love to get some feedback on how it feels, if you get stuck anywhere, if you feel like you're learning how the different blobs work and so on.
Thanks for looking!
7 comments
My Father died nearly 20-years ago from today. Outside of my Sister and my Step-Mom, they are the only family I have now.
I remember my Step-Mom sending me the classic poem from Robert Frost.
And I remembered ... I remember when I was young.
https://www.writerscafe.org/writing/dw817/1260511/
So ... in tribute, I have two programs. One is to try and recreate that very program for the TRS-80 I typed in those so many years ago - and to have it run at the same speed.
The other is something a bit more magical. A year after the funeral I wanted to make SNOW, real snow, on the computer, and as accurately as I could. A majestic tribute to my Dad and that program typed in from so many years ago.
8 comments
I have never really liked to write code in BlitzMAX despite the fact it can work with a screen of 1980x1080 with true 64-million color pixels for a very simple reason. It takes time to compile the code and test it.
About 5-seconds to be precise, and that includes finding errors, even for a 2-line program.
My programming style if you are curious is a little like a rabid rabbit. It's like I take a cracker, nibble on it, look at it, nibble on it, look at it again, and nibble a little bit more.
That is - I write a bit of code, run it, add a bit more, run it again, then add a bit more.
My Dad was the opposite in that he could sit down and write a flawless program from beginning to end and NEVER have to run it once until he knew it was completely done. I can't do that.
So ... Pico-8 is a bit of my friend now for as you know when you RUN or press CTRL+R the language is already off like a shot and running.
Therefore I decided I could use it to write my Pico-8 website of favorite games.
9 comments
Here's my first video game with Pico8!
I know it's not very impressive but I hope
you'll have fun playing !
Defend the hen house from foxes
Edit 11/03/19:
Update I made for the game:
- New music
- Menu changes
- Bug fixing that occured explosions on the player
- Bug fixing that changed text color
- (TEMPORARY) Different enemy system: a fox attack every 30s
5 comments
im noticing as i import 3d file (magicavoxel to qb) the white is missing- i wonder if there is a way to fix this/import the white areas of the model...
0 comments
Controls
up arrow/down arrow: zoom in/zoom out
left arrow: show/hide debug information
z: multiply gravity by 10
x: turn off gravitational influence on player
Post
So, this is my second post. This time I'm posting some WIP of a gravity simulation I'm writing.
I'm not sure if this will ever turn into a game, maybe I'll just keep it as a "toy".
If you read "The Three Body Problem" by Cixin Liu and ever wondered how the trisolaran solar system worked, then take a look at the orbit of the planet in this simulation and imagine what it would be like, living on this planet. ;)
This cartridge implements a gravity simulation using a kind of modified newtonian gravity to make the simulation more stable for a simple toy like this.
2 comments
So, there is a parsing bug with the unique "+=", "-=", "*=", "/=", and "%=" PICO-8 flavored lua syntax. In normal lua, something like this:
b=odds[2]b=b-1 |
is valid syntax, treated as two separate expressions. That works in PICO-8, but this:
b=odds[2]b-=1 |
throws a syntax error. It's odd because this:
odds={1,3,5}b-=1 |
does not throw a syntax error. It seems to be only with the unique PICO-8 equals operators and directly after square brackets.
Fixing this could benefit people working on tweet carts as well as carts that are token & character/compression sensitive.
2 comments
how to play
Use z to accelerate and the arrow keys to turn.
Post
Hey everyone,
this is my first post here, so hopefully I'm doing everything correct.
I discovered PICO-8 around two weeks ago and was intrigued by its design philosophy. As someone who is only interested in Game development as a hobby, I love that basically all tools needed for developing a small game.
So I've been playing around with the program for the last two weeks and decided that the best way to learn how to use PICO-8 (and Lua, as I never used that language before) was to develop a small game.
The result is this small racing game against the time (as I don't have any idea how to write an AI for a racing game) with two tracks. The gameplay is nothing to write home about but I'm still quite fond of the end result.
In principle it's pretty easy to add more tracks, just "draw" them on the map screen with the sprites. However, I didn't bother to write a code that automates the finish-line or the creation of checkpoints along the track, so those have to be set in code.
Some small things I personally find neat:
Animated audience
3 comments
Made this little cart as I was working through coding a look-at type function. Wanted to post it in case it's helpful for someone.
This type of functionality is useful for all sorts of things. Maybe you just want one character to look at another or a gun barrel to follow the cursor etc.
3 comments
The more I've been experimenting with the #INCLUDE command, the more I'm realizing that when you compile to an executable that - well ... you're not.
You can test this quite easily by using my homebrew Pico-8 compiler.
It's very simple.
-- external p8 compiler -- written by dw817 -- note: you must compile this -- program to exe in order to -- use it cls() repeat flip() until forever |
First, type out this code in the P8 source-code editor. Don't add anything else.
Save it. Run it. Press F7 for a screenshot even though nothing is there.
Now remove those 3-lines of repeat, flip, and until forever.
Go to sprites, mapper, sound, add stuff if you want. You don't have to.
When you're done with that, return to the sourcecode and add just below cls() the line:
#include source.txt |
Now save this to a filename as a normal .P8 first. You'll get a warning that "could not #include file: source.txt". But don't worry about that. It worked. Then export as an EXE.
5 comments
I wanted to share a little work-in-progress I've been tinkering on.
Dungeon guy doesn't know what he's searching for. Maybe treasure? Maybe a way out? Maybe dungeon girl?
All he knows is to keep searching.
Levels are randomly generated and get progressively larger.
The only objective so far is to find the key and the exit door.
2 comments
Nibble in Cyberspace: #Digipres Adventures, Volume 1
Nibble lives in cyberspace but their very reality is crumbling before them. Help Nibble fight entropy itself by following good #digipres practice - collect strategy and policy to actively tackle the degradation of the digital world around them. Along the way, avoid all the risks, viruses, physical damage, power surges; and try and get your score high enough to avoid the complete collapse of cyberspace.
Nibble is an infinity game. The game will eventually self-destruct, but can you prolong its existence by following good practice?
Nibble in Cyberspace teaches players that good digital preservation will help our digital materials last longer, but there is a cost to inaction as well. Players are invited to get the highest score they can before the eventual collapse of everything around.
After all, you can't beat entropy, but you can fight it as long as you try.
0 comments
Zep, your front page HERE:
https://www.lexaloffle.com/pico-8.php
When I click on any of the games, the middle screen stays dark and does not load any game as intended.
I'm using Windows 10, 64-bit, Firefox Quantum v69.0.
If it doesn't work here chances are it doesn't work there for someone else. Thought I'd let you know ...
. . .
Solved. Just needed to clean the internet cookies for Firefox. Runs well here now.
3 comments
Hello.
Now that I've learned where the files are located, I've started to put together a little engine for myself that can create a nice list of Pico-8 games.
Here is what I've done so far:
https://dw-817-blog.tumblr.com/
sorry, had to shift some things around.
Hover over the cart to get a brief description and list the author.
Unlike embedding once you click the game it goes straight to the post in Lexaloffle where the game was released so not only can you play the game but read the author's comments, comments and questions from others, if you're logged in get a chance to add your own comments.
Special thanks to kittenm4ster and BoneVolt for their excellent programming and carts in the current list.
If it all looks okay, feel free to reply and post your game information and I'll add it to the list.
All I need is the URL address of where your game is (in Lexaloffle), it will look like this:
http: // www . lexaloffle.com / bbs / ?tid=00000
4 comments
.
.
This one is an oldie that some may remember. Wasn't the greatest of arcade games but for a time as a youth it was the arcade game I had the most access too.
Tried to make this pretty faithful to the original although I think it is too easy. Per the original there are two alien deployment patterns that alternate on levels. The large yellow UFO's also deploy as in the original. And the point value for the UFO's changes depending on the shot number you are on. Hint: 16th shot for max value.
29 comments
A demake of gamedesign.jp's "chat noir".
Updated, thanks to your valuable feedback.
Three difficulty modes:
- normal: 6 spots are blocked at start.
- easy: 12 spots.
- practice: 18 spots.
Visible distance is now a toggle and does not reset the current game.
Moves is now a separate setting, 1 or 2 per each of the cat's one move.
Wins are tracked in the upper left-hand corner. Plays are not counted.
Cartdata saves win count, difficulty, visibility, and move setting.
After a win or loss, the game waits for a button press to reset.
9 comments
Hello. As you know I've been recently experimenting with the new #INCLUDE command.
I have now recently found that if you use PRINTH it APPENDS text to a file, it does not overwrite it. If there is some way to overwrite the data, then this program could be run more than just a few times.
BUT IT DOES WORK.
You can indeed load a text file as data for PICO-8. Modify it. Save it back. Then re-run the program to see all the changes recorded without having to save anything to SRAM or 256-byte storage.
One problem I ran into is that #INCLUDE can also not be used in a comparison. For instance, this:
IF 1==0 THEN #INCLUDE DOESNOTEXIST END |
Will crash because it ignores any commands around it and WILL INCLUDE that data if it exists and crash if not.
Here is the program. It does work a few times. Can you make it so it's perfect and can be run over and over again ?
-- test load and save text file
-- by dw817
cls()
game_name=""
game_x={} game_y={} game_r={}
game_c={}
#include gamedata.p8l
repeat
cls()
print("name="..game_name)
for i=0,15 do
circ(game_x[i],game_y[i],game_r[i],game_c[i])
end
color(6)
print("",0,90)
print"left for new name"
print"right to clear name"
print"up to clear circles"
print"down to create new circles"
print"press 🅾️ to save"
flip()
if btnp(⬅️) then
game_name=""
for i=1,3 do
r=flr(rnd(17))+1
game_name=game_name..sub("bdfghjklmnprstvwy",r,r)
r=flr(rnd(5))+1
game_name=game_name..sub("aeiou",r,r)
end--next i
elseif btnp(➡️) then
game_name=""
elseif btnp(⬆️) then
for i=0,15 do
game_x={} game_y={}
game_r={} game_c={}
end
elseif btnp(⬇️) then
for i=0,15 do
game_x[i]=flr(rnd(128))
game_y[i]=flr(rnd(128))
game_r[i]=flr(rnd(16))+16
game_c[i]=flr(rnd(15))+1
end
elseif btnp(🅾️) then
t=""
t='game_name="'..game_name..'" '
for i=1,4 do
t=t.."game_"..sub("xyrc",i,i).."={"
for j=0,15 do
if (i==1) v=game_x[j]
if (i==2) v=game_y[j]
if (i==3) v=game_r[j]
if (i==4) v=game_c[j]
if v!=nil then
t=t..v
if j<15 then
t=t..","
else
t=t.."}"
end
end
end--next j
t=t.." "
end--next i
printh(t,"gamedata")
sfx(0)
end
until forever
|
5 comments
Will post here my experiments with particle effects...
Experiment 1: Fireworks... basic explosions
version 1: very basic approach
version 2: added gravity pull and callback update/draw for particles to operate multiple particle types (f.e. rocket and spark in the test)
Experiment 2: Additive blit particle fire
version 1:
3 comments