Project

General

Profile

Bug #2897

Editor: Rename "Original creature" field

Added by Who Knows about 2 years ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Editor
Target version:
Start date:
08/29/2015
% Done:

0%

Reproducibility:
Always
Operating system:
Other
Severity:
Normal

Description

TES3-CS names this "Sound gen creature" which is more precise. IMO, better would be "sound ID" or "creature sound ID"

./openmw-cs > new/load > MW.esm > objects > new entry > creature > "Original creature"

Let's say I clone a creature - a dreugh - because it's easier to achieve with the CS. But I want to make a minotaur, hence I change everything from name to how it looks like. Then I think that the alit sound would fit the minotaur, why would "alit" be the "original creature"? "alit" is a mp3/wav file in the filesystem. It's usually used for the alit creature, but it is not the alit "as whole".

The other way around: assumedly I create a new (not cloned) creature. How would I know that "Original creature" would be the field where I can set a sound for my creature?

History

#1 Updated by Marc Zinnschlag about 2 years ago

  • Category set to Editor
  • Target version set to openmw-0.37

#2 Updated by Who Knows about 2 years ago

I just thought about this again. "*sound ID*" is better than "creature sound ID". The latter is mistakeable as well. To correct that, the field heading would be "sound ID of creature".
Even then, maybe I want to use the sound a hammer makes for my creature. A hammer is no creature - so, succinct -

name it (just) "sound ID" please.

#3 Updated by Marc Zinnschlag about 2 years ago

  • Target version changed from openmw-0.37 to openmw-0.38

#4 Updated by Marc Zinnschlag almost 2 years ago

Sound ID is bad, because:

1. We generally don't include the term ID
2. It is not a sound ID. It is a creature ID.

Actually, "Create Sound ID" is also pretty bad for the same reason. I am open to changing the name of this column, but we need to find something better.

#5 Updated by Who Knows almost 2 years ago

Looking on that from a users perspective maybe "sound source" would be good. It would make sense in a way, but you still need to know that it refers to the creature that has the sound you want to have payed for your creature. If "sound source creature" isn't too long that might fit well.

#6 Updated by Who Knows almost 2 years ago

For the openmw-future it might be nice if you could give a sound file as value instead of a link to the creature that has that sound attached.

#7 Updated by Marc Zinnschlag almost 2 years ago

  • Target version changed from openmw-0.38 to openmw-0.39

#8 Updated by Marc Zinnschlag over 1 year ago

  • Target version changed from openmw-0.39 to openmw-0.40

#9 Updated by Marc Zinnschlag over 1 year ago

  • Target version changed from openmw-0.40 to openmw-cs-1.0

#10 Updated by Martin Otto 9 months ago

Who Knows wrote:

For the openmw-future it might be nice if you could give a sound file as value instead of a link to the creature that has that sound attached.

As I understand it, the reference to another "parent" creature is useful for modding. You don't want to change the creature sound for every derived creature.

Anyway, what about one of the following names:
- "Sounds like: " (quick and dirty)
- "Parent Creature" (may be misleading)
- "Creature Sound Parent"

#11 Updated by Who Knows 9 months ago

Martin Otto wrote:

Who Knows wrote:

For the openmw-future it might be nice if you could give a sound file as value instead of a link to the creature that has that sound attached.

As I understand it, the reference to another "parent" creature is useful for modding. You don't want to change the creature sound for every derived creature.

Still, if I was using the OpenMW-CS for the first time(s) and making new creatures I had no clue what to put into that field.
I'm just suggesting to use a precise title for that field.

Anyway, what about one of the following names:
- "Sounds like: " (quick and dirty)

To make it consistent there would be "looks like" (texture,mesh…,"water") and "feels like" (metal, chitin…).
Admittedly this is probably the most understandable, though still not saying that a reference is requested. Users might enter "Eldafire" or "bird"… or "<path>/bird.mp3"

- "Parent Creature" (may be misleading)

Correct, why not "sound (ID of taken-from creature)"? Or mouseover: "Sound derived of another creature (enter it's ID) - optional".

- "Creature Sound Parent"

Can still be misleading. IMO better "sound from creature: ID".

I had to to ask what that field means, maybe other users will stumble over this too.
I favour "sounds like:" then. Quick and dirty is better than "kept as it is"

#12 Updated by scrawl . 3 months ago

  • Subject changed from OpenMW-CS: the title "Original creature" in creature create/edit is meaningless, please change it to "creature sound ID" to Rename "Original creature" field

I'd vote for using what the original CS used (Sound gen creature) just to prevent any confusion. From the other suggestions my preference would be 'Parent Creature' as that leaves open the possibility of using this link for other features in the future.

#13 Updated by Alexei Dobrohotov about 1 month ago

  • Subject changed from Rename "Original creature" field to Editor: Rename "Original creature" field
  • Status changed from New to Confirmed
  • Operating system changed from Linux to Other

Also available in: Atom PDF