INTERLOPE command

  • Typical usage: get s.interlope.pull:27015
    • Faulty "INTERLOPE" command is required
    • Message replies
      • getting socket for s.interlope.pull...
      • extracting data from terminal
      • submitting envelope
      • received
      • request from archive submitted
      • message from server administrator : CONGRATULATIONS AND WELCOME PLEASE ENTER WITH CAUTION YOU ARE NOT WELCOME HERE
    • GET command creates a data.dem demo file (additional demos increment)
      • Demos sometime save custom maps as data.bsp
    • Demo plays immediately
    • Worked briefly during IL1, then stopped working at 6 AM. Commands exit with no response.
  • Eida's removed commands (removed 2012?)
    • get s.interlope.pull:27016
    • connect s.interlope.pop:27015
    • send test.dme Mechanics/DME
    • Could be the mechanism used to generate demos on specific (custom) maps
  • Tuesday Manifest
    • New commands logged in SFM sessions
      • com_pull_request
      • hook s.interlope.pull:27016 is noted as a back door
] INTERLOPE
Unknown Command: INTERLOPE
] get s.interlope.pull:27015

This isn't valve ConCommand syntax, instead seems reminiscent of property access.

#theory s.interlope.pull represents a hierarchy of objects: s (sourcebox?) > interlope (The Interloper?) > pull (pull function called with a port argument)
Anomi knows what concommands look like and chose this to communicate something specific

Have Mechanics/Commit Numbers

In ILD Anomi speculates that it may have been affected/broken by the HL2 20th anniversary update, but this seems to have been a red herring.

We know demos must be recordings because we've had repeats