Skip to main content

​
Install a release

Use the humalike.zip asset from GitHub Releases. Do not download GitHub’s automatic source archives: they contain repository files, not the composed runtime resource. Place the extracted humalike directory directly in a resources directory and start it by name:
The directory must not be nested as humalike/humalike.

​
Resource order

HumaLike can start without a framework. For automatic selection during initial startup, start optional dependencies first:
Late-starting and restarted dependencies are detected. A custom bridge should start after humalike and declare it as a dependency.

​
Callback networking

The callback URL registered in the dashboard must reach the FXServer from the public internet. Allow inbound TCP traffic to the selected server port. If you change the FXServer port or public address, update the callback in the dashboard. The URL format is:
The host must be a globally routable literal IPv4 address. Hostnames, IPv6, private addresses, loopback addresses, and reserved example addresses are not accepted. Supported ports are 1024–65535; do not add a path, query, or fragment.

​
Update

  1. Download the new release and verify its published SHA-256 checksum.
  2. Stop humalike or stop the FXServer.
  3. Keep the previous directory as a rollback copy outside the active resources tree.
  4. Replace the complete humalike directory.
  5. Start it and run humalike_status.
Do not merge a new release over the old directory. Removed files would remain active and can produce mixed-version behavior. Keep custom code in a separate bridge resource. Updating HumaLike should never overwrite server-specific jobs, dispatch logic, rewards, or UI hooks.

​
Roll back

Stop the resource, restore the complete directory from the previous release, and start it again. The server license remains valid. If the dashboard schema or required server behavior changed in a release, follow that release’s notes before rolling back.

​
Development builds

Production servers should use release archives. Repository checkouts require a frontend build and are intended only for contributors. A release already contains all compiled NUI assets.

​
Next