Protect the server license
The HumaLike server license is a secret. Configure it with server-onlyset:
setr, commit the value, paste it into a client script, include it in
a screenshot, or publish it in logs. Rotate it from the dashboard if exposed.
HumaLike derives short-lived runtime access from the license. Do not copy,
persist, log, or manually configure those runtime values.
Trust boundaries
Client events and action parameters are untrusted. Custom providers must enforce permissions and validate player state, distance, item names, quantities, metadata, account amounts, and framework identifiers on the server. UseReportPlayerEvent from an authoritative server handler. Do not expose a
generic client event that lets a player report arbitrary identity, item, badge,
or roleplay observations.
Separate custom code
Keep custom bridges outside thehumalike directory. This prevents accidental
credential disclosure, makes ownership clear, and permits complete verified
resource updates.
Register only the domains the bridge implements. Use specific provider names,
minimal exports, and the least ACE permissions necessary.

