https://wiki.returnofreckoning.com/index.php?action=history&feed=atom&title=API%3AWindowGameAction 2026-10-17T17:54:15Z Revision history for this page on the wiki MediaWiki 1.43.11 https://wiki.returnofreckoning.com/index.php?title=API:WindowGameAction&diff=30865&oldid=prev 2026-10-16T19:51:22Z

<p>UI Lua API import (WAR 1.4.8)</p> <p><b>New page</b></p><div>{{LuaApi|group=Window}}<br /> Carries out the game action attached to a window.<br /> <br /> &lt;pre&gt;<br /> WindowGameAction(windowName)<br /> &lt;/pre&gt;<br /> <br /> == Arguments ==<br /> ;windowName : &lt;code&gt;string&lt;/code&gt; – Name of the window.<br /> <br /> == Returns ==<br /> Nothing.<br /> <br /> == Details ==<br /> * The client runs the game action that was attached to the window with [[API:WindowSetGameActionData|WindowSetGameActionData]].<br /> * Nothing happens if the window has no game action. The client also skips the action unless a flag on the window is set and a client-wide flag is clear; what controls these flags could not be determined.<br /> * The stock action buttons call it from their click handler for slots that do not need special handling (see the example).<br /> * The function needs at least one argument and only reads the last one.<br /> <br /> == Errors ==<br /> This is written to the UI log; the call returns normally.<br /> * &lt;code&gt;Error in function call &#039;WindowGameAction&#039;: Window %s does not exist&lt;/code&gt;<br /> <br /> == Example ==<br /> From &lt;code&gt;ea_actionbars/source/actionbutton.lua&lt;/code&gt;, where an action button runs its action from a click handler:<br /> &lt;pre&gt;<br /> else<br /> WindowGameAction( SystemData.ActiveWindow.name )<br /> end<br /> &lt;/pre&gt;<br /> <br /> == See also ==<br /> * [[API:WindowSetGameActionData|WindowSetGameActionData]]<br /> * [[API:WindowGetGameActionData|WindowGetGameActionData]]<br /> * [[API:WindowSetGameActionTrigger|WindowSetGameActionTrigger]]</div>

Maintenance script