Hello, i have a file here that is called TriggerStings.txt and basic all there are codes like these Trigger/Name/D51CD746=Switch to Item Shop.......
i would like yo know how to add them. i would also want to know what they are called meaning is called Text or just String?
Most text should be done via external lookup. There is where a path is given and a localized text element returned. This decouples localization from implementation which is important for developing maps with multiple language support. The theory is that translators (people writing the localizations) only need to see the text file with all the string declarations.
GUI uses a lot of trigger generated paths designed for uniqueness rather than actually being helpful to understanding what the text represents. In theory you can use custom lookup paths that are more meaningful however in the end it makes very little difference.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hello, i have a file here that is called TriggerStings.txt and basic all there are codes like these Trigger/Name/D51CD746=Switch to Item Shop....... i would like yo know how to add them. i would also want to know what they are called meaning is called Text or just String?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAs I told you over the other thread, those are just trigger names and nothing else. They are not scripts at all. You need th galaxy files.
Go play Antioch Chronicles Remastered!
Also, coming soon, Antioch Episode 3: Thoughts in Chaos!
Dont like mapster's ugly white? Try Mapster's Classic Skin!
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumJust open the map in editor, and copy paste over to a new map, unless you cracking a locked map, in which case you can't do that.
Still alive and kicking, just busy.
My guide to the trigger editor (still a work in progress)
@SFEdev: Go
it could be for localization. it's text
Most text should be done via external lookup. There is where a path is given and a localized text element returned. This decouples localization from implementation which is important for developing maps with multiple language support. The theory is that translators (people writing the localizations) only need to see the text file with all the string declarations.
GUI uses a lot of trigger generated paths designed for uniqueness rather than actually being helpful to understanding what the text represents. In theory you can use custom lookup paths that are more meaningful however in the end it makes very little difference.