| |
Didi
Registered: Nov 2011
Posts: 479 |
Event id #2757 : Intro Creation Competition 2018
Preface: Please use this thread for questions, discussion and everything else concerning this competition.
After ChristopherJam had the chance to run a similar compo last year, this year I am back with the known ruleset, with only slight change.
Runnning the competition after X party turned out to be a great timeframe, so I stay there.
Competition runs from November 5th, 2018, until January 6th, 2019. So you have a full 2 months to deliver your creations. This should be enough for an intro.
THE RULES:
Your intro...
- has to work on a plain stock C64 (PAL standard) without any extensions.
- has to be a one-part intro. Short fade-ins and fade-outs are OK.
- has to contain at least one Logo at whatever size you like.
- has to contain a changing or moving text message (e.g. scrolling text, different lines fading in & out, etc.)
- has to contain music (not just a humming sound, please).
- has a maximum RAM footprint of $4000 bytes at one block, at whatever location you like. Screen RAM counts as used memory. Exclusions are system addresses like VIC (inkl. Color RAM), SID, CIA, Stack, Zero-page, IRQ vectors. This means RAM besides chosen $4000 bytes area and exceptions has to be the same before and after running the intro. What happens during runtime is up to you.
- has to be interruptable any time by pressing SPACE-key (exception are short fade-in and fade-out).
- does not need to have exclusive graphics, charsets or music. But the code should be exclusive, so reuse of existing code with just exchanged graphics and music is not allowed.
- has not been publicly used before entering the competition.
- has to be handed in as executable format startable with RUN (.prg or embedded in .t64 or .d64).
Maximum 3 entries per participant. Entries might be taken back from the compo until deadline. That means if you want to remove one of your works from the compo to make space for another entry from you, this can be done until deadline.
Deadline for entry submission is Sunday January 6th, 2019 at 23:59:59 (11:59:59 pm) CET.
Voting closes at Sunday January 13th, 2019 at 23:59:59 (11:59:59 pm) CET.
Voting platform is CSDb (with all disadvantages it may have), therefore entries have to be posted here.
Entries will be ranked by weighted average of CSDb votes. Entries with the same weighted average are ranked by their percentages of 10s, 9s, etc.
No prices to win, just the fame. May the best creation win! |
|
... 155 posts hidden. Click here to view all posts....
|
| |
Raistlin
Registered: Mar 2007
Posts: 575 |
I haven’t started my entry yet... can we extend the deadline by a couple of weeks? To make it fair, we just cancel all the entries so far so that everyone’s working to the same two weeks as me ;-) |
| |
iAN CooG
Registered: May 2002
Posts: 3138 |
lazy coders can enter next compo. |
| |
TheRyk
Registered: Mar 2009
Posts: 2097 |
or finish their stuff and submit it for BCC#13 ;) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11149 |
or procrastinate further! |
| |
Digger
Registered: Mar 2005
Posts: 422 |
I love your support guys ;) Thanks! |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
I have unfinished stuff as well, I'll just hope there's a ICC next year, which gives me a year to finish that stuff :)
Though I'll probably either forget about that, or delete it by accident. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1382 |
Yes, I started two other parts for this year's compo. Best get cracking if I'm going to have them finished by next year :) |
| |
deetsay
Registered: Aug 2005
Posts: 38 |
Quote: OK, so we're just to assume the 16k block has been loaded and SYSed into.
I remember I got into trouble with my first submission of Scharf for ICC 2016 by using the decruncher to initialize color memory. I'll learn my lesson one of these days :)
I just did exactly that too, but simply moved everything (including exodecrunch) to $4000-$7fff first, just to be sure. I'm being told it was unnecessary, but it seemed like the appropriate thing to do.
If it was OK to initialize excepted areas (colorram, SID, VIC, zeropage, stack..) outside the 16k area -- how would that make sense? Then it would be a "16k + about 1k + unlimited amount of initializer code" -intro. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Ah, by Wodan,
My entry uses $0800-$46a4, but it calls $ff5b in the init code, meaning it wipes $0400+.
I refuse to release a 1.2 version that doesn't do that. Invalidate my entry if that standard init code violates the rules (I also use $fda3 and $fd15). |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
Come on, Digger, you can do it! Two more hours to go! |
| Previous - 1 | ... | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | ... | 17 - Next |
