Initialise services and modules
Avoid circular dependencies and race conditions in your startup sequence.
Separate setup from running#
Load modules, supply their dependencies, then start listeners and loops. Keep top-level module code small. Avoid a module waiting for another module that is waiting for the first one.
Wait for replicated dependencies#
A client can start before a server-created instance arrives. Use WaitForChild when the instance is expected to replicate, and handle timeouts where an optional system may be absent. A missing instance is not solved by adding arbitrary long waits everywhere.
Using Knit or another framework#
BLOXG AI does not ship a fork of another company’s framework. If your project already uses Knit, preserve that project’s version and lifecycle conventions and include them in your context bundle. The built-in starters use Roblox services directly, so no third-party framework install is required.