Go to file

saves a single cycle per bullet, but...

2025-06-24 23:16:47 -07:00

.gitignore

ignore vscode config

2023-12-21 23:30:17 -08:00

arrays_profiling.p8

profile-guided optimization

2025-06-23 01:37:57 -07:00

autobrake_test.p8

port improvements to autobrake_test too, excluding the weird calc_targets thing

2024-08-16 19:37:43 -07:00

code-of-conduct.md

Add code-of-conduct

2023-12-30 12:50:18 -08:00

collision_profiling.p8

initialization is very slightly faster this way, I think

2025-06-24 22:54:03 -07:00

collisiontest.p8

profile the drawing options

2025-06-08 17:36:50 -07:00

genericshmup-basic-collision..p8.png

Starting state: my generic shmup engine from a while back

2023-09-12 22:40:48 -07:00

genericshmup.p8

I am baffled I never noticed this before

2024-01-27 13:25:47 -08:00

genericshmup.p8.png

Starting state: my generic shmup engine from a while back

2023-09-12 22:40:48 -07:00

last_tyrianlike.p8

it's still tyrian-like so update last_tyrianlike

2024-09-02 15:09:27 -07:00

LICENSE

Initial commit

2023-09-13 05:37:53 +00:00

magnitest.p8

magnitest: cover image, png file

2025-06-08 16:16:16 -07:00

magnitest.p8.png

magnitest: cover image, png file

2025-06-08 16:16:16 -07:00

old_readme.md

remove readme from .p8 into a separate .md file

2024-12-24 15:04:23 -08:00

profiling.p8

fastest sqrt version, fix percentage

2025-06-08 16:14:18 -07:00

README.md

Initial commit

2023-09-13 05:37:53 +00:00

rearm_prototype.p8

clean up, run at 60 fps

2024-12-26 17:43:04 -08:00

the_parser.p8

Squash level_parser into main: parse levels in CSV

2023-12-20 14:09:07 -08:00

todo.md

update todo list

2023-10-01 14:39:34 -07:00

updatedshmup.p8

fix search-and-replace damage from a while back

2023-12-24 21:39:52 -08:00

vacuum_gambit.p8

reverse strip logic

2025-06-24 23:16:47 -07:00

zotprofiling.p8

profile the drawing options

2025-06-08 17:36:50 -07:00

README.md

mmbshmup

A Pico-8 shmup except it's a deckbuilder that is also Mega Man Battle Network.