Difference between revisions of "Launcher"

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

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.

The log of the current client session is visible here.

See also: Logging

@@ Line 1: / Line 1: @@
-The client starts up with a separate launcher that is responsible to keep the client updated. Besides that it also sets the JVM parameters for the client.
+Exilent starts up with a separate application called the launcher.
-== Log ==
+The launcher is responsible for keeping the client file and its dependencies up to date and setting the JVM parameters.
-The client logs events for debugging and error reporting purposes. If you run into some problems/bugs this is where you should look first. Posting the logs of an incident helps the developer resolving the problem.
+https://i.imgur.com/mFCFnaR.png
+https://i.imgur.com/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