• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

editor names don't save? wtf???

Status
Not open for further replies.
Level 10
Joined
Jul 1, 2008
Messages
453
So I'm having this problem with a .mod I'm making. I organized it by adding stuff in the Editor - Editor Prefix box, but when I try and load that mod in a new map, it's not saving and some of my data objects change their name.

WTF blizz... can someone help me? I'll post some pictures if it helps.

thisiswhatiwantu.jpg


wtfgbv.jpg
 
I took a screen shot of the wrong map
but basically, if i open up the mod file (desert.mod) it shows everything fine, however if I load it as a dependency in another map, all the editor names and such are lost and it looks like scrn shot 2
 
UPDATE: I've discovered why the names of the data changed... it seems as if the ID is being used for the name itself. SO like all my neat a pretty parentheses and stuff is lost when put into the actual name because it's only saving/using the ID.

now.. does anyone know why this is and if there's a fix?
 
Names are all localized strings. Thus only a path to them is stored with the data, the actual text is in a separate localization specifc file. If it is failing to load the localized text (eg, if the mod was made by a US person and your using the UK client) then I guess it would exhibit that behaviour. You should still see a valid localization path if you use raw data view for all the "missing" fields, normal view probably hides missing localized text.
 
Status
Not open for further replies.
Back
Top