it's a bit time consuming, but you can do stuff in the GUI~Editor first, and then look at it in code view, seeing how it's done in code (and for me, the reverse, lol~hehe. Doing it in code, then switching to the GUI~Editor mode, to see how it's done via the GUI~Editor, lol).
if you don't yet know, besides just opening the file with notepad, wordpad, or notepad++ (highly recommend to download if you don't use it already, very useful for writing, editing, and troubleshooting code. From the top menu, when using notepad++ software, under the "language" menu choice, choose "XML" for the coding language), within the GUI~Editor, at the top is a bar, click on the notepaper like button (it's between the "play" and "?-help" buttons. This notepaper like button is a toggle button, for switching between the GUI~Editor mode and the Code View mode.
----------
the conflict is likely due to having two things with the same NAME attribute.
NAME attribute: this is used as the "ID" (identifier) for the game engine, so you can't have two things with the same Name Attribute.
ALIAS attribute: this is for us the players of the game during game play, it is what we see, it is the "name" of the thing for us. But, the ALIAS attribute is *NOT* used by the game engine to recognize~identify things, so you can have multiple things with the same ALIAS attribute.
In Code, for example:to CREATE (Add) a Name Attribute to an Object and~or an attribute (and to create~add an object and~or Attribute too, if that is what you've choosen to code):
<object name="orc_boss_1">
</object>
OR, in this format (an old version but still useable format for attributes), the first word~string (orc_boss_1) is recognized as the NAME attribute:
<orc_boss_1 type="object">
</orc_boss_1>
<dead type="boolean">false</dead>
<strength type="int">50</strength>
<hit_points type="double">5005.9813</hit_points>
<race type="string">human</race>
<race_string_list type="simplestringlist">human; dwarf; elf; orc</race_string_list> // notice how I can't also call (NAME attribute) this as "race", using instead "race_string_list" as it's Name Attribute, due to already using "race" for my String Attribute's NAME attribute above, as it'll cause an error.
<game_over type="script"><![CDATA[
-> if (player.hit_points <= 0) {
->-> msg ("GAME OVER")
->-> finish
-> }
]]></game_over>
for Scripting (actions, USING the object_and_its_attribute or just a variable_string):
Global~Permanent: name_of_object.name_of_attribute=Value_or_Expression
example using a Value: HK.strength = 100
example using an Expression ("addr" = add'er = addition): HK.strength = HK.strength + 5
conceptually:
HK.strength = 0 (old~initial~starting value)
HK.strength (new value) = HK.strength (old value) + 5
HK.strength = 0 + 5
HK.strength = 5 (new value)
~OR~
Local~Temporary: name_of_variable_string=Value_or_Expression
Example: you_go_first_in_combat = true~false // or: yes~no, plus~minus, up~down (lol), black~blue (lol), etc etc etc (whatever strings you want to use, long as you use them properly)
example of using "exotic" strings ("black", "blue", and "yellow"):
show menu ("what color?", split ("black;blue;yellow", ";"), false) {
-> // quest engine does this automatically for you: result = what you selected
-> value_x = result
-> switch (value_x) {
->-> case ("black") {
->->-> msg ("1")
->-> }
->-> case ("blue") {
->->-> msg ("2")
->-> }
->-> case ("yellow") {
->->-> msg ("3")
->-> }
-> }
}
In GUI~Editor, for example:"room" (default single Room Object) -> Objects (Tab) -> Add ->
Name (popup box, type it's name in here): orc_boss_1
"player" (default single Player Object) -> Attributes (Tab) -> Attributes -> Add ->
(you don't have these options~boxes for "Type" and "Value" in the online~web version; but you can use a roundabout way, by using the: Game -> Scripts Tab -> "Start" Script -> Add a~new script -> Variables -> Add a variable or attribute -> fill it in)
Attributes of the "player" (Player) Object's Attributes:
Attribute 1:
Name Attribute: strength
Type Attribute: int
Value Attribute: 100
Attribute 2:
Name: flying
Type: boolean
Value: false
Attribute 3:
Name: death
Type: script
Value (as an Expression): if (player.hit_points <= 0) { finish }
Attribute 4:
Name: bag_of_food
Type: objectlist
Value (as an Expression... or maybe not, not sure on this, meh, lol): bread; salted_pork; etc
so, if we have (I'll use the code form instead, as it's quicker to type out ~ why I like using code when trying to explain stuff):
// your object
<object name="orc">
</object>
// HK's Library's object
<object name="orc">
</object>
= ERROR!
// your script (verb)
<equip type="script">
</equip>
// HK's Library's script (verb)
<equip type="script">
</equip>
= ERROR!
---------------------------
// your object
<object name="orc_boss_1">
</object>
// HK's Library's object
<object name="orc_boss_2">
</object>
= NO error! = it WORKS!
// your object
<object name="orc_boss_1">
-> <alias type="string">orc</alias> // or, this simplified format~syntax: <alias>orc</alias>
-> <strength type="int">100</strength>
</object>
// HK's Library's object
<object name="orc_green_1">
-> <alias type="string">orc</alias> // or, this simplified format~syntax: <alias>orc</alias>
-> <strength type="int">25</strength>
</object>
// HK's Library's object
<object name="orc_dark_green_1">
-> <alias type="string">orc</alias> // or, this simplified format~syntax: <alias>orc</alias>
-> <strength type="int">50</strength>
</object>
// HK's Library's object
<object name="orc_shadow_1">
-> <alias type="string">orc</alias> // or, this simplified format~syntax: <alias>orc</alias>
-> <strength type="int">75</strength>
</object>
= NO error! = it WORKS!
Follow us on Facebook
Follow @TextAdv on Twitter