Add a Run/Debug config to launch DreamDaemon and DreamSeeker together

[Inorien]

N̶o̶ ̶I̶ ̶d̶i̶d̶ ̶n̶o̶t̶ ̶s̶p̶e̶n̶d̶ ̶t̶w̶o̶ ̶h̶o̶u̶r̶s̶ ̶f̶u̶c̶k̶i̶n̶g̶ ̶a̶r̶o̶u̶n̶d̶ ̶w̶i̶t̶h̶ ̶p̶o̶w̶e̶r̶s̶h̶e̶l̶l̶ ̶a̶n̶d̶ ̶b̶a̶t̶c̶h̶ ̶s̶c̶r̶i̶p̶t̶s̶ ̶a̶n̶d̶ ̶o̶t̶h̶e̶r̶ ̶j̶s̶o̶n̶ ̶a̶n̶d̶ ̶p̶o̶r̶t̶s̶ ̶o̶n̶ ̶m̶y̶ ̶m̶a̶c̶h̶i̶n̶e̶ ̶t̶o̶ ̶d̶o̶ ̶i̶t̶ ̶a̶n̶ ̶i̶n̶c̶r̶e̶d̶i̶b̶l̶y̶ ̶r̶e̶t̶a̶r̶d̶e̶d̶ ̶w̶a̶y̶ ̶b̶e̶f̶o̶r̶e̶ ̶I̶ ̶d̶i̶d̶ ̶i̶t̶ ̶t̶h̶i̶s̶ ̶w̶a̶y̶ (it ended up being four)
APPARENTLY IT WAS WORTH IT IN THE END

themostpregnantman.mp4

There was a lot of fucking around to get here. Problems encountered:

• In the initial try, DreamSeeker was starting independent of DreamDaemon and didnt actually connect
• In the second try, DreamSeeker actually waited for DreamDaemon to finish building and launch before launching itself, but still wasn't connecting to it due to how the VSCode Byond plugin works
• In the third try, it just fuckin worked on the very first attempt

What it does

Adds a Run/Debug config to VSCode so you can just slam F5 and it will launch both DreamDaemon and DreamSeeker together

Initial attempt DreamSeeker wasnt waiting for DreamDaemon, Dilt spotted it so now theres a blocking powershell script that:

• scans for DreamDaemon.exe or dd.exe process
• gets its port
• pings it until it responds
• launches DreamSeeker at the found DreamDaemon instance

Why its good

saves valuable development time

Changelog

No user-facing change

[Inorien]

wait fuck this doesnt work properly yet

[Inorien]

pregnant man emoji

[Inorien]

this is embarassing

[CrazyAmphibian]

does it work on linux?

[Inorien]

if you can run powershell scripts then yes
if not then youll have to write something to find the server process and get its listen port, should be a trivial bash script
and also adapt the task to use that

[Inorien]

DNM for a bit while i figure out an issue reported by west where it doesnt seem to ever launch dreamdaemon