[CSDb] - User Forums - Re-Crack definition

Welcome to our latest new user danikAdmiral ! (Registered 2024-12-17)

You are not logged in - nap

CSDb User Forums

Forums > CSDb Feedback > Re-Crack definition

2023-11-05 22:59

Didi

Registered: Nov 2011
Posts: 487

Re-Crack definition

From my understanding a re-crack is to claim something as own work which isn't yours and not crediting the original releaser(s) when adding stuff/features and/or removing their intros.
So adding trainers to trainerless cracks, adding PAL/NTSC fixes with crediting the original releaser and/or even leaving the intro infront isn't a re-crack by this definition. This also includes IDE fixes, adding drive independency (like Ghosts'n Goblins +5DH [any drive fix]) and stuff like this.

2023-11-05 23:14

TheRyk

Registered: Mar 2009
Posts: 2240

yeah... no... :D
What's an import?
Handling recracks, sids, etc

Bottom line: If releasing group/scener gives credits as clear as possible (best without intro-stripping) to original group/scener, we categorize it as "Import" here on CSDb (knowing that 'Importing' was sth completely different in the 80s and 90s, but as a database workaround it... uhmm... kinda works). For sure, there's still a bunch of releases left not following that logic yet.

2023-11-06 02:34

Fungus

Registered: Sep 2002
Posts: 686

It's a recrack.

Importing doesn't exist since the internet really.

Maybe the rules should be changed to reflect time period that things were released. When the internet became mainstream, releasing became different with 0day ftp instead of BBS.

It's kind of hard to have rules that span everything.

In regards to N0S releases, I think we would prefer to have bugs reported so we can fix them ourselves rather than having people take our hard work and slap an intro on it.

Refresh

Subscribe to this thread: