What would you like to see?
Add a managed wrapper and registry for placed native air conditioners.
The first version should expose:
- current mode through an S1API-owned
AirConditionerMode enum;
- the existing wrapped
TemperatureEmitter associated with the unit;
- position/GameObject access and discovery of active units;
- a managed mode-changed event;
- safe server-authoritative operations for off, cooling, heating, and selecting a mode.
Why would this help?
The temperature API delivered in #237 makes emitters and world-temperature queries reusable, but mods still need native ScheduleOne.Temperature.AirConditioner and its network methods to inspect or control the furniture that drives those emitters. A supported wrapper would enable HVAC controls, automation, custom furniture integrations, and temperature UI on Mono and IL2CPP.
Extra Context (Optional)
Keep the initial API limited to existing placed air conditioners and native temperature behavior. Custom HVAC simulation, custom replication, replacement UI, and custom air-conditioner prefab authoring should remain out of scope.
Validate discovery, mode transitions, event timing, host/client authority, scene reload, and stale-wrapper cleanup separately on Mono and IL2CPP.
What would you like to see?
Add a managed wrapper and registry for placed native air conditioners.
The first version should expose:
AirConditionerModeenum;TemperatureEmitterassociated with the unit;Why would this help?
The temperature API delivered in #237 makes emitters and world-temperature queries reusable, but mods still need native
ScheduleOne.Temperature.AirConditionerand its network methods to inspect or control the furniture that drives those emitters. A supported wrapper would enable HVAC controls, automation, custom furniture integrations, and temperature UI on Mono and IL2CPP.Extra Context (Optional)
Keep the initial API limited to existing placed air conditioners and native temperature behavior. Custom HVAC simulation, custom replication, replacement UI, and custom air-conditioner prefab authoring should remain out of scope.
Validate discovery, mode transitions, event timing, host/client authority, scene reload, and stale-wrapper cleanup separately on Mono and IL2CPP.