vwemirror/SiteLink
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
3 Commits 1 Branch 0 Tags
d373e3c1d341bf90c77df2aa2a07dba2bdd10354
Commit Graph
3 Commits
Author SHA1 Message Date
CydandClaude Fable 5 d373e3c1d3 Add TeslaRel410 (original 4.10 games under DOSBox-X emulation) 
- Ecosystem doc: new section on the TeslaRel410 project — custom
  DOSBox-X fork HLE-emulating the Division VPX board to run the
  original, unmodified Tesla 4.10 BattleTech/Red Planet DOS binaries
  on current Windows 10 pod hardware (RIO COM1 / plasma COM2
  passthrough). Networking facts for SiteLink: WATTCP (real TCP/IP)
  via NetNub over emulated NE2000 bridged by pcap -> routable in
  principle; BOOTP is broadcast -> site-local provisioning.
- Clarified BT411 and RP411 as the two native Win32 Tesla 4.10
  reconstructions (per operator), complementary to the emulation path.
- Brainstorm: new game-linking subsection for the emulated originals +
  open question 11 (NetNub cross-subnet addressing, 30 Hz sim latency
  tolerance).
- CTCL naming note: provenance question is out with VWE veterans.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-10 11:09:34 -05:00
CydandClaude Fable 5 88caa81e04 Correct CTCL description: acronym expansion is inference, not attested 
Searched the firestorm tree for an authoritative expansion of "CTCL" and
found none. Replaced the guessed "cafe/Tesla control layer" wording with
the attested facts (Console 2 Launcher message comments, _ECTCL_Console/
_ECTCL_Launcher roles, Tesla-centric coin-op API) and flagged the reading
"Console-Tesla Control Layer" as inference. New facts from the dig: CTCL
is game-agnostic (_EAT_MW4/_EAT_RP) and has its own ports 1000/1001,
added to the port map.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-10 11:05:25 -05:00
CydandClaude Fable 5 7ebcb0f0ab Initial brainstorm record: linking Pod Bays across the internet 
- README: project charter + seed concept (per-site 10.0.y.0/24 subnets,
  VPN into one /16, merged siteconfigs -> master console)
- docs/PODBAY-ECOSYSTEM: survey of the existing bay stack with source
  pointers (TeslaSuite RPC 53290, Firestorm DirectPlay 4 + CTCL, BT411
  console/egg protocol, RP Munga 1501, PQS, port map)
- docs/BRAINSTORM: addressing plan, routed-L3 vs bridged-L2 analysis,
  master console vs federation, per-game linking, shared services,
  security posture, open questions, phased roadmap
- sites/: site-ID / subnet registry (public info only)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
 2026-07-10 10:31:34 -05:00