Difference between revisions of "Launcher"
From Exilent
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
https://i.imgur.com/mFCFnaR.png | https://i.imgur.com/mFCFnaR.png | ||
| + | |||
| + | https://i.imgur.com/30xg4ax.png | ||
== View Log== | == View Log== | ||
| Line 19: | Line 21: | ||
* Client | * Client | ||
** '''Default world''': world used to launch the client | ** '''Default world''': world used to launch the client | ||
| − | * 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.
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
