@DarkestEx : cool idea! 99% of the code I'm using is not mine, and it seems it's GPLv2 (look at the headers), so you can use it under this licence. I'm still curious to look at @Juju 's one, which is probably more advanced!
Will you use 2 arduinos for this project, or something else?

I've asked the price for printing such small pieces, and it's around 20 €, it's 1/3 the price I paid for the whole console + shipping, so I think i won't make printing this, and I'll keep my bluetooth controllers!
3D printings are still damn too expensive...

A very good remake indeed.

Thank you Gameblabla! (and also to Julu for the original post)

I doubt they'll ever do this, but it seems there are some solutions: http://blog.nextthing.co/modify-pocketc-h-i-p-with-these-4-hardware-hacks/
A friend of mine has a 3D printer, I'll ask him to print the first one!

you can play exploration games, one button games (like my "rabbit, fox, hunter" ), or ones involving simple movements. For platformers like Celeste I think it's almost impossible. Maybe a new challenge?

Otherwise the CHIP community and developpers are nice, so it worths getting one in my opinion.

I've got my PocketCHIP recently. It's nice, but the keyboard is quite horrible: noisy, hard to type, much worse than my first android phone with physical keyboard. It's impossible to type fast with it, and difficult to actually play. You can't really type the two buttons for diagonals, and the clac clac noise is annoying as hell. I also don't really see anything I can't do instead with my android phone (with a bigger screen resolution and a chroot linux distribution).

Yet, I like this pocketCHIP: it is hacker friendly, it has wifi and bluetooth (you can use another keyboard, but I didn't manage to make another joypad work with it, but I think it's possible), it has GPIO, it's more like a raspberry with screen in fact. The object itself is cool and good looking (even if cheap). And it was affordable. It's also quite conveniant to use if for making music with Sunvox (with a nintendo ds pen). I've already installed syncthing on it for sharing data between my other computers.

I only regret I haven't bought an extra CHIP with it, because you can't just remove the CHIP from the pocketCHIP and use it on your TV (you have to reflash it to an other OS), but they're working on this, for having only one OS in the future.

they've already removed the download because they feared about nintendo's lawyers.

QuoteMaybe I should start a CYOA topic at some point?

yes, good idea!

I played/read many "livres dont vous êtes le héros" in my youth. I like that, but it's true the battles are not very interesting (I cheated every time I guess)

Nice WM juju, I like that. It's very smooth too (thank you new 60 fps mode)

The pico-8 gif export is not optimised at all, but it's easy to load the exported gif into GIMP, then use the "optimise gif" tool which will reduce it by a factor of 8 or 10.

The good thing with txt2tags (and most other lightweight markup langages) is you don't really need closing characters, for example your can write this kind of thing in txt2tags:

I **enjoy** //Casio// calculators, but I **love even more** the //TI// ones.

and it correctly will convert to:

I enjoy Casio calculators, but I love even more the TI ones.

it will certainly not convert to something like:  I enjoy Casio calculators, but I love even more the TI[/i] ones.  (which the bbcode doesn't even handle well)

The only thing you can't do is using such marks accross several paragraphs. If you really need to do this you can just mark the beginning and the end of every single paragraph. But marking in bold several paragraphs is not very meaningful, in this case if you need such a thing it's better to create a new "class" ("code", "remark", "important", whatever) and use this new class across the paragraphs. Because the other good thing with txt2tags is you can redefine your own marks, and you can decide to use closing characters if you feel so. It's what I did for some documents, for example you define them this way:


%!preproc: '\{\+\+\}'     'CONVERTsizeincBEGIN'
%!preproc: '\{/\+\+\}'    'CONVERTsizeincEND'


%!postproc(xhtml): 'CONVERTsizeincBEGIN' '<span class="big">'
%!postproc(xhtml): 'CONVERTsizeincEND' '</span>'


So I can use the {++}bigger font{/++} marks to make a part with this new style (I can do the same for bold or italic, for marking a whole area).

You can make whole books with that, for example:
https://mega.nz/#F!00Ix1TZA!Yj-GM6alhJplzLgS5K8_fw

(it's a choose your own adventure, in French, which I converted to epub, pdf and html using this syntax. If you can read French you can play it, it's a very good story, with a lovecraftian background)

I'm pretty sure it could allow both syntax (wiki and bbcode). Yet, I prefer to use the bbcode than the mediawiki (aka wikipedia) syntax, which is really one of the worst design ever made. For example, with '' for italic, ''' for bold, which mean you have ''''' for bold + italic.

But there is maybe worse, for dokuwiki, the heading is the opposite of the logic, for example heading level 1 is, instead of being one =, 4 or 5 = (or maybe 6?).

For converting between syntaxes, there is pandoc, which can input one markup, and output to an other one.

That's interesting, both the Shoes app and this script.

For all my documents, I'm using the txt2tags wiki markup langage. It's has a cool syntax (much better and logical than mediawiki).

http://txt2tags.org/

For example **bold** is for bold, //italic// for italic, __underline__ for underline, --strikeout-- for strikeout etc.
The advantage is you don't use extra letters (such as b for bold like in bbcode), and it's super fast to type (no need to use those [ ])

It can also export to several markup: markdown, mediawiki, bbcode, rtf (useful for making documents), laTeX, html etc

Some wiki such as dokuwiki, pmwiki and a few others can be adapted to use the txt2tags syntax.

 

I thought you were the only boss here...

I love this kind of game... and your looks very good!
It really gives the lust to play and explore it.

looks nice. I can't see it on the pico-8 forum, it's not online yet?