AddPluginManager
This compatibility method behaves like AddPlugins. Adds a plugin manager for local, inline, prebuilt, or approved remote plugins. It is kept so scripts written with the older AddPluginManager name continue to work.
AddPluginManager
Compatibility alias
AddPluginManager is an alternate name for AddPlugins. New code can use AddPlugins.
What it does
This compatibility method behaves like AddPlugins. Adds a plugin manager for local, inline, prebuilt, or approved remote plugins. It is kept so scripts written with the older AddPluginManager name continue to work.
When to use it
Use it when your hub exposes optional modules and needs a user-facing way to load or manage them. Prefer AddPlugins in new code so the method name matches the current API.
ElementFunction:AddPluginManager(PluginConfig)
local Result = Section:AddPluginManager({
Name = "Example",
})Behavior and return value
This alias forwards to AddPlugins, so its options, callbacks, and returned value follow the canonical method.
Fields marked optional may be omitted. XLQP then uses the method’s built-in default or leaves that feature disabled.
Related reference
AddPlayerCard
This compatibility method behaves like AddPlayerVisualizer. Adds a visual player preview with optional overlay boxes and live coloring. It is kept so scripts written with the older AddPlayerCard name continue to work.
AddProgress
This compatibility method behaves like CreateProgress. Creates a controller-driven progress element with optional saving and callback behavior. It is kept so scripts written with the older AddProgress name continue to work.