| |
jailbird
Registered: Dec 2001
Posts: 1578 |
Updating releases after initial upload
OK, maybe a one pixel change doesn't grants a new entry, but lately I've seen people updating their releases after fixing bugs and stuff, then deleting the old download link and adding a new one. So, up to that point, 2-3 different versions of the same release exists somewhere.
If f.e. a data file is revised to an executable, an update is logical and even a must, but in these particular cases the authors are changing the actual visual characteristics of their work:
CSDb Logo
Weightless Fish Floating over a Worm Infested Desert
Following the same logic, I could go back to my old stuff, change a pixel here and there, refurbish them to modern standards, silently update them, and no one would notice except for those who're really familiar with my works.
PBY & FatFrost, it's really nothing personal, I'm just wondering where's the line where we'd have to open a new entry for an updated release? |
|
... 20 posts hidden. Click here to view all posts....
|
| |
soci
Registered: Sep 2003
Posts: 479 |
Submitted by MacGyver on 19 March 2014
Soci: Thanks! But again: New version - new CSDb release entry!
Ok, maybe next time I'll not forget this.
I have no problem with creating a new release in general. However it would be good to have "clone release" function which copies most of the constant release data like type, released by, credits, website, etc. which is otherwise a pain to re-enter. Then I would be less inclined to just add a new download instead. As a bonus the relationship between releases could be stored like older/newer versions. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
Quote:What about the cracks of new(er) games which are not welcome/featured here for whatever reason?
it has been tolerated to not have the files linked IF (and only if) they are publicly (!) available elsewhere, meaning one of the FTP sites listed in the rules. also in almost all of these cases, it was the cracking group itself who didnt provide a file - technically anyone who got the file could upload it to the entry in order to complete it.
and yes, this rule must be changed somehow, since TDD is no more accepting cracks, and none of the cracking groups managed and/or bothers to get a proper FTP online. |
| |
spider-j
Registered: Oct 2004
Posts: 498 |
Quoting Groepaztechnically anyone who got the file could upload it to the entry in order to complete it.
I don't think this works with locked entries.
Quote:and yes, this rule must be changed somehow, since TDD is no more accepting cracks, and none of the cracking groups managed and/or bothers to get a proper FTP online.
Since CSDb allows adding "not public" downloads, I'd appreciate if this option would be used instead of not uploading at all. |
| |
Romppainen
Account closed
Registered: Apr 2008
Posts: 40 |
Quoting spider-jSince CSDb allows adding "not public" downloads, I'd appreciate if this option would be used instead of not uploading at all.
+1, at least until proper FTP site is available again. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11359 |
Quote:I don't think this works with locked entries.
if an incomplete entry is locked, contact one of the trusted users or a moderator. incomplete entries shouldnt be locked in the first place :) (imho this locking bullshit should be removed completely, now that we have proper logging)
Quote:Since CSDb allows adding "not public" downloads, I'd appreciate if this option would be used instead of not uploading at all.
indeed - that was the intend more or less. (personally i dont see a reason for why not ALL downloads should be like that, but thats another thing) |
| Previous - 1 | 2 | 3 - Next |
