Difference between revisions of "Launcher"

From Exilent
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
The client starts up with a separate application that is responsible to keep the client file and its dependancies updated. Besides that it also sets the JVM parameters for the client.
+
Exilent starts up with a separate application called the launcher.
  
https://i.imgur.com/qJjPeeA.png
+
The launcher is responsible for keeping the client file and its dependencies up to date and setting the JVM parameters.
  
== Log ==
+
https://i.imgur.com/mFCFnaR.png
The [[logs]] of the current client session is visible here.
 
  
== Parameters ==
+
https://i.imgur.com/30xg4ax.png
* Max heap size: controls the max memory used by the client. Recommended: 1024MB
 
* DirectDraw: controls the hardware acceleration. Recommended: true for Nvidia/AMD video cards, false for Intel integrated video cards.
 
* Prefer IPv4: uses ipv4 protocol over ipv6 which is not supported by all computers yet.
 
  
== Tools ==
+
== View Log==
* Open client folder: helps you location the client files
+
The log of the current client session is visible here.
* Reset resource files: resolves resource related problems
+
 
* Reset client settings: resolves settings related problems
+
{{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

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