| |
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. =) |
|
... 34 posts hidden. Click here to view all posts....
|
| |
Jazzcat
Registered: Feb 2002
Posts: 1045 |
Quote: Quote:Most important is a FIRST RELEASE flag.
i wonder how many more suggestion before anyone reads the fucking textfile :=)
and yes, bepp got it right again :)
Like I give a fuck, just drive it to completion and get the shit implemented. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11390 |
Quote:Like I give a fuck
so why are you posting here then? |
| |
Jazzcat
Registered: Feb 2002
Posts: 1045 |
Quote: Quote:Like I give a fuck
so why are you posting here then?
Less blabla, get it implemented. Thanks. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11390 |
flags actually ARE implemented already, perff just has to fix a few more details before it can go live |
| |
Jazzcat
Registered: Feb 2002
Posts: 1045 |
Looking forward to it. |
| |
Moloch
Registered: Jan 2002
Posts: 2929 |
Quoting beppAnd in that sense, all added trainers and imports are re-cracks, yes. But if the re-crack flag is intended for something else then the concept might need to be revised.
Then a different term needs to be added because re-crack, as you know, does mean something lame database or not. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11390 |
yes, and "cracking", as you know, refers to removing copyprotections... |
| |
bepp
Registered: Jun 2010
Posts: 265 |
Since import have its own flag, they need not worry about being classified as re-cracks. I believe it's really only "lame re-cracks" and added trainers that fall into the re-crack category.
And the definition (referenced Groepaz file) of a re-crack is " not a genuine crack". I'd have to bend myself to tick this flag for a version with added trainers. At least if that's the definition..
Can this be made more clear in any way? |
| |
chatGPZ
Registered: Dec 2001
Posts: 11390 |
maybe "genuine" is not the right word. its supposed to be a generic definition along the lines of how "crack" was defined. so if a crack is "an unauthorized modification of someones game", a recrack is "an unauthorized modification of someones crack". |
| |
Jazzcat
Registered: Feb 2002
Posts: 1045 |
Then you have "Re-Release" flag also, equally as lame. |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
