Skip to content

SlotForge Paddock v0.20.0 - One remembered Dealership password and faster saves

Choose a tag to compare

@theDutchmanJames theDutchmanJames released this 01 Nov 12:48

SlotForge Paddock v0.20.0

One remembered Dealership password, simpler connections, and faster saves.

Dealership Mode

  • One password for Paddock and Timing. Choose a password of 4–128 characters. It grants browsing, submissions for review, private Paddock replication and Timing results access. No separate Timing password or results-enable switch is needed in Dealership Mode.
  • Remembered connections. The dealership computer keeps its password across hosting and app restarts. Connected Paddock copies remember their password too. Changing it revokes the old password.
  • Independent controls. The Dealership card has its own setup, start, stop and password controls. Legacy sharing controls are hidden and legacy credentials are inactive while hosting a Dealership.
  • Review stays in place. Proposed car and parts edits still need approval on the dealership computer. Results finalized in Timing are stored directly, then distributed to connected copies.

Faster saves and submissions

Unchanged photos reuse their validated JSON encodings, and small saves send only changed data back to the interface. In three alternating local benchmark runs with a 27 MiB collection, median workshop saves fell from 151 to 84 ms, submissions from 487 to 185 ms, and approvals from 388 to 147 ms. Desktop save responses were around 15 KB instead of resending the photo collection. Actual speed depends on the computer, storage and collection; initial downloads and large writes can still take time.

Updating and Timing compatibility

Existing Dealership installations first need to choose Set password… in Connections, then Start Dealership. Use that same password and the displayed address/port in both apps. The password survives restarts; the host may still choose a different port.

Timing currently accepts passwords of 8–128 characters. Use at least eight characters until Timing updates its minimum to four. Its existing car browsing and results protocol already works with the unified Dealership password. The included handoff explains the small validation and wording update. Timing source is not changed by this release.

Database schema 11 and Timing integration v1 are unchanged. Keep a complete backup before updating; v0.18.x and older cannot read schema-11 saves. Passwords are local device settings and are not included in collection backups or replication. Legacy sharing outside Dealership Mode retains its separate temporary credentials.

Downloads

  • Windows: SlotForge.Paddock.0.20.0.exe — close the previous copy, then run this portable app. Node.js is not required.
  • Linux: x64 and ARM64 AppImage/deb packages, attached by the native build jobs.
  • macOS: universal DMG/ZIP for Intel and Apple Silicon, attached by the native build job.
  • Integration: SlotForge-Paddock-Timing-v1.zip contains the updated contract, guide and fixtures.

SHA-256 manifests accompany the downloads. Windows is unsigned; macOS is ad-hoc signed and not Apple-notarised. AppImages need executable permission.

Validation

335 automated tests and 188 isolated desktop checks passed, with no captured renderer errors. Tests cover password persistence, revocation, failed-save rollback, unified Timing access, queued retries, review, corrections and withdrawals. Testing used temporary collections and local HTTP connections, not user data or a new physical two-computer Wi-Fi test.

See the Dealership guide and Timing handoff.