Migration of links to git repo AndorsTrailRelease

ContentFormatReference/0_Header.txt

@@ -1,3 +1,5 @@
+by Zukero » Fri Aug 11, 2017 1:01 pm
+
 Hello adventurers!
 
 This thread compiles a reference documentation of all files format used to define game content.
@@ -20,10 +22,8 @@ You'll have to know a little bit about the XML and JSON formats for this to make
 [b][url=https://andorstrail.com/viewtopic.php?f=6&t=5825#p57706]NPCs[/url][/b]
 [b][url=https://andorstrail.com/viewtopic.php?f=6&t=5825#p57707]Quests[/url][/b]
 
-by Zukero » Fri Aug 11, 2017 1:01 pm
-
 
 Revised by Nut in March 2023:
-- Migration to git repo AndorsTrailRelease
+- Migration to git repo https://github.com/AndorsTrailRelease/andors-trail/tree/master/AndorsTrail
 - Additions to the engine
 - Small fixes

ContentFormatReference/3_Actor_conditions.txt

@@ -2,7 +2,7 @@ Actor conditions format.
 
 [b]Actor conditions are defined in JSON format. Files containing actor conditions should be named actorconditions_[i]<name>[/i].json, and placed under res/raw/ in the game source folder. The [i]<name>[/i] can be anything composed of lower case letters, digits, and underscores.[/b]
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/actor_condition.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/actor_condition.png[/img]
 A single file can hold any number of actor conditions, as a list. Even if only one actor condition is defined in a file, it must be contained within a list.
 
 Actor conditions, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.

ContentFormatReference/4_Dialogues.txt

@@ -2,7 +2,7 @@ Dialogues format.
 
 Dialogues are defined in JSON format. Files containing dialogues should be named conversationlist_<name>.json, and placed under res/raw/ in the game source folder. The <name> can be anything composed of lower case letters, digits, and underscores.
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/dialogue.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/dialogue.png[/img]
 
 A single file can hold any number of dialogues, as a list. Even if only one dialogue is defined in a file, it must be contained within a list.
 Dialogues, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.
@@ -69,7 +69,7 @@ When the "rewardType" is "[b]alignmentChange[/b]" or "[b]alignmentSet[/b]", the
 [list]When "rewardType" is "[b]createTimer[/b]", the "rewardID" field must contain any textual value that will be this timer's ID. The "value" and "mapName" fields are unused. When granted this reward, the game will keep note of the game time (in game rounds elapsed since you started the game), and use this for comparison in requirements. Every time you [i]create[/i] a timer, any previous note with the same timer ID will be overwritten.[/list]
 [list]When "rewardType" is "[b]spawnAll[/b]", "[b]removeSpawnArea[/b]", or "[b]deactivateSpawnArea[/b]", the "mapName" field must match a map's ID, and the "rewardID" field must match a spawn area's ID within the selected map. The "value" field is unused. In the case of "[b]spawnAll[/b]", when granted this reward, this spawn area will be activated (if it was inactive), and all included NPCs will be spawned immediately. In the case of "[b]removeSpawnArea[/b]", when granted this reward, this spawn area will be deactivated, and all included NPCs will be removed immediately. In the case of "[b]deactivateSpawnArea[/b]", when granted this reward, this spawn area will be deactivated, but all included NPCs will remain on the map until killed or removed by a dialogue reward.[/list]
 [list]When "rewardType" id "[b]activateMapObjectGroup[/b]", or "[b]deactivateMapObjectGroup[/b]", the "mapName" field must match a map's ID, and the "rewardID" field must match an object group's ID within the selected map. The "value" field is unused. In the case of "[b]activateMapObjectGroup[/b]", when granted this reward, all map objects (except spawn areas) within this object group will be made active. In the case of "[b]deactivateMapObjectGroup[/b]", when granted this reward, all map objects (except spawn areas) within this object group will be made inactive (they have no effect on the game anymore).  :!: Beware though, as deactivating an object group containing a replace area that has already been triggered will NOT revert the map to its previous look.[/list]
-[list]When "rewardType" id "[b]changeMapFilter[/b]", the "mapName" field must match a map's ID, and the "rewardID" field must match a color filter's ID, as found here: [url]https://github.com/Zukero/ATCS/blob/master/src/com/gpl/rpg/atcontentstudio/model/maps/TMXMap.java[/url]. The "value" field is unused. When granted this reward, the selected map will have its "colorFilter" property changed to the value of the "rewardID" field. See the post about maps to know the effect of the different available color filters.[/list]
+[list]When "rewardType" id "[b]changeMapFilter[/b]", the "mapName" field must match a map's ID, and the "rewardID" field must match a color filter's ID, as found here: [url]https://github.com/AndorsTrailRelease/ATCS/blob/master/src/com/gpl/rpg/atcontentstudio/model/maps/TMXMap.java[/url]. The "value" field is unused. When granted this reward, the selected map will have its "colorFilter" property changed to the value of the "rewardID" field. See the post about maps to know the effect of the different available color filters.[/list]
 [/list]
 
 [b]The special case of selectors[/b]

ContentFormatReference/5_Droplists.txt

@@ -2,7 +2,7 @@ Droplists format.
 
 [b]Droplists are defined in JSON format. Files containing droplists should be named droplists_[i]<name>[/i].json, and placed under res/raw/ in the game source folder. The [i]<name>[/i] can be anything composed of lower case letters, digits, and underscores.[/b]
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/ui_icon_equipment.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/ui_icon_equipment.png[/img]
 A single file can hold any number of droplists, as a list. Even if only one droplist is defined in a file, it must be contained within a list.
 Droplists, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.
 

ContentFormatReference/6_Items.txt

@@ -2,7 +2,7 @@ Items format.
 
 Items are defined in JSON format. Files containing items should be named itemlist_<name>.json, and placed under res/raw/ in the game source folder. The <name> can be anything composed of lower case letters, digits, and underscores.
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/item.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/item.png[/img]
 
 A single file can hold any number of items , as a list. Even if only one item is defined in a file, it must be contained within a list.
 Items, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.

ContentFormatReference/7_Item_categories.txt

@@ -2,7 +2,7 @@ Item categories format.
 
 Item categories are defined in JSON format. Files containing item categories should be named itemcategories_<name>.json, and placed under res/raw/ in the game source folder. The <name> can be anything composed of lower case letters, digits, and underscores.
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/equip_shield.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/equip_shield.png[/img]
 
 A single file can hold any number of item categories, as a list. Even if only one item category is defined in a file, it must be contained within a list.
 Item categories, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.

ContentFormatReference/8_NPCs.txt

@@ -2,7 +2,7 @@ NPCs format.
 
 NPCs are defined in JSON format. Files containing NPCs should be named monsterlist_<name>.json, and placed under res/raw/ in the game source folder. The <name> can be anything composed of lower case letters, digits, and underscores.
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/npc.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/npc.png[/img]
 
 A single file can hold any number of NPCs, as a list. Even if only one NPC is defined in a file, it must be contained within a list.
 NPCs, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.

ContentFormatReference/9_Quests.txt

@@ -2,7 +2,7 @@ Quests format.
 
 Quests are defined in JSON format. Files containing quests should be named questlist_<name>.json, and placed under res/raw/ in the game source folder. The <name> can be anything composed of lower case letters, digits, and underscores.
 
-[img]https://raw.githubusercontent.com/Zukero/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/ui_icon_quest.png[/img]
+[img]https://raw.githubusercontent.com/AndorsTrailRelease/ATCS/master/src/com/gpl/rpg/atcontentstudio/img/ui_icon_quest.png[/img]
 
 A single file can hold any number of quests, as a list. Even if only one quest is defined in a file, it must be contained within a list.
 Quests, like all JSON-based content, is best created and edited using ATCS, but a text editor can be used for simple fixes (typos...) or by masochists.