Module 08 · Lesson 25

Cleanup discipline

Spawning is easy. Cleaning up is the part that separates scripts that work from scripts that destroy servers. If you spawn entities and never delete them, the world fills with ghost objects, entity counts climb, and the server lags or crashes. This lesson teaches the three moments cleanup has to happen, and why one of them cannot be done from the client at all.

You'll ship: Cleanup handlers for resource stop, player drop, and timed auto-delete.
Time: ~25 minutes
You'll learn: Signs of entity leaks, cleanup on resource stop, cleanup on player drop, timeout auto-delete, and why the drop path has to live on the server.
Prereqs: Lesson 24 (spawning entities, the registry pattern).

BEFORE YOU START

Build it

Make the resource folder

The server has one folder for this lesson.

Inside your server's resources folder, create this folder:

code

resources/qu_cleanup_discipline

Create the files

Every file named in the manifest exists.

Create this exact file layout. Note the new server.lua compared to Lesson 24:

Cleanup discipline

Build it

Make the resource folder

Create the files

Write fxmanifest.lua

Write the client code

Write the server code

Start and test it

Keep reading the full lesson