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


Forums > CSDb Feedback > Difference between competition date & release date
2003-06-14 22:31
TDJ

Registered: Dec 2001
Posts: 1879
Difference between competition date & release date

What if a demo competed at event A and was released later, maybe even on event B? That's what happened to Visual Delight (competed at Silicon party early july 1991 and released at the August Venlo meeting a month later).

Right now there seems to be no way of entering that information. In order for the result to show up I need to enter the Silicon party as the 'released at' value, but I can however set the Venlo date as the release date. Which can only cause confusion.

Maybe an extra field 'competed at' linked to the result field would be a solution?
2003-06-14 22:57
Perff
Administrator

Posts: 1679
In my world a demo which competes in a compo is also released the moment it is turned in. (or when the compo is over)

If you release it later it is not the same release (demo or whatever) imho.
If any changed are made to the demo it's no longer the same demo but an improved version, and if nothing is changed why delay the release date?
2003-06-15 00:22
TDJ

Registered: Dec 2001
Posts: 1879
And what if a demo was NOT released at the party but still competed there? Because that is what happened to both Visual Delight & Visual Delight 2: I took back the disks from the organizers so the compo-versions wouldn't be spread. Which they weren't. And I know lots of other demos that competed at a party were never released there. So if you link the release-date to the result, you've got a problem :)
2003-06-15 00:34
TDJ

Registered: Dec 2001
Posts: 1879
Hmm, reading your post once again, I understand your point: you feel that if a demo is changed it is basically a different release, and so the party result should not be linked to it. Which basically means that you just retconned Visual Delight into 2 seperate entities: the compo version which was never released but finished first place, and the improved version (with some added parts).

Sorry, but I don't like that at all, because you're basically deciding that Visual Delight, the version that is out there, did NOT win the party. Which it did. It is the same demo, although with changes to the compo version yes. But still the same demo. Now if the compo version had been released I could see your point, but not like this.

Now I can understand that you wouldn't want to add more fields to the database if it wasn't really necessary, but I don't think that that gives you the 'right' to determine that demos that are released after their competition date are not entitled to their result. There have been compo & final versions of demos since forever, and up until now I never heard of this rule.

To me it's real simple: I'll use the 'released at' field as a 'competed at' field and use the real release date, eventhough it may be different from the competition date. If that means your database is inconsistent, so be it.
2003-06-15 08:54
Perff
Administrator

Posts: 1679
Basically I still disagree, but.. :)

I think I could make a 'hack' that might solve this.
If the release date is outside the dates of the event which it is released/competet at I could make the text say 'Competed at'. Else it would say 'Released at' as it says now.

Idea?

.. But I still think that it would be two different "releases". Is this only me?
2003-06-15 09:12
TDJ

Registered: Dec 2001
Posts: 1879
Quote: Basically I still disagree, but.. :)

I think I could make a 'hack' that might solve this.
If the release date is outside the dates of the event which it is released/competet at I could make the text say 'Competed at'. Else it would say 'Released at' as it says now.

Idea?

.. But I still think that it would be two different "releases". Is this only me?


Not a bad solution, but still you'll get the problem that, if something is competing at event A and released at event B, this cannot be shown. Not a major issue but ..

I guess that having multiple versions per release, each with their own release-date/event etc. but a shared competition ranking would be too much trouble? :)
2003-06-15 09:31
Graham
Account closed

Registered: Dec 2002
Posts: 990
i agree with TDJ. the sense of knowing the release date is to know when a demo was around in the scene.

but i noticed other problems, what about demos which competed at more than one event? like for example that light demo...
2003-06-15 12:01
chatGPZ

Registered: Dec 2001
Posts: 11384
Bwaahh that lamah topic again. I agree 100% with Perff... competing at a compo for me means releasing aswell. improving later doesnt count, if you do so its a different release - end of story :)

however as for the database it would still be interisting to find out which groups/people cheated most in that respect :=)
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
Linus/MSL
Oxbow/Xenon
MCM/ONSLAUGHT
JonEgg
Alta
Wayne Kerr/Flashtro
LordNikon/Dekadence
Northwind
Retroluzzer/Quantum
Scrapper
pcollins/Quantum
astaroth/TRSI
Guests online: 88
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Mojo  (9.6)
4 Coma Light 13  (9.6)
5 Edge of Disgrace  (9.6)
6 What Is The Matrix 2  (9.6)
7 The Demo Coder  (9.6)
8 Uncensored  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (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 No Listen  (9.6)
6 Rainbow Connection  (9.5)
7 Dawnfall V1.1  (9.5)
8 Onscreen 5k  (9.5)
9 Morph  (9.5)
10 Libertongo  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Triad  (9.3)
5 Censor Design  (9.3)
Top Webmasters
1 Slaygon  (9.6)
2 Perff  (9.6)
3 Sabbi  (9.5)
4 Morpheus  (9.4)
5 CreaMD  (9.1)

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