Log In  

@tyroney

Follow
Follow

I remember apple II and qbasic fondly. Still bummed about all that visual stuff. Pico 8 is almost as much as I want. But what do I want?

And you thought the ArduBoy sounded neat.

https://www.adafruit.com/product/4200
They're working on porting NES emulation, and it comes with CircuitPython, so maybe a pico8 implementation wouldn't be out of the question.

That said, I might just pick one up and get busy. Who needs only 128 horizontal resolution and a static color palette?

P#64265 2019-05-09 17:36 ( Edited 2019-05-09 17:42)

While I continue my hiatus from working on silly-detailed platforming, I thought I'd workshop camera scrolling. I enjoy adventurey things, and using the camera to "hide" areas and enhance transitions has always felt good to me.

I could just use map flags and get per-tile camera control, though that might be more detailed map work than I want to do. (every boundary might need two lines of camera tiles: [main area]<->[reset]<->[show]<->[secret area] )

A little less involved would be minimap-scale flagging, which could be stored as an array, or just as pixels in an unused area of the sprite/map memory. (pixel per "screen", flagged for camera "edges" "corners" and "secrets") Tracking it this way might also be handy for music switching, atmospheric effect triggers, etc.

Now that I compare the two above techniques, per-tile flags might be nice to avoid getting stuck with screen resolution for secret area boundaries. Plus with a minimap scale, you're essentially adding a second fuzzy layer of tile-detection on top of any map tile checking already happening for collision and such.

Any thoughts or handy shortcuts that haven't occurred to me?

P#63266 2019-04-05 18:58 ( Edited 2019-04-05 18:59)

Cart [#27372#] | Code | 2016-08-26 | License: CC4-BY-NC-SA | Embed
1

Got things mostly working. (but still borked on right walls and cornes) Placeholder camera implemented, want to add dead zone and false boundaries to it eventually.

Taking an official break of sorts while I contemplate robust collision (and probably slopes) offline. I've made some progress on the theme/flavor, but I'm still keeping that to myself while I hammer on the basics.

Strange, editing the post I got the bbs to eat all my previous version. Broken tags below.


0.15 - Here it's half-working with all sorts of fun debug displays added.
Cart [#27096#] | Code | 2016-08-20 | License: CC4-BY-NC-SA | Embed
1

0.14 - First pass at something resembling collision; completely broken for the moment. But don't offer assistance yet! When I get back home I'll have time to dig in it and see what has transpired.

Cart [#27062#] | Code | 2016-08-18 | License: CC4-BY-NC-SA | Embed
1

ver 0.13 - I needed a little air control, too

Cart [#26786#] | Code | 2016-08-12 | License: CC4-BY-NC-SA | Embed
1

ver 0.12 - Here, have a jump

Cart [#26783#] | Code | 2016-08-12 | License: CC4-BY-NC-SA | Embed
1

ver 0.1 - just trying to lay out some of the basics - no collision, vertical movement, or really anything so far.

Cart [#26752#] | Code | 2016-08-11 | License: CC4-BY-NC-SA | Embed
1

P#26753 2016-08-10 23:08 ( Edited 2016-08-26 03:10)

In my opinion, pico-8's musical notes don't go nearly low enough.

In addition, its UI assigns numerical values to notes' octaves which are off by 2. (A middle C in reality lies at the bottom of octave 4. In pico-8, its octave is labeled as 2)

Personally, I would love pico-8 to at least cover the range of a traditional 4-string bass guitar, down to e1. (in the 1.8 UI that note would be labeled as octave -1) Even better would be getting all the way to octave 0.

(also, I'm aware I can put a track in "slow" mode.)

P#24751 2016-07-06 19:51 ( Edited 2018-06-12 01:54)

Backup should also exist when overwriting the cartridge in memory with the load command...

P#21166 2016-05-23 15:05 ( Edited 2016-05-23 19:05)

About | Contact | Updates | Terms of Use
Follow Lexaloffle:        
Generated 2019-07-23 23:12 | 0.071s | 4194k | Q:61