DevliN: 1 revision imported: Restoring SC1 backup

2015-03-21T04:27:23Z

1 revision imported: Restoring SC1 backup

DevliN at 10:45, 23 November 2012

2012-11-23T10:45:37Z

New page

'''Strings''' are text values found in a StarCraft map. Every modifiable piece of text in a map is a string. Strings may include special control codes to change things like text alignment and colors.

== String usage ==
The following elements use strings.
*Map title and description
*[[Forces|Force]] names
*[[Locations]] (even if unnamed)
*The "Anywhere" location
*Custom [[Switches|switch]] names
*Custom [[Units|unit]] names
*All text used in the Comment, Display Text Message, Leaderboard, Set Mission Objectives, Set Next Scenario, and Transmission [[trigger]] actions
*All text used in the Mission Objectives, Text Message, and Transmission [[mission briefing]] actions
*[[WAV]] sound paths

== String limits ==
[[StarEdit]] and [[StarForge]] both limit mappers to 1024 individual strings. StarEdit additionally limits all strings to 1024 bytes. (That is, 1024 characters including control codes.) [[SCMDraft 2]] and both of the Uberation programs support an unlimited number of strings. However, the total size of all strings cannot exceed 65536 bytes.

Each character in a string (including control codes) takes up one byte of data. Each string has a two-byte offset value and a one-byte null terminator (which marks the end of the string). So the string "Hello", for example, takes up 8 bytes.

Some third-party [[map editors]], such as SCMDraft 2, will automatically recycle strings that are exact duplicates of each other (whitespace and control codes included). So if someone uses the string "Hello" eight times, SCMDraft 2 will only create one string. (Other map editors would create eight identical and useless copies of that string.) This helps keep maps from reaching the string limit.

=== Saving strings ===
There are ways to save on strings if you hit the limit.
*Set Forces to all share the same name (or leave them unnamed to use the default names).
*Remove names from Switches. You can write down their functions in a text file.
*Remove names from named units that are being used as [[death counters]]. You can write down their functions in a text file.
*Removing names from Locations will not save strings, but setting all Locations to the same name will. (This could cause problems with SCMDraft 2's Text Trigedit, however.)
*When displaying multiple variables at once via Display Text Message, do not have multiple variables on the same line. (If you do, then you need to create a string for every possible combination of both values.)

== Control codes ==
Strings can contain special ''control characters'' that trigger various formatting changes. The control characters' effects tend to differ depending on where the string is displayed. Generally, a control character's effect will last until the end of the line or the next control code. Some codes, however, will "overflow"; they will affect the entire line (overriding subsequent codes). In some cases (such as in Mission Objectives), they will affect ''all'' text that follows them, ignoring newlines.

Such characters are only direcrly available in third-party map editors (you can copy and paste the actual bytes into StarEdit if you have them), and the means through which they are added vary from editor to editor. StarForge provides mappers with clickable buttons; SCMDraft 2 allows mappers to type the character's hex code surrounded by angle brackets (e.x. <code><nowiki><0E></nowiki></code>). To maintain consistency, the SCMDraft 2 notation for control codes will be used in the lists below.

=== List of control codes ===
{| border="1" cellpadding="5" style="width:100%"
|+ '''<big>Global control codes</big>''' These codes have the same effect regardless of where they are displayed.
|-
!style="width:12%"|01
|style="width:13%"|Use object default. Usually cyan.
!style="width:12%"|09
|style="width:13%"|Tab. Does not appear in SCMDraft 2 previews.
!style="width:12%"|0A
|style="width:13%"|Line break.
!style="width:12%"|0B
|style="width:13%"|Invisible. Overflows. Does not appear in SCMDraft 2 previews.
|-
!style="width:12%"|12
|style="width:13%"|Right align. Does not appear in SCMDraft 2 previews.
!style="width:12%"|13
|style="width:13%"|Center align. Does not appear in SCMDraft 2 previews.
!style="width:12%"|14
|style="width:13%"|Invisible. Overflows. Does not appear in SCMDraft 2 previews.
|}

{| border="1" cellpadding="5" style="width:100%"
|+ '''<big>Title screen control codes</big>''' The effects of certain controls on title screen text.
|-
!style="width:12%"|02
|style="width:13%;background:#000"|'''Sky blue'''
!style="width:12%"|03
|style="width:13%"|'''Peach'''
!style="width:12%"|04
|style="width:13%;background:#000"|'''White'''
!style="width:12%"|05
|style="width:13%"|'''Grey''' Overflows.
|-
!style="width:12%"|06
|style="width:13%"|'''Green'''
!style="width:12%"|0D
|style="width:13%;background:#000"|'''Sky blue'''
!style="width:12%"|0E
|style="width:13%;background:#000"|'''Sky blue'''
|}

{| border="1" cellpadding="5" style="width:100%"
|+ '''<big>Glue control codes</big>''' The effects of certain controls on text in lobbies, mission briefings, menus, etc..
|-
!style="width:12%"|02
|style="width:13%;background:#000"|'''Sky blue'''
!style="width:12%"|03
|style="width:13%;background:#000"|'''Green'''
!style="width:12%"|04
|style="width:13%;background:#000"|'''Light Green'''
!style="width:12%"|05
|style="width:13%"|'''Grey''' Overflows.
|-
!style="width:12%"|06
|style="width:13%;background:#000"|'''White'''
!style="width:12%"|07
|style="width:13%;background:#000"|'''Red'''
!style="width:12%"|0D
|style="width:13%;background:#000"|'''Sky blue'''
!style="width:12%"|0E
|style="width:13%;background:#000"|'''Sky blue'''
|}

{| border="1" cellpadding="5" style="width:100%"
|+ '''<big>In-game control codes</big>''' The effects of certain controls on text in Mission Objectives, unit names, etc..
|-
!style="width:12%"|02
|style="width:13%;background:#000"|'''Cyan'''
!style="width:12%"|03
|style="width:13%;background:#000"|'''Yellow'''
!style="width:12%"|04
|style="width:13%;background:#000"|'''White'''
!style="width:12%"|05
|style="width:13%"|'''Grey''' Overflows.
|-
!style="width:12%"|06
|style="width:13%;background:#000"|'''Red'''
!style="width:12%"|07
|style="width:13%;background:#000"|'''Green'''
!style="width:12%"|08
|style="width:13%;background:#000"|'''Red (Player 1)'''
!style="width:12%"|0E
|style="width:13%;background:#000"|'''Blue (Player 2)'''
|-
!style="width:12%"|0F
|style="width:13%;background:#000"|'''Teal (Player 3)'''
!style="width:12%"|10
|style="width:13%;background:#000"|'''Purple (Player 4)'''
!style="width:12%"|11
|style="width:13%;background:#000"|'''Orange (Player 5)'''
!style="width:12%"|15
|style="width:13%;background:#000"|'''Brown (Player 6)'''
|-
!style="width:12%"|16
|style="width:13%;background:#000"|'''White (Player 7)'''
!style="width:12%"|17
|style="width:13%;background:#000"|'''Yellow (Player 8)'''
!style="width:12%"|18
|style="width:13%;background:#000"|'''Green (Player 9)'''
!style="width:12%"|19
|style="width:13%;background:#000"|'''Bright Yellow (Player 10)'''
|-
!style="width:12%"|1A
|style="width:13%;background:#000"|'''Cyan'''
!style="width:12%"|1B
|style="width:13%;background:#000"|'''Tan (Player 11)'''
!style="width:12%"|1C
|style="width:13%;background:#000"|'''Dark Cyan (Player 12)'''
!style="width:12%"|1D
|style="width:13%;background:#000"|'''Greygreen'''
|-
!style="width:12%"|1E
|style="width:13%;background:#000"|'''Bluegrey'''
!style="width:12%"|1F
|style="width:13%;background:#000"|'''Turquoise'''
|}

== Overlapping text in unit names ==
[[File:Overlapping Unit Name.png|frame|right|An example, seen in-game.]]
With clever use of string formatting, mappers can overlap text in unit names, giving such names a multicolored appearance. Unfortunately, color and overlapping are disabled in forces, and using overlapping in a map name makes games unjoinable.

Overlapped names tend to look like this:

[B]Name[F]Name[T][T][T][T][S][S]

...where "Name" is the unit name, "[B]" represents a backspace character (known as "Center Align" in SCMDraft 2), "[F]" represents a frontspace character (known as "Right Align" in SCMDraft 2), "[T]" represents a normal tab, and "[S]" represents a normal space. ("[B]", "[F]", etc., are not the actual characters used to achieve this effect. They are representations; different map editors use different characters.)

The amount of tabs needed to successfully overlap a name tends to vary depending on the name that is being overlapped. The following table contains general estimates. If they are not working, adding or removing a tab may fix any problems. Note that names longer than 12 characters do not always work, and names shorter than 4 characters sometimes become buggy.
{|border="1"
!Characters in name!!Tabs required
|-
|11-12||1
|-
|9-10||2
|-
|7-8||3
|-
|4-6||4
|-
|2-3||5
|}
In cases where the technique isn't working, adding characters after the two trailing spaces may help to properly align the text, and using invisible characters (such as "W", "%", and "Q") in place of tabs may also help. You may notice that SCMDraft 2 and StarForge display control codes (like the backspace character) as tombstones (□); this is perfectly normal.

[[Category:StarCraft]]
[[Category:Reference]]

← Older revision	Revision as of 04:27, 21 March 2015
(No difference)

String - Revision history

DevliN: 1 revision imported: Restoring SC1 backup

DevliN at 10:45, 23 November 2012