Log inRegister an accountBrowse CSDbHelp & documentationFacts & StatisticsThe forumsAvailable RSS-feeds on CSDbSupport CSDb Commodore 64 Scene Database
 Welcome to our latest new user danikAdmiral ! (Registered 2024-12-17) You are not logged in - nap
CSDb User Forums


Forums > CSDb Feedback > Tags for fixing...
2006-03-30 11:39
Zyron

Registered: Jan 2002
Posts: 2381
Tags for fixing...

Maybe we should decided on some standard how to tag fixed cracks to make them easier to find in a search & to get some consistancy in the database.
I think I've seen the following variations this far:

1) [pal/ntsc]
2) [Pal/Ntsc]
3) [PAL/NTSC]
4) [ntsc/pal]
5) [Ntsc/Pal]
6) [NTSC/PAL]
7) [Fix]
8) [FX]

I personally use & prefer #1

What are your views on this?
2006-03-30 11:44
cba

Registered: Apr 2002
Posts: 935
Quote: Maybe we should decided on some standard how to tag fixed cracks to make them easier to find in a search & to get some consistancy in the database.
I think I've seen the following variations this far:

1) [pal/ntsc]
2) [Pal/Ntsc]
3) [PAL/NTSC]
4) [ntsc/pal]
5) [Ntsc/Pal]
6) [NTSC/PAL]
7) [Fix]
8) [FX]

I personally use & prefer #1

What are your views on this?


I've listed all the cracks that I've added here
with the first one.

[pal/ntsc]

I would prefer to use that one.

Niels
2006-03-30 11:46
Moloch

Registered: Jan 2002
Posts: 2928
I'll be using [NTSC/PAL] as it was used on the boards.
2006-03-30 11:46
Burglar

Registered: Dec 2004
Posts: 1098
some firstreleases that didnt require any fix, were labelled pal/ntsc in the past.

so I would say use 7 [fix] if it actually contains a fix, and [pal/ntsc] for those that already run fine on both.
2006-03-30 11:51
cba

Registered: Apr 2002
Posts: 935
Quote: some firstreleases that didnt require any fix, were labelled pal/ntsc in the past.

so I would say use 7 [fix] if it actually contains a fix, and [pal/ntsc] for those that already run fine on both.


I wonder what's going to be the standard :)

2006-03-30 11:54
Moloch

Registered: Jan 2002
Posts: 2928
also don't forget

NP

If we must come to some standard it's probably best to use FIX or FX. I don't ever remember seeing pal/ntsc but 99% of the time ntsc/pal.
2006-03-30 12:06
cba

Registered: Apr 2002
Posts: 935
Quote: also don't forget

NP

If we must come to some standard it's probably best to use FIX or FX. I don't ever remember seeing pal/ntsc but 99% of the time ntsc/pal.


At The Digital Dungeon I am using FIX

2006-03-30 12:13
Mason

Registered: Dec 2001
Posts: 461
I dont mention them as something special in c64heaven archive. I mean if its from Armageddon then people its pal/ntsc.
2006-03-30 12:14
Moloch

Registered: Jan 2002
Posts: 2928
Quote: I dont mention them as something special in c64heaven archive. I mean if its from Armageddon then people its pal/ntsc.


Only problem there is importing groups didn't fix releases in the early years.

What a mess. ;)
2006-03-30 13:35
TDJ

Registered: Dec 2001
Posts: 1879
Why not just delete all cracks from this database and get it over with? :)
2006-03-30 14:49
wreg
Account closed

Registered: Mar 2004
Posts: 679
pls stop discussing this useless shit ...

just let perff add some boolean-tags to the release-data on which you can select if its NTSC and/or PAL
maybe be need 'working on' and 'fixed for' and then NTSC and/or PAL

anyway this should be regulated by the administration
and not some ppl deciding which string would fit better/personal likes and dislikes are misplaced here :)

if its necessary for you to see NTSCPAL in the results when searching i'm sure perff will do this as well :)
2006-03-30 14:50
Compyx

Registered: Jan 2005
Posts: 631
Quote: Why not just delete all cracks from this database and get it over with? :)

Well spoken :)
2006-03-30 16:18
Tch
Account closed

Registered: Sep 2004
Posts: 512
Quote: Well spoken :)

Wouldn´t that make this C64.CH? ;)

Anyway,I like option 1 best,but I´m sure I´ve used option 3 aswell.
2006-04-01 07:53
Zyron

Registered: Jan 2002
Posts: 2381
Just saw another one: [pal&ntsc]

Maybe we should all have different ways of tagging the releases to make it really messy & ugly, I'll use {P4l+N75<}
2006-04-01 13:25
Slator

Registered: Jan 2002
Posts: 274
Quote: Just saw another one: [pal&ntsc]

Maybe we should all have different ways of tagging the releases to make it really messy & ugly, I'll use {P4l+N75<}


well it got a bit late while adding and I must have been very sleepy, changed it to the style I prefer ;-D so no more [pal&ntsc] and hey, I didn't see this post before.

forgive my zyron ;-D
2006-04-01 16:58
Zyron

Registered: Jan 2002
Posts: 2381
Go go Slator! :)
2006-06-11 20:55
Grim Reaper
Account closed

Registered: Aug 2005
Posts: 21
Complications....
"fix" USA term, meaning euro game was ntsc-fixed
"pal-fix", meaning USA game was pal-fixed

geeze was so easy then, no wonder i wouldn't align myself during the Amiga daze.
2006-06-11 20:56
Grim Reaper
Account closed

Registered: Aug 2005
Posts: 21
Complications....
"fix" USA term, meaning euro game was ntsc-fixed
"pal-fix", meaning USA game was pal-fixed

geeze was so easy then, no wonder i wouldn't align myself during the Amiga daze.
2006-06-11 21:50
Rough
Account closed

Registered: Feb 2002
Posts: 1829
Dont forget the games from Canada.

8)
2006-06-12 03:27
Jazzcat

Registered: Feb 2002
Posts: 1044
Hmmm I find it more neat to do it like in the old days.
F = fix

(if it was bug-fixed or pal-fixed or something needing ellaboration, that should be done in the comments field anyway).

While we're at it:

D = Docs
E = Editor Included
F = Fix
H = Hi-score Saver installed
I = IDE64 fixed
R = REU support
T = Translation
100% = When no other cracked version works, if your fixing someone else's crack or fixing an error in your own release
101% = If the first fix still has flaws, this can continue. I recall even seeing 102% and 103% versions before it was finally done right.

Gamename- = Gamename Preview

Over the years things have changed a little, # has been docs but it is also picture file in the directory. M has symbolised mega version but also means trainers that can be used ingame.

I prefer the above system, which has been used for years now, as it looks simple and neat.

http://c64.rulez.org/onslaught/1987_int_release_standards.jpg
2006-06-12 09:29
Moloch

Registered: Jan 2002
Posts: 2928
"fix" or "fx" was the standard "years ago"...
2006-06-12 10:01
Jazzcat

Registered: Feb 2002
Posts: 1044
Yep. It sure was. Along with some things that we still use and other things we no longer use. I guess F is packed better than FIX or FX.

These days we have better packers. ;)
2006-06-12 19:58
Tch
Account closed

Registered: Sep 2004
Posts: 512
D for docs?

Sorry but I won´t use that.
It has close to always been # for me and I think everybody knows what it means.
Pictures have been ´arrow up´ or % or (..),quite a mess.

Oh,when I see an `I´,IFFL comes to mind.
Why is there not something short for that? ;)
2006-06-13 10:21
Jazzcat

Registered: Feb 2002
Posts: 1044
Heheh IFFL in itself is an acronym, so abbreviating an acronym from say IFFL to I would suck ;)

2009-01-04 14:10
The Shadow

Registered: Oct 2007
Posts: 304
His this been standardized yet? There should be rules added to the Cracking Standards. Added features to a crack should have universal symbols.

Proposed additions:

B = bugfix
O = a crack that has been crunched to one disk side
C = a preview that has been completed

As it used to be in the old scene, only if a game was actually fixed and contains a $02A6 subroutine with a template (Compatible with both NTSC and Pal systems), was it referred to as (NTSC/Pal)
Logically though, if it started out as a Pal game and was NTSC fixed, it would be (Pal/NTSC)
Visa versa if a game was originally programmed on an NTSC machine and Pal fixed it would be (NTSC/Pal)

2009-01-04 14:22
Oswald

Registered: Apr 2002
Posts: 5094
or just implement tags for csdb :)
2013-04-08 17:39
Luca

Registered: Apr 2002
Posts:
Sorry for resurrecting this old thread, just some quick questions about:

- which standard for docs/instructions, "#" or D? I saw both are regularly used, and don't see an actual difference;
- F is for PAL<->NTSC exclusively, or does it also mean a generic bugfix tho? Does somebody really use B for bugfix?
- PAL<->NTSC is a must-do for any decent crack nowadays; I've ever thought not all the stuff running on PAL would work on NTSC too, because of the NTSC's lack in global rastertime, so what if a PAL program uses almost all the machine time?

Thank you in advance.
2013-04-08 19:02
Fungus

Registered: Sep 2002
Posts: 686
Old way for docs is #
New way for docs is D

F , FX, or FIX is for NTSC fix

a real fix has the game working on both ntsc and pal as close as possible. The only things which cannot be fixed 100% are sprites in the borders, which are often moved from the bottom to the top for ntsc machines.

many times a great deal of effort is put into recoding routines in pal games to make them work on ntsc. Thankfully pal coders in the past (NOT NOW) were pretty lazy with optimization, so it's usually not too much work.
2013-04-08 19:17
Luca

Registered: Apr 2002
Posts:
Thanks Fungus. So a fixed game should be tagged 101%, does it?
2013-04-08 20:15
chatGPZ

Registered: Dec 2001
Posts: 11384
no, 101% means that the original game contained bugs, which are fixed in the release. its not related to pal/ntsc fixing.

that said, perff is (hopefully) working on adding all kind of stuff to the crack entries atm, i recommend not to waste time on putting more meta info into release names.
2013-04-08 20:29
Skate

Registered: Jul 2003
Posts: 494
Quote:
i recommend not to waste time on putting more meta info into release names


i second that. it's 2013, relational databases are history and we still have missing fields in CSDB database. :)
2013-04-08 20:44
Luca

Registered: Apr 2002
Posts:
Quote: no, 101% means that the original game contained bugs, which are fixed in the release. its not related to pal/ntsc fixing.

that said, perff is (hopefully) working on adding all kind of stuff to the crack entries atm, i recommend not to waste time on putting more meta info into release names.


Exactly, I was referring to my original question about bugfixes, now that's definitely clear :)
2013-04-09 06:42
Fungus

Registered: Sep 2002
Posts: 686
101% or more can also mean added features, like 2 player mode in a 1 player game, high scores entry in a game which didn't have one, etc.
2013-04-09 10:40
Didi

Registered: Nov 2011
Posts: 487
Just repeating the tags I spotted to be used here.

D = Docs
E = Translation to english
F = NTSC or PAL Fix followed by [pal/ntsc] or [ntsc/pal] at the end, original format first
G = Additional graphics (like converted coverpic)
H = Highscore-Saver installed
I = IDE64 fixed
J = Joystick control added (if not present in original)
M = Modifications like additional keys, etc.
P = Passwords added
Pic = Original Pic included
R = REU support
T = Translation
100% = Bugfix of a bugged crack, your own or other's
101% or higher = Bugs fixed that were in the original
[language] = other language than english, e.g. [german] if the release is in german

I agree, proper checkboxes would be better.
2013-04-09 18:50
Luca

Registered: Apr 2002
Posts:
Quite fulfilling, thank you all.
RefreshSubscribe to this thread:

You need to be logged in to post in the forum.

Search the forum:
Search   for   in  
All times are CET.
Search CSDb
Advanced
Users Online
chesser/Blazon
Airwolf/F4CG
t0m3000/hf^boom!^ibx
ΛΛdZ
psych
AMB/Level 64
MWR/Visdom
pcollins/Quantum
Archmage/SHAPE
Guests online: 91
Top Demos
1 Next Level  (9.7)
2 13:37  (9.7)
3 Mojo  (9.6)
4 Coma Light 13  (9.6)
5 Edge of Disgrace  (9.6)
6 What Is The Matrix 2  (9.6)
7 The Demo Coder  (9.6)
8 Uncensored  (9.6)
9 Comaland 100%  (9.6)
10 Wonderland XIV  (9.6)
Top onefile Demos
1 Layers  (9.6)
2 Party Elk 2  (9.6)
3 Cubic Dream  (9.6)
4 Copper Booze  (9.6)
5 No Listen  (9.6)
6 Rainbow Connection  (9.5)
7 Dawnfall V1.1  (9.5)
8 Onscreen 5k  (9.5)
9 Morph  (9.5)
10 Libertongo  (9.5)
Top Groups
1 Performers  (9.3)
2 Booze Design  (9.3)
3 Oxyron  (9.3)
4 Triad  (9.3)
5 Censor Design  (9.3)
Top Crackers
1 Mr. Z  (9.9)
2 Antitrack  (9.8)
3 OTD  (9.8)
4 Fungus  (9.8)
5 S!R  (9.8)

Home - Disclaimer
Copyright © No Name 2001-2024
Page generated in: 0.083 sec.