the things i'm thinking about right now are good ranges for strings and ability ID's.
advice on ID ranges to reduce mod incompatability
Débuté par
gordonbrown82
, mai 14 2010 07:59
#1
Posté 14 mai 2010 - 07:59
#2
Posté 15 mai 2010 - 01:36
#3
Posté 15 mai 2010 - 06:09
#4
Posté 18 mai 2010 - 09:45
According to the ABI_base page under the tooltipstrref column, anything over 500000 is considered a debuff. This would limit the range a fair amount.
0 - 200262 Bioware - Main campaign
0 - 1000000 Bioware - reserved
37000-38000 Baldur's Gate Redux
30000000-40000000 MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
5680000 - 5680050 Phaenan's The Winter Forge
2560000 - 2560500 Timelord's Blood and Lyrium
MCC obviously must narrow it down significantly. also it says that anything over 500000 is considered a debuff but since bioware has reserved a range that encompasses that number and several people have id's that is higher i don't understand what it means. i'm thinking of taking 2561000-2562000 tentatively so i'm unsure if that's ok.
0 - 200262 Bioware - Main campaign
0 - 1000000 Bioware - reserved
37000-38000 Baldur's Gate Redux
30000000-40000000 MCC's Senderfall: The Last Bastion (To author: unreasonable range, please correct)
5680000 - 5680050 Phaenan's The Winter Forge
2560000 - 2560500 Timelord's Blood and Lyrium
MCC obviously must narrow it down significantly. also it says that anything over 500000 is considered a debuff but since bioware has reserved a range that encompasses that number and several people have id's that is higher i don't understand what it means. i'm thinking of taking 2561000-2562000 tentatively so i'm unsure if that's ok.
Modifié par gordonbrown82, 18 mai 2010 - 09:46 .
#5
Posté 05 novembre 2010 - 07:44
Are those 2da ranges of the wiki page updated? How can I pick a few numbers? And what about the ID string ranges? I see there is a Community Contest list with numbers reserved is there another list somewhere from moders?
Thanks
Thanks
#6
Posté 05 novembre 2010 - 08:00
@gordonbrown82 - the debuff thing is because that's how it's been coded into one of the core include files, I think. I remember checking this a long time back but this really has no impact for a stand-alone module since you can write your own core script to replace that.
@alschemid, the Community Contest reserved those ranges so that the builders will stick to that and can import VO without having to renumber the VO files. Given the huge range of the string IDs, it is unlikely that a conflict will occur. However, feel free to open a new section for String IDs in the reservation page - I am sure modders will enter the ranges they are using.
@alschemid, the Community Contest reserved those ranges so that the builders will stick to that and can import VO without having to renumber the VO files. Given the huge range of the string IDs, it is unlikely that a conflict will occur. However, feel free to open a new section for String IDs in the reservation page - I am sure modders will enter the ranges they are using.
#7
Posté 05 novembre 2010 - 09:37
I created a String ID in the wiki, now in the toolset I see:
Bioware 0 - 10 Mil
Certified 10 Mil - 610 Mil
Default 610+ Mil
Can we use the range between 10 Mil to 610 Mil or only the 610+ Mil?
Bioware 0 - 10 Mil
Certified 10 Mil - 610 Mil
Default 610+ Mil
Can we use the range between 10 Mil to 610 Mil or only the 610+ Mil?
#8
Posté 06 novembre 2010 - 08:16
IIRC the Certified range was reserved by Bioware just in case they decide to commission or adopt some third party campaigns one day.
So, I wouldn't use it.
There's no danger of that if you accept the default string range generated by the toolset when a module is created.
I added a comment to your wiki entry, because AFAIK we don't need string id ranges to be registered under normal circumstances.
2DA lines are a different matter - we do encourage everyone to register those. You'll see from the wiki history that there's been plenty of activity.
So, I wouldn't use it.
There's no danger of that if you accept the default string range generated by the toolset when a module is created.
I added a comment to your wiki entry, because AFAIK we don't need string id ranges to be registered under normal circumstances.
2DA lines are a different matter - we do encourage everyone to register those. You'll see from the wiki history that there's been plenty of activity.
#9
Posté 06 novembre 2010 - 10:37
Thank you Proleric1.
My problem is that I was expanding one single player's dialogue file and got the main campaing strings ID... now I need to rename all the VOs, change the string id lines and face fx files, hope it is something easy to do.
My problem is that I was expanding one single player's dialogue file and got the main campaing strings ID... now I need to rename all the VOs, change the string id lines and face fx files, hope it is something easy to do.
Modifié par alschemid, 06 novembre 2010 - 10:47 .
#10
Posté 06 novembre 2010 - 01:04
Nothing wrong in using the default ID lines. Just write them down in the wiki.
Another thing I do, for the 2DA especifically, is to use the same IDs as the default lines assigned to me by the toolset. Saves me a lot of headaches. ;-)
Another thing I do, for the 2DA especifically, is to use the same IDs as the default lines assigned to me by the toolset. Saves me a lot of headaches. ;-)





Retour en haut







