Difference between revisions of "Launcher"

From Exilent
Line 1: Line 1:
 
Exilent starts up with a separate application called the launcher.
 
Exilent starts up with a separate application called the launcher.
  
The launcher is responsible for keeping the client file and its dependencies updated and setting the JVM parameters.
+
The launcher is responsible for keeping the client file and its dependencies up to date and setting the JVM parameters.
  
https://i.imgur.com/v9706MY.png
+
https://i.imgur.com/BbfpQWg.png
  
== Log ==
+
== View Log==
 
The log of the current client session is visible here.
 
The log of the current client session is visible here.
  
 
{{See also|Logging}}
 
{{See also|Logging}}
  
== Parameters ==
+
== Settings==
* JVM: change these values only if you have performance issues
+
* JVM paremeters
 
** '''Max heap size''': max memory used by the client  
 
** '''Max heap size''': max memory used by the client  
 
** '''Garbage collector: mechanism for memory management
 
** '''Garbage collector: mechanism for memory management
 
** '''DirectDraw''': controls hardware acceleration of rendering the GUI
 
** '''DirectDraw''': controls hardware acceleration of rendering the GUI
 +
** '''VM args''': extra JVM pars can be passed here
 +
** '''Program args''': extra program params can be passed here
 
* Client
 
* Client
 
** '''Default world''': world used to launch the client, change it in case the world goes offline
 
** '''Default world''': world used to launch the client, change it in case the world goes offline
 
== Tools ==
 
* '''Open client folder''': helps you locate where the files of Exilent are stored
 
 
* '''Reset client settings''': sets all Exilent settings to default
 
* '''Reset client settings''': sets all Exilent settings to default

Revision as of 18:46, 16 October 2019

Exilent starts up with a separate application called the launcher.

The launcher is responsible for keeping the client file and its dependencies up to date and setting the JVM parameters.

BbfpQWg.png

View Log

The log of the current client session is visible here.

See also: Logging

Settings

  • JVM paremeters
    • Max heap size: max memory used by the client
    • Garbage collector: mechanism for memory management
    • DirectDraw: controls hardware acceleration of rendering the GUI
    • VM args: extra JVM pars can be passed here
    • Program args: extra program params can be passed here
  • Client
    • Default world: world used to launch the client, change it in case the world goes offline
  • Reset client settings: sets all Exilent settings to default