Staredit Network > Forums > SC1 UMS Theory and Ideas > Topic: Standard Extended Strings
Standard Extended Strings
Sep 13 2013, 6:52 pm
By: jjf28  

Sep 23 2013, 3:35 am trgk Post #21



Suggestion


Post has been edited 1 time(s), last time on Sep 24 2013, 2:33 am by trgk.



EUD

Jul 12 2019, 1:48 am jjf28 Post #22

Cartography Artisan

Since discovering reverse stacking among other compression methods for the STR section the current KSTR format using the highest indexes has become a major problem - I'll be drafting something more solid in a bit but I'm now thinking of the following format...

struct OSTR {
u32 version; // Current version: 1
u32 scenarioName;
u32 scenarioDescription;
u32 forceName[Chk::TotalForces];
u32 unitName[Sc::Unit::TotalTypes];
u32 expUnitName[Sc::Unit::TotalTypes];
u32 soundPath[Chk::TotalSounds];
u32 switchName[Chk::TotalSwitches];
u32 locationName[Chk::TotalLocations];
};

All of scenarioName, scenarioDescription, and forceNames have no good reason to be overridden but I've included them to make the structure exaustive/more future proof.

The trigger section contains the following list of strings: text message, mission objectives, leaderboard text, transmission text, next scenario, sound path, comment. Of these the only editor-specific string is comment, which the trigger metadata section KTRG could cover; sound path can already be overridden via TRIG->WAV->OSTR, the others should be left alone.

Mission briefing only has text message, mission objectives, and sound path - sound path can be overridden via TRIG->WAV->OSTR, others should be left alone.

Everything about KSTR can stay the same - except the way it is read, the ids no longer count backwards from 65535 and no longer have extended string ids stored directly in the sections referencing the strings. The extended strings would get read as the default display string if present in OSTR or KTRG. Location names and sound paths, if reordered in other editors not implementing these sections the connection may be broken, and would have to be manually corrected by users, triggers would be reasonably well locked to the extended strings, unless recompiled in some text editor not preserving full player data (which KTRG uses to link a trigger to its metadata)

Post has been edited 1 time(s), last time on Jul 12 2019, 1:53 am by jjf28.



Rs_yes-im4real - Clan Aura - jjf28.net84.net

Reached the top of StarCraft theory crafting 2:12 AM CST, August 2nd, 2014.

Options
  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[06:59 pm]
Ultraviolet -- Suicidal Insanity
Suicidal Insanity shouted: Or maybe: ScmDraft 2: Rendering staredit obsolete since 2003?
That one's got a good ring to it
[06:07 pm]
Suicidal Insanity -- Or maybe: ScmDraft 2: Rendering staredit obsolete since 2003?
[05:44 pm]
Suicidal Insanity -- ScmDraft 2: Now the fully official inofficial staredit replacement (Unless you install 1.16.1)
[05:43 pm]
Suicidal Insanity -- :P
[05:43 pm]
Suicidal Insanity -- Ya the entire site is now outdated
[05:16 pm]
Ultraviolet -- might have to change the url here, too. Scmdraft2.net ;)
[05:16 pm]
Ultraviolet -- Not the most accurate description anymore, eh? Scmdraft 2: The Standard SC Map Editor; replacing Staredit since the 2000's!
[04:31 pm]
Suicidal Insanity -- Maybe I should no longer call scmdraft 2 an alternative starcraft map editor ;D
[2019-7-14. : 8:29 pm]
Ultraviolet -- Suicidal Insanity
Suicidal Insanity shouted: or the scmdraft thread here
Suicidal Insanity
Suicidal Insanity shouted: or the one in the bnet forums
Suicidal Insanity
Suicidal Insanity shouted: or the one on reddit
:lol:
[2019-7-14. : 7:04 pm]
Suicidal Insanity -- or the one on reddit
Please log in to shout.


Members Online: Roy, Blackbirdx661