Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user jmi ! (Registered 2024-09-15) You are not logged in - nap
CSDb User Forums


Forums > CSDb Entries > Event id #2416 : First CSDB "Unintended OpCode coding competition"
2015-10-03 19:53
Monte Carlos

Registered: Jun 2004
Posts: 355
Event id #2416 : First CSDB "Unintended OpCode coding competition"

Just wanted to make my new compo idea more visable to the audience:

First CSDb "Unintended OpCode coding competition"

(unintended opcode coding competition)

Feedback welcome!
2015-10-03 20:35
Digger

Registered: Mar 2005
Posts: 423
Yay! Neat idea, however I am against the rules of what the demo must contain, i.e. sprites, 1x1 scroll, PETASCII etc. Would it not be better if that stuff was optional? Just keep the focus on the code ;-)
2015-10-03 21:39
Monte Carlos

Registered: Jun 2004
Posts: 355
Thank you for your opinion.
Let me explain my thoughts:
At first the restrictions are not really restrictive and hard to fulfill. Sprites and credits/scroller resemble common elements in demoparts and so are easily justified.
Contrary PETSCII is not really common in demoparts, but it has a long tradition in C64 demomaking and could maybe serve as something like the corporate design for all contributions of this compo.
At second i would like to have some common elements between different contributions so
1st) They are better comparable
2nd) One can see how different coders deal with these elements
3rd) There is reference to this compo, there are credits
4th) there is at least some screen sub-division making it look not too bulky
2015-10-04 08:16
Bitbreaker

Registered: Oct 2002
Posts: 501
Will there be extra kudos for proper use of TAS/LAS? :-D Will it be necessary to deliver also sourcecode?
2015-10-04 18:02
Monte Carlos

Registered: Jun 2004
Posts: 355
Its up to the competitor to make clear what's so special about his contribution. There is no rule to publish source but for some codep0rn project it would maybe be the best solution to make it understandable to the audience.
Proper use of LAS/TAS will be revarded by hugs and (schlabber)kisses from Monte Carlos himself.
2015-10-04 19:04
Digger

Registered: Mar 2005
Posts: 423
I'd say source code is a must. Otherwise we won't learn anything ;-)
2015-10-04 19:43
tlr

Registered: Sep 2003
Posts: 1762
Nah, just disassemble it if you want to know how it works. Codepr0n is only pr0n in its binary form.
2015-10-04 20:49
enthusi

Registered: May 2004
Posts: 675
Well, the rules state that 'your' opcode must be crucial for the part. Without a comment such as 'I use SHIT to convert colors to frequency tables' its kinda pointless.
2015-10-05 10:25
Monte Carlos

Registered: Jun 2004
Posts: 355
Well, subtile efforts will not get the deserved reward if nobody knows whats going on behind the scenes. Therefore i would strongly recommend thinking about publishing sources or at least add some explaining words. Anyway it's too early to change the rules so this will stay as a recommendation.
It's you who want to get high votes.

The rulez state:
The demo must
- show a main effect which uses UOCs
- must have a relation to UOCs in everything even if it's heavily constructed
- emphasize on coding and the main effect

They leave room for other art than coding although the focus should be on the main effect using UOCs and the coding.
However, the part should be rated for the coding efforts and overusing of design elements may lead to unclear situations where one does not know if the vote applies to a good logo or music theme instead of the code.
Therefore the second restriction was added so that everything in the part is related to UOCs.
Of course there's the phrase "heavily contructed" which means, you must not use UOCs for every design element but you should somehow make a connection to UOCs.
For example you could do a main effect using UOCs and a banner stating "me hates UOCs" or "saxalolax". Be creative.
Everything which is not explicitly forbidden is allowed.

Please make the demo as a one screener which i meant as beeing also a one parter.

If the compo will have a good resonance, i would be willing to rise a second compo. In this case, extreme parts, like all border sprite multiplexer, which leave no room for anything else, could be submitted then.

Have in mind that this is the first compo concerning UOCs and if it's not perfect there will be room for improvement in some following compo. Don't take every misunderstanding of compo rules too serious.

I really look forward seeing the first submissions.

Very curious Monte Carlos
2015-10-05 17:23
soci

Registered: Sep 2003
Posts: 478
Rules are meant to be broken ;)

Might as well wait a few iterations until this compo is fully debugged ;)
2015-10-05 18:52
Monte Carlos

Registered: Jun 2004
Posts: 355
Politics is the best example how to interpret rules most extended ...
Soci: Please do not wait, if you have a good idea fitting into this compo ;-)
 
... 19 posts hidden. Click here to view all posts....
 
Previous - 1 | 2 | 3 - Next
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
Darkflight
haschpipan
Guests online: 129
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Coma Light 13  (9.7)
4 Edge of Disgrace  (9.6)
5 Mojo  (9.6)
6 Uncensored  (9.6)
7 Wonderland XIV  (9.6)
8 Comaland 100%  (9.6)
9 No Bounds  (9.6)
10 Unboxed  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 Rainbow Connection  (9.5)
6 It's More Fun to Com..  (9.5)
7 Dawnfall V1.1  (9.5)
8 Onscreen 5k  (9.5)
9 Daah, Those Acid Pil..  (9.5)
10 Morph  (9.5)
Top Groups
1 Booze Design  (9.3)
2 Oxyron  (9.3)
3 Nostalgia  (9.3)
4 Censor Design  (9.3)
5 Triad  (9.2)
Top Original Suppliers
1 Derbyshire Ram  (9.7)
2 Fungus  (9.3)
3 Black Beard  (9.2)
4 Baracuda  (9.2)
5 hedning  (9.2)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.052 sec.