pouët.net

As for the original question, it's very fair for the orgas to be considering something different. One-scene is a great idea and seems to be seeing success where it's implemented (demobit and asm come to mind, and I believe there are others). Maybe have a 64k workshop this year (and maybe drop the compo this time, or not) and ask again next year? :)

One scene is a great idea. I love a good 64k intro but as an author of a potential compo entry it feels daunting to start working on one. A single scene on the other hand...

if you think the one-scene was a success on the demobit then on the other hand you should see: one-scene killed the intro compo: look at the result. This was the only one reason how I was able to finish 2nd place on a combined intro compo with a 512b prod. (although it's great in its own category).

Usually an 1k intro has only one scene (the 256b intro the same). Making clear the situation, imho it would be a good addition rule for one-scene compo - the intro size must be larger then 1k (or 4k).

A dedicated pico-8 competition would be nice, seeing as it's one of the few new things with some successful demoscene outreach in the last few years.

I like the idea of a pico-8 compo.

Ask Photon.

rimina: how many entries do you want? :)

It's not only me who decides these things but also the compo organizers and main organizers of the event. So asking from me how many entries I want is kind of irrelevant. But since you asked I'd like a good compo where makers feel good to compete each other and viewers have a good time watching. Like what else can any compo organizer ever want? I don't think there is any absolute minimum number of entries to that but if you want some arbitrary number I would say at least 5 entries from different makers.

Oh and I like how much different kind of suggestions and good conversation here has been about the compos! Keep it up! We will definitely consider the feedback!

I also think a PICO-8 compo would be great! Of course, I have selfish reasons for thinking so :) But also because 4mat has a good point. I think PICO-8 is one of the best alternatives out there for potential demo coders to dip their toes, and a compo might encourage people to give it a shot.

Of course, PICO-8 does cost money, which could disincline some. The PICO-8 license does allow it to be used for workshops, and while the license probably isn't suitable for Assembly as it is (it's a site-wide license allowing installing on on-site computers specifically), it might still be a good idea to contact Zep and ask him if some details can be worked out.

Using Pico-8 for a workshop in the Scene Lounge wouldn't actually be a bad idea :)

*cough* how about allowing TIC-80 as well? *cough*

Heck, a combined compo for fantasy consoles/computers would be great, provided that voters understand that PICO-8 has rather strict virtual limitations compared to TIC-80.

Fantasy platforms in general are a very welcome throwback to 8-bit computers that booted right into a BASIC interpreter. I think the built in development tools do a wonderful job at removing an initial threshold to getting your first things done, even though once you really start getting serious, you'd never choose the PICO-8 code editor over any decent text editor :)

I could get behind a fantasy compo as long as custom (eg. FPGA) platforms are allowed instead of necessarily restricted to a few arbitrary ones (this is purely motivated by my own late 90's accelerated platform so understandably a bit arbitrary but the point still stands).

Not to weigh in on either side of the scale(s), but how is that at that point different from a wild compo though?

It's not :)

A Pico8 compo could be fun.

Of course, as Gargaj said, if this compos opens up to TIC-80 ( which is already a whole different game ) and FPGAs, then it's basically a wild compo ¯\_(ツ)_/¯

Ditto for a workshop. That could be a good idea.
I'm pretty sure the site wide / teacher's licence term applies. I do run a Code Club at the local school using Pico-8 and Zep was really supportive and helped a few kids get a licence at a discount. Super nice chap all around!

I feel I should defend the TIC-80 here even though I'm happy for a compo to be pico only or have both.. Yes, the tic has less limits, the lack of a token count and the cpu limiting being the main things, but it has to fit everything in 64kb the same as the pico and doesn't have other things that the pico 8 has, like patterns or a huge amount of example code and tools online. You can get around the unlimited cpu by forcing the entries to have to play in the browser (where it would be equivalent to the pico-8), and then it's not so different then having the atari st and amiga 500 in the same compo.

I don't know enough about FPGA to say whether or not that would be a fair fight, but not allowing LED arrays and other physical entries (which iirc have done well at assembly wild in the past), would make it a different more accessible compo imo. At least for the fantasy consoles, the open source of all existing demos means there's a low bar to entry, they're fun to make, and I think you'd get more first timers trying their luck. A rumour that there was going to be a pico-8 only compo at evoke is what got me to learn it, and having a compo at assembly (or another big party) is probably to get more people to try making demos..

So TL;DR, good idea whether it's just pico-8 or a wider compo

(Also if you want to code outside of the tic-80's text editor you are supposed to pay for a "pro" edition, and jobe is very right about FC editors :)

a tiny intro (256byte) competition please