UGX Launcher We are updaing the UGXL Documentation! The old UGX Launcher Documentation prior v0.8.0 can be found here!
Skip to end of metadata
Go to start of metadata

The UGX Launcher can be started with launch parameters (command line parameters) to influence the UGX Launcher.

 

 ShortLongDescriptionNote
-d
-debug

Enable Debug Mode (Logger & Debugger)

 
-log
-logfile

Enable logging to logfile

Force Enabled during Beta Phase
-logcat
-logcategories
Allow logging for categories to be enabled or disabled in a flexible way

For more information read the official Qt5 documentation: http://doc.qt.io/qt-5/qloggingcategory.html#logging-rules

Read below about all available log categories.

-off
-offline

Force offline mode (not implemented yet)

Not supported yet!

-des
-designer
Designer Mode, so styling will be easier 
    
-map
-launch

Launch map

Not implemented yet!

-type
-launch_type

COOP or SP

Not implemented yet!

    
 
-nodonor
Disable any donors specific benefits (will turn a donor account into non donor)Note that certain donor permissions are untouched (like beta access)
    
 
-reset
Reset UGXL to default. (Settings and group order) 
 
-clearcache
Will clear any cached files. (including webcache) 
    
 
-profile <name>
Set the profile to <profile>Depending on the name, a new config file will be created. Default is settings.default.ini

 

Debugging

After enabling the Debug Mode (-d | -debug) you will get access to the Logger & Debugger.

Logging

Logging is forced in Beta

While in Beta, the logfile is forced to help development.

Log File

After enabling logfile support (-log | -logfile) any availabke log messages will be written to the logfile.

There can be up to 5 logfiles stored in the log folder, located at

<ugxl_root>/logs

<ugxl_root>/logs/ugxl.log | main logfile of current / latest application run
<ugxl_root>/logs/ugxl.*.log | where * = 1 up to 3, each time the application runs it will be incremented up, on 4 it will be deleted

 

Log Categories

Possible Types: debug, info, warning, or critical

CategoryInformation
default
Default log
socket.io
Socket.io logging
awe.js
Awesomium Javascript
awe
Awesomium
mod.ent
Mod Entity (represents a mod, like UGX Requiem)
mod.dl
Mod Download
mod.man
Mod Manager
man.set
Settings Manager
man.not
Notification Manager
man.game
Game Manager
man.wmi
WMI Manager
man.fitler
Filter Manager
man.acc
Account Manager
addon.t4m
T4M
webreq
Web Request
login
Login (UI)
mod.list
Mod List (UI)
mod.view
Mod View (UI)
settings
Settings (UI)
uninstall
Uninstall (UI)
dloadman
Download Manager (UI)

To enable / disable certain categories, use the following format:

Each entry needs to be in a new line, so two or more entries need to be seperated by \n (new line)

-logcat "default.debug=false" | Hide all default debug massages
-logcat "default.*=false" | Hide all default messages
-logcat "default.*=false\ndefault.critical=true" | Hide all default messages and enable critical messages again
-logcat "*.*=false\nsettings.debug=true" | Disable all messages and enable debug settings messages agai
  • No labels