22 replies to this topic

[SConrad]

What I said was that it was a good idea to have "ar" in the name somewhere, if for no other reason than keeping track of the things if for whatever reason you can't see the extension clearly. It doesn't necessarily have to be at the beginning.

Ah, okay, I misread, then.

And disagree, but that's another matter.

[Sir BillyBob]

Nope, no AR in any of the mods I have worked on except the NTotSC for BGT project. And that was only because the original version already used unique naming, i.e. AR10PB.ARE, AR53PB.ARE, etc. Otherwise, the areas are always based on the mod in question, BH for BoneHill, DSC for DSotSC, and TC for CA (total conversion). If I don't use AR, I know that it is an area from my mod, and second I know I have less (but not complete) chance of someone else using that area name.

But since none of these mods are for SoA itself (BG1 or my TC project), I don't expect much need of someone changing the SoA/ToB areas to also change the BG1 areas.

[Azkyroth]

Nope, no AR in any of the mods I have worked on except the NTotSC for BGT project. And that was only because the original version already used unique naming, i.e. AR10PB.ARE, AR53PB.ARE, etc. Otherwise, the areas are always based on the mod in question, BH for BoneHill, DSC for DSotSC, and TC for CA (total conversion). If I don't use AR, I know that it is an area from my mod, and second I know I have less (but not complete) chance of someone else using that area name.

That's more or less what I'm doing, with the A2Kar### format. There are only 28 new area files that go with Arkalian, so the number use isn't too restrictive...