| |
abaddon
Account closed
Registered: Apr 2002
Posts: 28 |
Release id #154278 : Sloppy Seconds
Last night, after I realized I had uploaded a faulty version of the tune, I tried to delete the entry and then create another entry which would include the correct tune. Much to my dismay the entry had been supposedly locked by the mods of CSDb.
The result is I can't replace the broken files since I don't have edit rights, I can only paste a link to working version in the comments section.
So lend me a hand here, I don't want to upload crap which has broken links and the only place you can get a decent one is from a google drive link |
|
| |
Zyron
Registered: Jan 2002
Posts: 2381 |
Once something is released, and uploaded here, it can't be "unreleased". You should create a new entry for the fixed version. |
| |
abaddon
Account closed
Registered: Apr 2002
Posts: 28 |
Right. |
| |
abaddon
Account closed
Registered: Apr 2002
Posts: 28 |
I created a new entry with the fixed tune. But really, for the sake of keeping the database clean, the broken version should be removed.
But whatever, it's just another crappy tune out there. |
| |
Smasher
Registered: Feb 2003
Posts: 519 |
IMHO that rule should be adjusted.
we should discern the following cases:
if a group releases a crack of a game, a few hours later a csdb user comments "hey, level 15 crashes! you lamers!", then the same group releases the 100% version to satisfy their fans; well it perfectly makes sense to create a new entry and keep the old one for historical reasons (or "eternal shame"... :) ).
but: (this case) if a scener creates an entry, uploads his own stuff, he then sees he uploaded a buggy version because in his build he forgot to comment out a lame "jsr crappybuggydontuseroutine" before compile and he has the full working version of his prg ready; well... in some circumstances, like:
- the scener provides a valid reason why his previous upload should be void
- he gives that reason within 2 hours
- he uploads the working version
- the new version cannot be void again for any reasons ("errare humanvm est, perseverare autem diabolicvm")
then the "cannot unrelease", "must create new entry" rules could be overruled and the world can live without that unworking program. |
| |
Zyron
Registered: Jan 2002
Posts: 2381 |
It's not a CSDb "rule" per se though, it's simply how archiving works. It just gets a bit more "in your face" when you use CSDb as your main platform to spread stuff, than when old bugged releases spread on disks get added here. |
| |
Smasher
Registered: Feb 2003
Posts: 519 |
hi mighty Z. exactly: it gets on your face, and you deserve that punishment when you upload your buggy release you thought it was 100%, so you'll do your homework better next time. but the systems punishes you even when you upload the wrong file... "mmmh, damn! that wasn't the final, wrong usb stick inserted...".
you should at least add a disclaimer: "upload your stuff only when you are perfectly sober - if you are drunk go visit youporn, not csdb". :) |
| |
Scan
Registered: Dec 2015
Posts: 111 |
@ZeSmasher: That's the best advice ever. :) |
| |
Zyron
Registered: Jan 2002
Posts: 2381 |
As if anyone, even when sober and in a perfect mental state, ever read disclaimers. ;) |
| |
Smasher
Registered: Feb 2003
Posts: 519 |
come on... this problem is easy to solve: the upload button gets active only when you accept the disclaimer. to accept the disclaimer there's one of those captcha thingie...
d0h! I fail to pass any captcha check even when I'm at 100%, so it will be perfect! :) |
| |
chatGPZ
Registered: Dec 2001
Posts: 11354 |
"upload your stuff only when you are perfectly sober - if you are drunk go visit youporn, not csdb".
boooooooring |
... 3 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 - Next |
