Documentation
Optional Addon

Vcore-windowcleaning

Vcore-windowcleaning is part of Vcore Framework.

Introduction

Vcore-windowcleaning is part of Vcore Framework.

Version: 1.0.0Optional Resource4 Lua files0 SQL files

Dependencies

DependencyStatus
coreIncluded Vcore resource

Installation / Start Order

Install the resource with its required dependencies, then enable it in your resource start order.

server.cfg
ensure windowcleaning

Configuration

Config files

  • config.lua

Detected config keys

  • AdminCommand
  • AdminPermission
  • CleanAnim
  • CleanDuration
  • CleanMinigameTarget
  • CleanMinigameTime
  • CleanerOutfit
  • HQ
  • HQBlip
  • HQPed
  • HamperModel
  • HamperStep
  • HandleModel
  • Locations.DutyToggle
  • MoneyType
  • NotifyLength
  • PayPerWindow
  • Sites
  • SpawnPoint
  • Van

Events & Exports

Exports

No exports are documented for this resource.

Callbacks

servervcore-windowcleaning:server:clockOff

Callback available from this resource. Confirm parameters and return values before using it.

servervcore-windowcleaning:server:clockOn

Callback available from this resource. Confirm parameters and return values before using it.

servervcore-windowcleaning:server:startSite

Callback available from this resource. Confirm parameters and return values before using it.

servervcore-windowcleaning:server:windowCleaned

Callback available from this resource. Confirm parameters and return values before using it.

Registered network events

clientvcore-windowcleaning:client:notify

Registered event for this resource. Confirm the expected payload and intended scope before using it.

Commands

No registered commands were detected.

Database / SQL

SQL files

None detected in source.

Detected tables

None detected in source.

Troubleshooting

  • Confirm every manifest dependency above is started first.
  • Import the SQL where the resource includes database files.
  • Use the exact resource folder name shown on this page unless you intentionally change both the folder and configuration.
  • Do not copy internal event names into integrations without checking their implementation.