Set up baseevents and choose an event contract
baseevents supplies death and vehicle observations for resources that depend on it. Start the installed stock resource before its consumers. Its reports are useful gameplay notifications, not proof that a client-reported kill, position or vehicle action is authoritative.
Start the installed resource
In the active server configuration, put ensure baseevents before resources that use its events. In a consumer manifest, declare dependency 'baseevents' to express that dependency. Check the first server-console error and the actual resource name if startup fails; an extra archive directory or missing resource will not be repaired by changing an event name.
The existing resource overview lists client/server availability. Use the contract pages below for exact arguments and limits, rather than copying one payload shape to every death or vehicle event.
Death notifications
- onPlayerDied: killer type and death coordinates.
- onPlayerKilled: killer ID meaning and the emitted data fields.
- onPlayerWasted: legacy fallback with a different payload.
Vehicle observations
Follow enteringVehicle, enteringAborted, enteredVehicle and leftVehicle. A client-local entity handle is not interchangeable with a network ID; see network identifiers.
For rewards, access control or persistent state, validate the action and current session on the server. Do not grant money solely because a client observation arrived. Read secure events and the official baseevents documentation before integrating an installed version. Test death, aborted entry, successful entry/exit, disconnect and resource restart separately on a development server.