createSimpleTask - Revision history

Lou Montana: Some wiki formatting

2024-03-12T12:09:28Z

Some wiki formatting

← Older revision		Revision as of 14:09, 12 March 2024
Line 21:		Line 21:
	\|descr= Creates a new [[Task]] and adds it to the Diary.		\|descr= Creates a new [[Task]] and adds it to the Diary.
	{{Feature\|Arma3\|Using the '''[[Arma 3: Task Framework]]''' instead is recommended}}		{{Feature\|Arma3\|Using the '''[[Arma 3: Task Framework]]''' instead is recommended}}
	{{Feature\|informative\|When task is added as a child, it appears as subcategory to the parent task in the Tasks menu and can be parent to another child task. However this is cosmetic appearance as each task has own id and can be referenced directly via diary link.}}		{{Feature\|informative\|When task is added as a child, it appears as subcategory to the parent task in the Tasks menu and can be parent to another child task. However this is cosmetic appearance as each task has own id and can be referenced directly via diary link.}}

	\|mp= The task effect is [[Multiplayer Scripting#Locality\|local]], it will only exist on the client it was added.		\|mp= The task effect is [[Multiplayer Scripting#Locality\|local]], it will only exist on the client it was added.

	\|s1= unit [[createSimpleTask]] [name, parentTask]		\|s1= unit [[createSimpleTask]] [name, parentTask]

	\|p1= unit: [[Object]] - unit to add this new task		\|p1= unit: [[Object]] - unit to add this new task
Line 45:		Line 45:
	\|user= Lou Montana		\|user= Lou Montana
	\|timestamp= 20110702114500		\|timestamp= 20110702114500
	\|text= *Creating child will position the new task just under the parent task.		\|text=
	*Creating another "normal" (parent) task will create a new line '''above''' the others. Think of it if you want ordered objectives.		* Creating child will position the new task just under the parent task.
	*Succeeding parent task will automatically succeed childs, whatever their [[taskState]] was set to. (I.E. If a task is set as a child to another, it will be completed when its parent is complete.. no matter if the child task really was or not).		* Creating another "normal" (parent) task will create a new line '''above''' the others. Think of it if you want ordered objectives.
	*This command has to be executed again for it to be applied for JIP players - no server sync<br><br>		* Succeeding parent task will automatically succeed childs, whatever their [[taskState]] was set to. (I.E. If a task is set as a child to another, it will be completed when its parent is complete.. no matter if the child task really was or not).
			* This command has to be executed again for it to be applied for JIP players - no server sync<br><br>
	Full step by step code from beginning to end:<br>		Full step by step code from beginning to end:<br>
	'''Step 1: create a new simpleTask'''		'''Step 1: create a new simpleTask'''
Line 60:		Line 61:
	<sqf>		<sqf>
	MySimpleTask setSimpleTaskDescription [		MySimpleTask setSimpleTaskDescription [
	(localize "STR_aSimpleTaskLongText"),		localize "STR_aSimpleTaskLongText",
	(localize "STR_aSimpleTask"),		localize "STR_aSimpleTask",
	(localize "STR_aSimpleTaskWaypointLabel")		localize "STR_aSimpleTaskWaypointLabel"
	];		];
	</sqf>		</sqf>
	Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
			Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it.
			The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
	'''Step 4: set and update task states'''		'''Step 4: set and update task states'''
	<sqf>MySimpleTask setTaskState "CREATED";</sqf>		<sqf>MySimpleTask setTaskState "CREATED";</sqf>
Line 73:		Line 76:
	MySimpleTask setSimpleTaskDestination (position player);		MySimpleTask setSimpleTaskDestination (position player);
	MySimpleTask setSimpleTaskDescription [		MySimpleTask setSimpleTaskDescription [
	"simple task long description",		"simple task long description",
	"simple task title",		"simple task title",
	"simple task waypoint label"		"simple task waypoint label"
	];		];
	MySimpleTask setTaskState "CREATED";		MySimpleTask setTaskState "CREATED";
	</sqf>		</sqf>

	And then later in the mission:		And then later in the mission:
	<sqf>MySimpleTask setTaskState "SUCCEEDED";</sqf>		<sqf>MySimpleTask setTaskState "SUCCEEDED";</sqf>

	If you want to keep the player in the loop about the status of tasks, you may always do this:		If you want to keep the player in the loop about the status of tasks, you may always do this:
	<sqf>[objNull, objNull, MySimpleTask, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";</sqf>		<sqf>[objNull, objNull, MySimpleTask, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";</sqf>
	}}		}}

Lou Montana: Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

2024-02-01T23:25:06Z

Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

← Older revision		Revision as of 01:25, 2 February 2024
Line 21:		Line 21:
	\|descr= Creates a new [[Task]] and adds it to the Diary.		\|descr= Creates a new [[Task]] and adds it to the Diary.
	{{Feature\|Arma3\|Using the '''[[Arma 3: Task Framework]]''' instead is recommended}}		{{Feature\|Arma3\|Using the '''[[Arma 3: Task Framework]]''' instead is recommended}}
	{{Feature\|~~Informative~~\|When task is added as a child, it appears as subcategory to the parent task in the Tasks menu and can be parent to another child task. However this is cosmetic appearance as each task has own id and can be referenced directly via diary link.}}		{{Feature\|informative\|When task is added as a child, it appears as subcategory to the parent task in the Tasks menu and can be parent to another child task. However this is cosmetic appearance as each task has own id and can be referenced directly via diary link.}}

	\|mp= The task effect is [[Multiplayer Scripting#Locality\|local]], it will only exist on the client it was added.		\|mp= The task effect is [[Multiplayer Scripting#Locality\|local]], it will only exist on the client it was added.

Lou Montana: Text replacement - "(\|[pr][0-9]+ = [^- ]) - *U([a-z ])" to "$1 - u$2"

2023-11-08T14:52:25Z

Text replacement - "(\|[pr][0-9]+ *= *[^- ]*) *- *U([a-z ])" to "$1 - u$2"

← Older revision		Revision as of 16:52, 8 November 2023
Line 27:		Line 27:
	\|s1= unit [[createSimpleTask]] [name, parentTask]		\|s1= unit [[createSimpleTask]] [name, parentTask]

	\|p1= unit: [[Object]] - ~~Unit~~ to add this new task		\|p1= unit: [[Object]] - unit to add this new task

	\|p2= name: [[String]]		\|p2= name: [[String]]

Lou Montana: Text replacement - "(\|[pr][0-9]+ = [^-\r\n]+) - T([a-z])" to "$1 - t$2"

2023-11-08T13:45:17Z

Text replacement - "(\|[pr][0-9]+ *= *[^-\r\n]+) *- *T([a-z])" to "$1 - t$2"

← Older revision		Revision as of 15:45, 8 November 2023
Line 33:		Line 33:
	\|p3= parentTask: [[Task]] - (Optional, [[taskNull]]) - The new task will be a sub task of the parent task		\|p3= parentTask: [[Task]] - (Optional, [[taskNull]]) - The new task will be a sub task of the parent task

	\|r1= [[Task]] - ~~The~~ new task		\|r1= [[Task]] - the new task

	\|x1= <sqf>_currentTask = player createSimpleTask ["NewTask"];</sqf>		\|x1= <sqf>_currentTask = player createSimpleTask ["NewTask"];</sqf>

Lou Montana: Some wiki formatting

2022-05-13T10:01:21Z

Some wiki formatting

← Older revision		Revision as of 12:01, 13 May 2022
Line 42:		Line 42:
	}}		}}

	~~<dl class="command_description">~~		{{Note
			\|user= Lou Montana
	~~<dt></dt>~~		\|timestamp= 20110702114500
	~~<dd class="notedate">Posted on July 02, 2011 - 11:45 (GMT+1)</dd>~~		\|text= *Creating child will position the new task just under the parent task.
	~~<dt class~~=~~"note">[[User:~~Lou Montana\|~~Lou Montana]]</dt>~~
	~~<dd class~~=~~"note">~~
	*Creating child will position the new task just under the parent task.
	*Creating another "normal" (parent) task will create a new line '''above''' the others. Think of it if you want ordered objectives.		*Creating another "normal" (parent) task will create a new line '''above''' the others. Think of it if you want ordered objectives.
	*Succeeding parent task will automatically succeed childs, whatever their [[taskState]] was set to. (I.E. If a task is set as a child to another, it will be completed when its parent is complete.. no matter if the child task really was or not).		*Succeeding parent task will automatically succeed childs, whatever their [[taskState]] was set to. (I.E. If a task is set as a child to another, it will be completed when its parent is complete.. no matter if the child task really was or not).
Line 54:		Line 51:
	Full step by step code from beginning to end:<br>		Full step by step code from beginning to end:<br>
	'''Step 1: create a new simpleTask'''		'''Step 1: create a new simpleTask'''
	<sqf>~~A_SIMPLE_TASK~~ = player createSimpleTask [(localize "STR_aSimpleTask")];		<sqf>MySimpleTask = player createSimpleTask [(localize "STR_aSimpleTask")];</sqf>
	</sqf>
	You may create a task at any given point in time. You just need to be aware of the fact, that you've created the task for a single unit (the player). So if you make use of teamSwitch, respawn or similiar, you need to think about how to manage this, so all of these units will have up to date tasks assigned to them.		You may create a task at any given point in time. You just need to be aware of the fact, that you've created the task for a single unit (the player). So if you make use of teamSwitch, respawn or similiar, you need to think about how to manage this, so all of these units will have up to date tasks assigned to them.
	Second, it is a good practice to use a stringtable, even if you do not plan (yet) to offer translations.<br>		Second, it is a good practice to use a stringtable, even if you do not plan (yet) to offer translations.<br>
	'''Step 2: task destination'''<br>		'''Step 2: task destination'''<br>
	<sqf>~~A_SIMPLE_TASK~~ setSimpleTaskDestination _destination;		<sqf>MySimpleTask setSimpleTaskDestination _destination;</sqf>
	</sqf>
	variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br>		variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br>
	'''Step 3: task description'''		'''Step 3: task description'''
	<sqf>~~A_SIMPLE_TASK~~ setSimpleTaskDescription [		<sqf>
			MySimpleTask setSimpleTaskDescription [
	(localize "STR_aSimpleTaskLongText"),		(localize "STR_aSimpleTaskLongText"),
	(localize "STR_aSimpleTask"),		(localize "STR_aSimpleTask"),
	(localize "STR_aSimpleTaskWaypointLabel")		(localize "STR_aSimpleTaskWaypointLabel")
	];</sqf>		];
			</sqf>
	Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>		Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
	'''Step 4: set and update task states'''		'''Step 4: set and update task states'''
	<sqf>~~A_SIMPLE_TASK~~ setTaskState "CREATED";		<sqf>MySimpleTask setTaskState "CREATED";</sqf>
	</sqf>
	And that's it. Here a minimal working example:		And that's it. Here a minimal working example:
	<sqf>~~A_SIMPLE_TASK~~ = player createSimpleTask ["simple task title"];		<sqf>
	~~A_SIMPLE_TASK~~ setSimpleTaskDestination (position player);		MySimpleTask = player createSimpleTask ["simple task title"];
	~~A_SIMPLE_TASK~~ setSimpleTaskDescription [		MySimpleTask setSimpleTaskDestination (position player);
			MySimpleTask setSimpleTaskDescription [
	"simple task long description",		"simple task long description",
	"simple task title",		"simple task title",
	"simple task waypoint label"		"simple task waypoint label"
	];		];
	~~A_SIMPLE_TASK~~ setTaskState "CREATED";</sqf>		MySimpleTask setTaskState "CREATED";
			</sqf>
	And then later in the mission:		And then later in the mission:
	<sqf>~~A_SIMPLE_TASK~~ setTaskState "SUCCEEDED";		<sqf>MySimpleTask setTaskState "SUCCEEDED";</sqf>
	</sqf>
	If you want to keep the player in the loop about the status of tasks, you may always do this:		If you want to keep the player in the loop about the status of tasks, you may always do this:
	<sqf>[ objNull, objNull, ~~A_SIMPLE_TASK~~, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";		<sqf>[objNull, objNull, MySimpleTask, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";</sqf>
	</sqf>		}}
	~~</dl>~~

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`


2022-05-13T09:58:54Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:58, 13 May 2022
				
Line 85:
Line 85:
</sqf> </sqf>
If you want to keep the player in the loop about the status of tasks, you may always do this: If you want to keep the player in the loop about the status of tasks, you may always do this:
<code>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf"; <sqf>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";
</code> </sqf>
</dl> </dl>



Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "
$1$2"

2022-05-13T09:58:50Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:58, 13 May 2022
				
Line 82:
Line 82:
A_SIMPLE_TASK setTaskState "CREATED";</sqf> A_SIMPLE_TASK setTaskState "CREATED";</sqf>
And then later in the mission: And then later in the mission:
<code>A_SIMPLE_TASK setTaskState "SUCCEEDED"; <sqf>A_SIMPLE_TASK setTaskState "SUCCEEDED";
</code> </sqf>
If you want to keep the player in the loop about the status of tasks, you may always do this: If you want to keep the player in the loop about the status of tasks, you may always do this:
<code>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf"; <code>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";
</code> </code>
</dl> </dl>



Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "
$1$2"

2022-05-13T09:58:45Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:58, 13 May 2022
				
Line 73:
Line 73:
</sqf> </sqf>
And that's it. Here a minimal working example: And that's it. Here a minimal working example:
<code>A_SIMPLE_TASK = player createSimpleTask ["simple task title"]; <sqf>A_SIMPLE_TASK = player createSimpleTask ["simple task title"];
A_SIMPLE_TASK setSimpleTaskDestination (position player); A_SIMPLE_TASK setSimpleTaskDestination (position player);
A_SIMPLE_TASK setSimpleTaskDescription [ A_SIMPLE_TASK setSimpleTaskDescription [
Line 80:
Line 80:
    "simple task waypoint label"     "simple task waypoint label"
]; ];
A_SIMPLE_TASK setTaskState "CREATED";</code> A_SIMPLE_TASK setTaskState "CREATED";</sqf>
And then later in the mission: And then later in the mission:
<code>A_SIMPLE_TASK setTaskState "SUCCEEDED"; <code>A_SIMPLE_TASK setTaskState "SUCCEEDED";



Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "
$1$2"

2022-05-13T09:58:37Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:58, 13 May 2022
				
Line 70:
Line 70:
Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br> Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
'''Step 4: set and update task states''' '''Step 4: set and update task states'''
<code>A_SIMPLE_TASK setTaskState "CREATED"; <sqf>A_SIMPLE_TASK setTaskState "CREATED";
</code> </sqf>
And that's it. Here a minimal working example: And that's it. Here a minimal working example:
<code>A_SIMPLE_TASK = player createSimpleTask ["simple task title"]; <code>A_SIMPLE_TASK = player createSimpleTask ["simple task title"];



Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "
$1$2"

2022-05-13T09:58:30Z
Text replacement - "<dd class="note">([^}]*)<code>([^<]*)<\/code>" to "<dd class="note">$1<sqf>$2</sqf>"

				
				
				
				
				
				← Older revision
				Revision as of 11:58, 13 May 2022
				
Line 63:
Line 63:
variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br> variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br>
'''Step 3: task description''' '''Step 3: task description'''
<code>A_SIMPLE_TASK setSimpleTaskDescription [ <sqf>A_SIMPLE_TASK setSimpleTaskDescription [
    (localize "STR_aSimpleTaskLongText"),     (localize "STR_aSimpleTaskLongText"),
    (localize "STR_aSimpleTask"),     (localize "STR_aSimpleTask"),
    (localize "STR_aSimpleTaskWaypointLabel")     (localize "STR_aSimpleTaskWaypointLabel")
];</code> ];</sqf>
Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br> Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
'''Step 4: set and update task states''' '''Step 4: set and update task states'''

← Older revision		Revision as of 11:58, 13 May 2022
Line 85:		Line 85:
	</sqf>		</sqf>
	If you want to keep the player in the loop about the status of tasks, you may always do this:		If you want to keep the player in the loop about the status of tasks, you may always do this:
	<~~code~~>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";		<sqf>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";
	</~~code~~>		</sqf>
	</dl>		</dl>

← Older revision		Revision as of 11:58, 13 May 2022
Line 82:		Line 82:
	A_SIMPLE_TASK setTaskState "CREATED";</sqf>		A_SIMPLE_TASK setTaskState "CREATED";</sqf>
	And then later in the mission:		And then later in the mission:
	<~~code~~>A_SIMPLE_TASK setTaskState "SUCCEEDED";		<sqf>A_SIMPLE_TASK setTaskState "SUCCEEDED";
	</~~code~~>		</sqf>
	If you want to keep the player in the loop about the status of tasks, you may always do this:		If you want to keep the player in the loop about the status of tasks, you may always do this:
	<code>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";		<code>[ objNull, objNull, A_SIMPLE_TASK, "SUCCEEDED"] execVM "CA\Modules\MP\data\scriptCommands\taskHint.sqf";
	</code>		</code>
	</dl>		</dl>

← Older revision		Revision as of 11:58, 13 May 2022
Line 70:		Line 70:
	Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>		Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
	'''Step 4: set and update task states'''		'''Step 4: set and update task states'''
	<~~code~~>A_SIMPLE_TASK setTaskState "CREATED";		<sqf>A_SIMPLE_TASK setTaskState "CREATED";
	</~~code~~>		</sqf>
	And that's it. Here a minimal working example:		And that's it. Here a minimal working example:
	<code>A_SIMPLE_TASK = player createSimpleTask ["simple task title"];		<code>A_SIMPLE_TASK = player createSimpleTask ["simple task title"];

← Older revision		Revision as of 11:58, 13 May 2022
Line 63:		Line 63:
	variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br>		variable/pointer-to-your-task setSimpleTaskDestination some-position. That's it.<br>
	'''Step 3: task description'''		'''Step 3: task description'''
	<~~code~~>A_SIMPLE_TASK setSimpleTaskDescription [		<sqf>A_SIMPLE_TASK setSimpleTaskDescription [
	(localize "STR_aSimpleTaskLongText"),		(localize "STR_aSimpleTaskLongText"),
	(localize "STR_aSimpleTask"),		(localize "STR_aSimpleTask"),
	(localize "STR_aSimpleTaskWaypointLabel")		(localize "STR_aSimpleTaskWaypointLabel")
	];</~~code~~>		];</sqf>
	Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>		Again, no magic involved here. You take your task, the command setSimpleTaskDescription an pass an array with three strings in it. The first string is the long description text, the second is the name/title of the task and the last one will show up on-screen on the waypoint in cadet mode.<br>
	'''Step 4: set and update task states'''		'''Step 4: set and update task states'''

createSimpleTask - Revision history

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "{{Feature|Informative|" to "{{Feature|informative|"

Lou Montana: Text replacement - "(\|[pr][0-9]+ *= *[^- ]*) *- *U([a-z ])" to "$1 - u$2"

Lou Montana: Text replacement - "(\|[pr][0-9]+ *= *[^-\r\n]+) *- *T([a-z])" to "$1 - t$2"

Lou Montana: Some wiki formatting

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "([^}]*)([^<]*)<\/code>" to "$1$2"

Lou Montana: Text replacement - "(\|[pr][0-9]+ = [^- ]) - *U([a-z ])" to "$1 - u$2"

Lou Montana: Text replacement - "(\|[pr][0-9]+ = [^-\r\n]+) - T([a-z])" to "$1 - t$2"

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`

Lou Montana: Text replacement - "
([^}])`([^<])<\/code>" to "`
`$1$2"`