Add an event to localize new Item Categories

[Iridar]

Fixes #1112

[github-actions]

Pull request modifies event listener templates

Difference (click to expand)

diff --git a/target/CHL_Event_Compiletest.uc b/target/CHL_Event_Compiletest.uc
index c229218..e7b195b 100644
--- a/target/CHL_Event_Compiletest.uc
+++ b/target/CHL_Event_Compiletest.uc
@@ -217,6 +217,22 @@ static function EventListenerReturn OnGetCovertActionEvents_Settings(Object Even
 	return ELR_NoInterrupt;
 }
 
+static function EventListenerReturn OnGetLocalizedItemCategory(Object EventData, Object EventSource, XComGameState GameState, Name EventID, Object CallbackObject)
+{
+	local X2ItemTemplate ItemTemplate;
+	local XComLWTuple Tuple;
+	local string CategoryLocale;
+
+	ItemTemplate = X2ItemTemplate(EventSource);
+	Tuple = XComLWTuple(EventData);
+
+	// Your code here
+
+	Tuple.Data[0].s = CategoryLocale;
+
+	return ELR_NoInterrupt;
+}
+
 static function EventListenerReturn OnHeadquartersUnitFired(Object EventData, Object EventSource, XComGameState GameState, Name EventID, Object CallbackObject)
 {
 	local XComGameState_Unit FiredUnit;

What? (click to expand)

The Highlander documentation tool generates event listener examples from event specifications.
This comment contains the modifications that would be made to the copy-pasteable event listeners in documentation, for PR authors and reviewers to inspect for correctness, and will automatically be kept up-to-date whenever this PR is updated.

[Iridar]

In retrospect, using the event system for this is a huge overkill, especially in the presence of the Localize() function, but let's keep the event for the sake of consistency with similar implementation in `X2WeaponTemplate'.