Difference between revisions of "Launcher"

From Exilent
 
(13 intermediate revisions by the same user not shown)
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/qJjPeeA.png
+
https://i.imgur.com/mFCFnaR.png
  
== Log ==
+
https://i.imgur.com/30xg4ax.png
 +
 
 +
== 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
+
* JVM parameters (do not touch them unless needed)
** '''Max heap size''': controls the max memory used by the client. Setting it too low can cause lag/crash.
+
** '''Max heap size''': max memory used by the client  
*** Recommended: 1024MB.
+
** '''Garbage collector''': mechanism for memory management
** '''Garbage collector:  
+
** '''DirectDraw''': controls hardware acceleration of rendering the GUI
** '''DirectDraw''': controls the hardware acceleration.
+
** '''VM args''': extra JVM params can be passed here
*** Recommended: true for Nvidia/AMD video cards, false for Intel integrated video cards.
+
** '''Program args''': extra program params can be passed here
*** If you have performance issues try changing this.
 
 
* Client
 
* Client
** '''Default world''':
+
** '''Default world''': world used to launch the client
 
 
== 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

Latest revision as of 08:03, 6 July 2021

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.

mFCFnaR.png

30xg4ax.png

View Log

The log of the current client session is visible here.

See also: Logging

Settings

  • JVM parameters (do not touch them unless needed)
    • 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 params can be passed here
    • Program args: extra program params can be passed here
  • Client
    • Default world: world used to launch the client
  • Reset client settings: sets all Exilent settings to default