WildStar:UI AddOn: Difference between revisions

From AddOn Studio
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{dev/uiaddon}}
{{dev/uiaddon}}
<!--
This is the development reference for the structure and rules for WildStar '''UI AddOns'''. See [[AddOns]] for the general WildStar term. See [[development]] for the main development portal.
This is the development reference for the structure and rules for WildStar '''UI AddOns'''. See [[AddOns]] for the general WildStar term. See [[development]] for the main development portal.


Line 75: Line 74:
* [http://www.hiddenarena.com/content.php?160-Getting-Started-with-WildStar-Addon-Creation-Guide-Part-1 hiddenarena.com] ''Getting Started with WildStar Addon-Creation'' by Taterz (Dec-31-2013)
* [http://www.hiddenarena.com/content.php?160-Getting-Started-with-WildStar-Addon-Creation-Guide-Part-1 hiddenarena.com] ''Getting Started with WildStar Addon-Creation'' by Taterz (Dec-31-2013)
* [http://wildstarnasa.com/2014/01/a-complete-newbies-guide-to-apollo-and-houston/ wildstarnasa.com] - ''A Complete Newbie’s Guide to Apollo and Houston''
* [http://wildstarnasa.com/2014/01/a-complete-newbies-guide-to-apollo-and-houston/ wildstarnasa.com] - ''A Complete Newbie’s Guide to Apollo and Houston''
-->

Revision as of 01:35, 13 August 2023

This is the development reference for the structure and rules for WildStar UI AddOns. See AddOns for the general WildStar term. See development for the main development portal.

Reference

WS AddOn files and related files and concepts

Code files

  • TOC file - WS AddOn special "manifest" 'toc.xml' file.
  • XML file - WS AddOn 'XML' UI element 'form' file.
  • LUA file - WS AddOn 'Lua' code file.

Details

Client files

Art files

Help

Guides

FAQs

Icon-edit-22x22.png
Note: This is a generic section stub. You can help expand it by clicking Sprite-monaco-pencil.png Edit on the section title.

Summary

WildStar is capable of loading special files for adding or modifying aspects of the game. WS uses these files to create User Interface functionality for its own interface. These files and facilities can also be used for creating custom user UI functionality, or AddOns for WS. Before getting started, should read familiarize themselves with the WildStar AddOn Policy.

Example file layout anatomy of a basic WS AddOn:

  • {WS Install} (folder) - your WS installation folder
    • -- nothing --
  • {Operating system drive} (drive) - your actual operating system 'system drive'
    • Users (folder) - standard Windows Users folder, in the root of the drive
      • {User name} (folder)
        • AppData (folder)
          • Roaming (folder)
            • NCSOFT (folder)
              • WildStar (folder)
                • AddOns (folder)
                  • MyAddOn (folder) - your AddOn's own folder, normally matches the AddOn name
                    • toc.xml (TOC file) - WS AddOn "manifest" file
                    • MyAddOn.xml (XML file) - XML file with visible element 'form' definitions
                    • MyAddOn.lua (Lua file) - Code file, with instructions for AddOn behavior


This example establishes a WS AddOn named 'MyAddOn' with one xml form file and one Lua code file.

AddOns folder

For WildStar, most AddOn related files lie in your personal folders in the normally hidden AppData location. The WildStar AddOns folder inside AppData contains folders for each user AddOn.

Using windows environment values:

 %appdata%\NCSOFT\WildStar\AddOns

Typical example

 c:\Users\[UserFolderName]\AppData\Roaming\NCSOFT\WildStar\AddOns

External links