In the old claim system, when creating a claim, certain fields were filled out, and the claim name was generated based on those fields:
TR_i4-517-Hla
TR - assigned by default
i - assigned depending on where you create the claim; if the claim is created in Interiors: Unclaimed it is automatically assigned the 'i'
4 - assigned depending on the Group Map
517 - assigned automatically based on the above information; the 517th interior of Map 4
Hla - assigned faction
The new system no longer generates names automatically; instead, claim names need to be entered manually. However, it doesn't need to generate names automatically. The fields are still there, and you can easily locate claims using filters. The old claims browser could do the same, I should mention, though the amount of fields you could filter by depended on the claim type. However, most developers did not have access to the claims browser for reasons unknown. (Though considering the mess the old browser was, that may have been an act of mercy on the part of the core).
So claim names do not need to contain all that information as long as they are unique and identifiable. Conversely, manually entering that information, specifically manually keeping track of the claim number, will I think prove really annoying as time goes on and we actually start to open up more claims.
Now in the interests of keeping the claims identifiable I do think we should still have a naming convention, I just think we should simplify it.
Argumentation (feel free to skip):
Conclusion:
Exterior Claim Designation: RegionDesignationClaimNumber
Interior Claim Designation: ExtClaimDesignation/Settlement Name #ClaimNumber( Additional Designation)
Quest Claim Designation: FactionDesignation(QuestlineDesignation)(QuestNumber) "Quest Name"
In the CS, the prefix TR_ should still be used so that our cells/quests can be more easily located, and plugins should also keep that prefex, naturally. This all doesn't affect stuff like item naming.
2015-07-05 20:55
4 years 1 month ago
Is there any way to get a automatic naming system implemented in the new system?
2014-03-16 17:45
2 years 4 weeks ago
I'd add "short" to that when it comes to object prefixes, for much-needed convenience when viewing lists (wrt older references, and when typing the first characters to get to something in the CS...)
Again because of objects the "q" letter should be kept too, at least (same would probably go for objects created for interior claims having "i"). Having done quite a lot of fixing on the Mainland file I can assure you this is very very necessary to understanding that an item is quest-specific or interior-specific, and for modders too - a quest name or just a faction and number wouldn't be nearly explicit enough.
2015-08-10 20:50
4 days 21 hours ago
Ah, you misunderstand, I'm only talking about claim names here, not object IDs. The situation hasn't changed for object IDs; they do need to convey a lot of information as the CS doesn't really have an accessible filtering feature with which one can locate objects.
2014-03-16 17:45
2 years 4 weeks ago
Right – wanted to mind that object names derive directly from claim names, transition which probably needs to be preserved,
2015-08-10 20:50
4 days 21 hours ago
Hm. The most objectionable part of the current claim names (and therefore CS IDs) is the claim number, due to how tedious it will be to keep count. Now as I say for claims I think the rest is superfluous as well and that it’s probably better to go with a somewhat looser naming convention, but for CS IDs not so much. For items, I think the claim number could just be replaced by an abbreviated designation:
Vhul-11B – example for settlement interior
RR5-7 – example for ‘wilderness’ interior
RR5 – example for exterior
MiscBirdsofaFeather – example for misc quest; the name might need to be abbreviated
Hla20Sellout – example for faction questline quest
MiscOdy22Suitors – example for misc questline quest
The rest could stay the same.
Well, there is also the map designation; if we’re going with (roughly) the Imperial Districts as I think we should maps 1 through 6 should (finally) be replaced by D (Deshaan), M (Mournhold), N (Narsis), S (Solstheim, which we probably won’t use), T (Telvannis), V (Velothis) and W (Vvardenfell).
2014-03-16 17:45
2 years 4 weeks ago
I’d find a number easier to work with than a name or bunch of letters, but that might just be habit. I imagine CS IDs will keep using underscores between designations, TR_(map)_(i / q / e...) (_?) (claim ID)
2015-08-10 20:50
4 days 21 hours ago
Yeah filling out my above examples:
TR_M_iVhul-11B_Comb
TR_V_iRR5-7_Bugel
TR_V_eRR5_Alphorn
TR_D_qMiscBirdsofaFeather_Quill
TR_N_qHla20Sellout_LaundryBag – not sure if the map designation is really necessary for faction questlines.
TR_T_qMiscOdy22Suitors_OdyBow
I know what you mean about numbers, but I went with letters as they’re a bit less abstract; M=Mournhold seems a bit more intuitive than 3=Mournhold, and Vhul-11 seems a lot more intuitive than 790.
2015-08-10 20:50
4 days 21 hours ago
This was discussed in today’s Skype meeting. What we settled on:
Claim names:
Exterior claim: Roth-Roryn05
Wilderness interior claim: Roth-Roryn05-07
Settlement interior claim: Vhul-07
Claim split from a larger complex: Vhul-07B, Vhul-7Top or whatever else works for the given situation
Quest claim: Misc "Birds of a Feather"
Questline quest claim (if we handle these as individual claims): MiscOdyssey22 "Slaughter of the Suitors"
For exteriors, the claim number will be settled upon when the region is being prepared for exterior work. For interiors, the claim number will be based off of an exterior claim map or settlement map, as applies. For questlines, the number naturally signifies where in the questline the quest is.
Cell names:
Exterior cell: TR_Roth-Roryn05
Wilderness interior cell: TR_Roth-Roryn05-07
Settlement interior cell: TR_Vhul-07
Cell split from larger complex: TR_Vhul-07B, TR_Vhul-7Top or whatever else works for the given situation
We didn’t quite settle on the following:
Item names:
Item associated with exterior claim: TR_V_eRR05_Alphorn
Item associated with wilderness interior claim: TR_V_iRR05-07_Bugel
Item associated with settlement interior claim: TR_M_iVhul-11B_Comb
Item associated with quest claim: TR_T_qMiscOdy22Suitors_OdyBow
Item associated with questline quest claim: TR_D_qMiscBirdsofaFeather_Quill
It was commented that the IDs are rather ugly, and the possibility of doing away with claim-based item naming entirely was discussed. To that end, I’d like to hear the feedback from anyone who thinks items added by claims should have an ID to reflect that fat.
2015-12-12 23:47
3 years 4 months ago
If the items are unique and not expected to be used elsewhere, having a claim-bsaed name makes sense. If it’s an item that reasonably should be used elsewhere in different claims then it should either already be in TR_Data.esm or be given a more global, understandable name.
Does: concepts, textures, youtube vids, admin stuff e.g. PR, handbook, assets, small website things. Activity level: wildly unpredictable. Still active. Find me on Discord.
2015-08-10 20:50
4 days 21 hours ago
Yeah, this is only for claim-specific items. As far as more global naming conventions for items are concerned, I think that depends mostly on how the cross-project data files discussion pans out.
2016-10-09 23:10
1 day 19 hours ago
This is the new naming convention.
Our current naming convention for dungeon interiors is TR_[Exterior Claim Acronym]_[Type of Interior]_# For example, the claim "Lake Andaram 2 Tomb 1" would have the claim name TR_LA2_Tomb_1
- TR stands for Tamririel Rebuilt (you would use PC_ or Sky_ for claims in Cyrodiil or Skyrim)
- LA2 stands for Lake Andaram 2, the name of the exterior claim that has this tomb
- Tomb is the type of interior
- 1 is the number in the claim name (the number is dependent on the type)
For cities or some multi-claim dungeons the convention is TR_[City Name]_#_[Description] For example, the claim "Aimrah Interior Claim 2: Sailors' Inn" would be named TR_Aimrah_2_Sailors' Inn (spaces in the city name or interior description remain spaces)
If you have multiple interior cells in your claim, add "_[Description]" to each (optionally not to the main cell) These can be as barebones as TR_LA3_Grotto_1_Upper and TR_LA3_Grotto_1_Lower.
When an interior is merged into a section file, it will initially begin with TR_, but should be given a proper name after being NPCed.
2016-01-21 17:58
3 years 3 weeks ago
please stop using - (minus) math operator in identifiers, it may confuse scripting engine
use _ (underscore) instead.
2015-08-10 20:50
4 days 21 hours ago
Hm, that's unfortunate; visually binding ID elements with '-' and separating them with '_' works quite well. But shouldn't be too hard to change on our end moving forward as the above proposals use hyphens/minus sparingly as it is. (Changing existing IDs would be another matter).
For cells, though, that seems like a lost cause, or at any rate far more problematic.
2014-03-16 17:45
2 years 4 weeks ago
Is there any example of - confusing the MW engine? Every time this comes up it turns out to be an issue with openMW (fixed now) or with an external script compiler some people use for MWSE, so the province mods should keep using it consistently