What supports of Robo get as subscribers...

• They can play in more than one game at a time.
• Their vote on a RoboIssue carries double weight.
• They are eligible for rank advancement.
• They get posted to the player page.
• They get an individual page for themselves.
• They can use their NickName as a psuedo EMail address at Robomaster.Com
• They can use the RoboCyph encryption program to secure their web posted RST files.
• They can call for time-outs to delay game execution.
• They are virtually immume to the "3 strikes and you're out rule". (This has been slightly modified over the years from immume, to virtually immune, to reststant. Currently subscribers get 6 strikes. I'm considering a more complicated formula based on Karma). There were too many games ruined by 19+ missed TRNs.
• They can customize their psuedo Email address.
• They get a file detailing exactly what each ship and planet contributes to their RoboScore.
• Their mine sweeping messages are summarized in a game message using Robo's MINEMSGS utility.
• Robo will wait for late TRNs if he does not have enough TRN files from subscribers.
  

  Code fragment:
  
  PctInPaid: procedure expose g.
  arg i .
  
  GT = g.i.!goodPAIDTRNs
  DD = g.i.!datedue
  IP = g.i.!ImPatience
  PH = g.i.!PAIDhumans
  PV = g.i.!PAIDvacations
  AD = max(0,(makedate()-DD)) * IP
  
  return (100*(GT + AD)) / (PH-PV)
  
  ...
      if ... (PctInPaid(i) >= g.i.!mingood) ...
  
  Where '...' represents code that has been trimmed.
  
  

There may be more, and I'll update this is as they occur or are created. [an error occurred while processing this directive]