Update 0.1.4: Difference between revisions
Jump to navigation
Jump to search
Document upcoming 0.1.4 weapon confirmation and mouse camera APIs |
Clarify 0.1.4 weapon clearing, manual equipment and confirmation APIs |
||
| Line 18: | Line 18: | ||
== Weapon requests and mouse capture == | == Weapon requests and mouse capture == | ||
* [[Weapon control]]: independent melee/ranged confirmation, [[getPlayerWeaponState]] and [[onPlayerWeaponChangeResult]]. | * [[Weapon control]]: independent melee/ranged confirmation, [[getPlayerWeaponState]] and [[onPlayerWeaponChangeResult]]. | ||
* Weapon clearing: native slot and carry-visual cleanup, server confirmation and empty replication/late-join state; subsequent manual equipment changes remain allowed. No new Lua signatures are introduced by these corrections. | |||
* [[Mouse capture]]: resource-owned relative motion and look-only capture for camera scripts. | * [[Mouse capture]]: resource-owned relative motion and look-only capture for camera scripts. | ||
* [[UpdateCameraPose]]: latest-value camera streaming. | * [[UpdateCameraPose]]: latest-value camera streaming. | ||
These changes require the current 0.1.4 development client and updated server. This is not a public updater rollout. | |||
These changes require the | |||
<!-- weapon-mouse014:end --> | <!-- weapon-mouse014:end --> | ||
Revision as of 13:42, 20 September 2026
Update 0.1.4
Status: in development. The public release remains 0.1.3. This page documents the next version, not an updater rollout.
MySQL recovery
- dbConnect gains the opt-in autoreconnect=true option (default false).
- New server functions: dbReconnect and dbGetConnectionState.
- New server event: onDatabaseConnectionStateChange.
- Background reconnect with backoff, generation tracking, idle health checks and resource ownership.
- No automatic SQL replay; interrupted transactions/session-control operations require explicit recovery.
- gothic_rp reconnects after runtime loss without replaying startup initialization; uncertain COMMIT results are reconciled using transaction receipts.
- Character saves no longer treat queue acceptance as successful persistence.
See MySQL connection recovery for examples, limitations and test cases. Existing 0.1.3 servers do not expose the new functions or event; update the dedicated server before using these scripts. This database change does not alter network protocol 35.
Weapon requests and mouse capture
- Weapon control: independent melee/ranged confirmation, getPlayerWeaponState and onPlayerWeaponChangeResult.
- Weapon clearing: native slot and carry-visual cleanup, server confirmation and empty replication/late-join state; subsequent manual equipment changes remain allowed. No new Lua signatures are introduced by these corrections.
- Mouse capture: resource-owned relative motion and look-only capture for camera scripts.
- UpdateCameraPose: latest-value camera streaming.
These changes require the current 0.1.4 development client and updated server. This is not a public updater rollout.