Skip to content

ControlPlay v2.6.24-beta.4 (Beta)

Pre-release
Pre-release

Choose a tag to compare

@bubbinga bubbinga released this 22 Sep 18:35
Immutable release. Only release title and notes can be modified.
f3d9589

Was ist neu in v2.6.24-beta.4

Added

  • A new, paired connection for the Stream Deck plugin (protocol 3): Until now the plugin identified itself with a fixed name that any program on the PC could send. The app now also speaks a new protocol on the same port in which a plugin has to be paired first and then proves on every connection that it knows the shared secret, without ever sending it. A plugin on the same PC pairs by itself through a file only your Windows account can read; if that protection cannot be set up, the file is not written at all. The plugin you have installed today keeps working unchanged. Once a plugin that speaks the new protocol has connected, older plugins are turned away for the rest of that session, and a new switch lets you turn them off for good. The plugin version that uses all of this follows separately.
  • Trigger from the Stream Deck: The app is ready for keys that trigger game actions, sounds, overlay effects and voice effects. A key press takes exactly the path a viewer's redemption takes — the same window-focus guard, the same Do Not Disturb rules, the same hardware checks — only without Bits and without a viewer notification. Cooldowns are respected in both directions: a key is locked for as long as the viewers' button is, including group and profile cooldowns and the shared overlay cooldown, and the key is told the moment a cooldown ends. A key that would be refused is shown as unavailable with the reason a press would give. A voice key switches an effect on until you press again, never cuts off a viewer's effect in its protected second half, and can only switch off what it switched on itself. One switch turns all triggering from the deck off.
  • Stream Deck on another PC (Dual-PC): A new opt-in lets the plugin on your streaming PC reach ControlPlay on your gaming PC over your home network. It is off by default, and while it is off nothing changed: the connection stays reachable from your own PC only. When you turn it on, only devices in the same home network are accepted — or exactly one PC, if you name it — older plugins are never spoken to over the network, pairing needs a 12-character code that is valid for two minutes and five attempts, and every message of a network connection is sealed against tampering and replay. Repeated failed attempts lock a device out for fifteen minutes. Windows Firewall still has to let the connection in: the settings page gives you the command to copy, under its own rule name so that it never replaces the overlay rule. Uninstalling ControlPlay does not remove that rule yet; the page tells you how to.
  • A plugin section on the Stream Deck settings page: the three switches above, the address to enter on the streaming PC, the pairing code, and the list of paired plugins with a way to remove one or reset all. Your screen is on stream, so the pairing code stays hidden until you ask for it, and the page only ever shows home-network addresses — never your public one. In all 14 languages.

Changed

  • ControlPlay no longer opens your Stream Deck at every start: The app connected directly to the first Stream Deck it found on every launch, although nothing in the app uses a directly connected deck, and on a single PC that competes with the Elgato software the ControlPlay plugin runs in. This is now a switch on the Stream Deck settings page and it is off by default. If you relied on the old behaviour, turn "Connect the Stream Deck directly at start" on; connecting by hand from that page works either way.

Fixed

  • A game action's cooldown now holds for exactly the cooldown you set — no shorter, no longer: the app's own duplicate guard kept a mark per action but dropped it on rules left over from an older per-trigger design. Two consequences: a periodic clean-up dropped every mark older than 5 seconds, so any cooldown above 5 seconds really lasted only 5 to 35 seconds before a second trigger of the same action went through; and the timer that cleared a mark was started only when the run ended, so it fired one cooldown after the end of the run — a macro with delays could thereby erase the mark of a newer run that had started meanwhile. The mark is now held per game and action for exactly the configured cooldown, counted from the start of the run; a second trigger inside it is refused with the remaining seconds. Also: a cooldown edited while it is running keeps the end already set (the Stream Deck key shows that same end); the same action id in another game is not on cooldown; the app no longer starts a timer for every run.
  • A game action that did not run to completion no longer blocks its own retry: when an action was refused because the game window was not active, the board reported an error, or a macro was cut short, the app still treated it as "recently executed" until its periodic clean-up came round — up to 35 seconds (never longer than the action's own cooldown) in which every retry of that action by a viewer was answered with a cooldown although the action had not run to completion. A failed action is now forgotten at once; a completed one holds its cooldown as described above.

Security

  • The Stream Deck connection is now reachable only from your own PC: The local service the Stream Deck plugin talks to listened on every network interface, so any device on the same network could reach it, and it trusted a fixed name that any program could send. It now accepts connections only from this computer, over both address families your system uses for "localhost", and turns away any connection that carries a web-page origin. Nothing about the plugin's own messages changed, so an installed Stream Deck plugin keeps working exactly as before.
  • A crafted name from the Stream Deck channel can no longer run code inside the app: Values that arrived over that channel — a game id, an effect id, an on/off flag — were pasted straight into a script the app runs against its own interface, so a specially built name could have executed arbitrary code in the app. Every such value is now passed as data, never as code, and on/off is always read as a plain yes or no. There is also now an upper limit on how large a single incoming message may be.
  • Tighter limits on that same local channel: at most eight connections may wait for authentication at a time, repeated error logs collapse to one line per half minute, an unknown request is answered with a fixed text instead of an echo of what was sent, the icon request limit now counts per connection (and as one shared budget of 100 per minute for requests relayed through the ControlPlay cloud session, where it was never effective before), no raw request is written to the log any more, and an on/off request is confirmed back exactly as it was applied.
  • A turned-away connection could no longer end the app (found in 2.6.24-beta.1): when a ninth local connection was refused because eight were already waiting, the app stopped listening to it before the refusal had gone through — a malformed frame sent in that moment would have closed ControlPlay with an error box. Refused connections are now watched until they are gone, and a connection that ignores the refusal is cut off after one second instead of being kept for thirty. Only a program on your own PC could have triggered this.

The virtual-microphone driver is unchanged in this release: 2.6.24 ships the same Microsoft-attested driver package as 2.6.23.


📥 Installation

  • Windows: Lade ControlPlay-Setup.exe herunter (signiert mit EV-Zertifikat, Zertifikat-SimpleName: KOKOLIO GMBH; juristische Person: KOKOLIO GmbH)