ValidateWorldDoors: Difference between revisions
Jump to navigation
Jump to search
Document upcoming 0.1.9 custom native keys, shared doors, server Lua callbacks and persistence; not a release |
Release 0.1.9 / BUILD264 / Protocol42: availability and download setup; preserve experimental limits |
||
| Line 1: | Line 1: | ||
= validateWorldDoors = | = validateWorldDoors = | ||
'''Available from 0.1.9 | '''Available from 0.1.9. Use matching updated server and clients.''' | ||
Server Lua. Part of [[Custom keys|custom keys and shared placed doors]]. | Server Lua. Part of [[Custom keys|custom keys and shared placed doors]]. | ||
Latest revision as of 13:30, 20 October 2026
validateWorldDoors
Available from 0.1.9. Use matching updated server and clients.
Server Lua. Part of custom keys and shared placed doors.
Syntax
ok, error = validateWorldDoors(doors)
Parameters and behavior
Same complete array, limits and compatibility checks as setWorldDoors, without applying placements, locks or state. A later state change can invalidate an earlier successful check.
Returns
true, empty error when valid now; false, error string otherwise. No objects are created.
Examples and security
See Custom keys for complete registration, copy issuance, placement, persistence and callback examples. These are server functions, not client RPC endpoints. Do not forward untrusted client arguments without gameplay authorization.