| |
bepp
Registered: Jun 2010
Posts: 265 |
Suggestion: New release type "C64 Import"
Rough started a discussion a couple of years ago (see Adding the cracker group to import/trainer version), pin pointing a problem where a crack may be credited repeatedly for a group - due to the many imports that may exist.
Some attempts have been made to differentiate cracks from import by suffixing the entry with "[import]" - an approach that might not be appealing to all.
Discussions suggest that original crack group (pun intended) be credited only on *their* release, while imports only be credited to importing group, leaving a link to the original release.
My biggest concern is to be able to (quickly) identify and differentiate cracks from import, when checking for existence of a certain release for example. Although this can be partly solved by suffixing the name, I'm not sure it's the right approach. Cleaning up the credits list would partly solve the problem, but I still wouldn't be able to clearly see a difference between crack and import.
So I'm suggesting that we add a new release type. Let's call it "C64 Crack Import" or just "C64 Import" for short. It would be a fairly easy task to just "re-categorize" any imports stumbled upon, and to some extent it could probably be batch-made with an SQL query (Perff?).
It is often talked about that the DB is not designed to handle certain new features (tags for instance), while adding a new release type would make no harm to performance. Also, from a DB design perspective, it would make more sense since you can then do filtered searches where imports and cracks are differentiated. Also in release lists, it would be possible to see the difference.
...
Having import as a release type, it would furthermore be possible to have an option in listings to "Hide imports"... the result of which of course would depend on the quality of the entries, but it *would* be possible. Think future. =) |
|
... 40 posts hidden. Click here to view all posts....
|
| |
Didi
Registered: Nov 2011
Posts: 488 |
I don't remember if this has been discussed before, but how about implementing some kind of "release chain" feature for cracks in case a release was touched by several groups.
Game +x [pal/ntsc]
Release chain: Game (crack) by GroupA > Game (trainer) by GroupB
The current release needs to have a link to the release it's based on then.
Simpler might be just to add a "based on" link which may just direct to the release it was directly made of. It may direct to a previous crack or even a C64 Game entry if it is present on CSDb. Sometimes also Tools or Demos get fixed or developed further, so this may enable you to click through to previous versions.
Such entry may look like:
Current Release title
(Based on: <Backlink to base-release> by XYZ) |
| |
Didi
Registered: Nov 2011
Posts: 488 |
Quote:Also: Removing the original cracker's intro wasn't always done to hide the crack's origin but for size reasons. Sometimes the intro was also removed because it was incompatible to NTSC (or even PAL). There are several releases where I'd wish they had removed the intro because it's just bugging around.
It was mainly Euro-groups which removed the intros of the NTSC crackers while NTSC importers mostly just additionally linked their intro. This is interesting because NTSC compatibility of PAL code appears much more often than vice versa. |
| |
bepp
Registered: Jun 2010
Posts: 265 |
There will be a field to enter the id of the original crack (in case of re-crack or import). See http://hitmen.c02.at/temp/cracktags-draft.txt. |
| |
Didi
Registered: Nov 2011
Posts: 488 |
Might appear on Demos/Collections as well because e.g. Style fixed several of them.
Really looking forward to the changes to go live. |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
