3 réponses à ce sujet

[FollowTheGourd]

Hi,

I was thinking that for resources that would belong to a standalone module that a single underscore might be good enough, somewhat like implicitly registering a prefix on the wiki here. E.g., using xyz as a prefix, instead of xyz_orz110ar_hall_of_heroes or xyz110ar_hall_of_heroes, it would just be _orz110ar_hall_of_heroes.

My understanding is that there shouldn't be a resource name conflict as long as it's not a core resource or running at the same time another module is, as would be the case for two or more standalone modules. Edit: as TimelordDC pointed out, I mean in-game, for compatibility between different mod authors.

I'm just running this by the forum to see if there's anything obvious I overlooked, but I've been bumping into the 27 character limit by using a longer prefix where I could have used a little more space and this seems like a natural fit. I suppose it's reliant on somebody not using it outside of these restrictions, but then they'd still have to create the same resource name for a conflict.

Modifié par FollowTheGourd, 25 août 2010 - 12:39 .

[TimelordDC]

A resource name cannot be duplicated across add-ins currently.

Edit: I see you are mentioning conflict in terms of the game engine and not the toolset. That might work but I am not sure.

Modifié par TimelordDC, 25 août 2010 - 12:37 .

[FollowTheGourd]

That raises a valid point though - it'd make B2B imports potentially more problematic, but I haven't really had to deal with those and they seem to cause problems anyway from what I've read.

Modifié par FollowTheGourd, 25 août 2010 - 01:20 .

[Proleric]

The three digit prefix xxx_ was proposed because the risk of another builder using it accidentally is low.

Bear in mind that if a player has core add-ins or package overrides, our standalone campaigns will be impacted.

Obviously, some builders don't know about compatibility, others don't care. Sadly, there are some unhelpful tutorials out there, too.

Also, as TimelordDC mentioned, the toolset doesn't allow duplicate resource names. So, if you ever decide to make more than one module, it's convenient to use a different prefix.

We're using builder-to-builder successfully now, but I guess there could be issues if you wanted to import content from one standalone campaign to another unless the resource prefixes were different.

Of course, you might decide that these risks are acceptable.

Modifié par Proleric1, 25 août 2010 - 09:22 .