Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccurate bombs #10

Open
BurpDerp opened this issue May 24, 2024 · 1 comment
Open

Inaccurate bombs #10

BurpDerp opened this issue May 24, 2024 · 1 comment

Comments

@BurpDerp
Copy link

BurpDerp commented May 24, 2024

In pico 8 version, bombs destroy only cracked walls. In here they destroy regular walls.

In pico 8 version ghosts standing next to you are always visible. In here they can be invisible.

In pico 8 version scorpions blind you for 29 turns. In here 30 turns.

In pico 8 version if you ascend while a monster stands next to stairs, you take no damage. In here a slime hit me.

I have noticed issue #1 too.

You can restart quickly by pressing start in pico version, that would be helpful to have.

Small graphical glitch: if you are at the bottom tile and try to move below, the character sprite flashes.

Thanks for the port, this is fun for gameboy. May i ask why are there inaccuracies, isn't porklike open source?

edit: More bugs

When i stepped on a trap, my character became gray. He should have stayed yellow. I'm playing GBC version.

Throw a bolt to down when you are at the bottom tile. The bolt comes out from other side of the map and hit you.

When you hold down the arrow key, our character stops for a second then continuously move. That stop is slowing the pace.

@BurpDerp BurpDerp reopened this May 25, 2024
@binji
Copy link
Owner

binji commented May 29, 2024

Hey, thanks for the great feedback! I'll take a look at fixing these things soon.

May i ask why are there inaccuracies, isn't porklike open source?

Sort of, the porklike tutorial is developed on the LazyDev's youtube channel, but the final porklike game (which this is a port of) has a lot of changes that were not included there. However, you are able to extract the Lua code to see the behavior. I just have made a few mistakes in the porting process. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants