Guard Frequency Episode 056 | Steal or No Steal

Comments

6 responses to “Guard Frequency Episode 056 | Steal or No Steal”

1. 

   Dillek

   January 27, 2015

   Great show! Love it, even if you are not the first during the week.

   TIME COMPRESSION! It has been stated that 2 hours of real time will be 1 day in the ‘verse. That will be the reason that we are able to travel so fast with .2c. I know, some people aren’t fans of time compression but… What if you lose your ship and Insurance tells you it will take 3 days to get it back? Would you wait 3 real days or six hours? Your call…

   Have a great week!

   Reply
2. 

   Amontillado

   January 28, 2015

   Fairly new listener here. Great podcast! 🙂

   I’m absolutely fine with the notion of thrusters, quantum drives, and jump drives. I don’t really see the need for mini jump points or the value in fretting over the actual speed of light or real distances of various celestial objects from one another.

   My favorite take away from the PAX South Townhalls? It may seem silly, but it’s the revelation that we will have some variance in body types for our characters. I was afraid it would be facial and clothing customization only. I’m very glad to learn that we can make some adjustments to the bodies as well.

   Now what would make me even happier is if these body masses were taken into consideration for things like equipment carrying, combat (hand to hand and ranged), and the dragging of wounded comrades.

   Thanks for your efforts GF crew!

   Reply
   1. 

      Justin Lowmaster

      January 28, 2015

      I think we will pronounce your name right when we read this on the show … or I’ll have a cask of wine to show someone … down here … {;0)

      Thanks for the feedback! I tend to agree, as well.

      Reply
3. 

   Knix

   January 29, 2015

   I say keep both mini jump points and quantum drives, though why call them mini jump points? I’ve always thought that the game needs more jump points. More jump points for us to map is good. What’s to say that a jump point can’t lead to another location in the same system? I think jump points should have semi random destinations, with a higher probability for the destination to be close to the jump point. Jump points should tend to be “attracted” by gravity to increase the chance of them going someplace interesting. Shorter jumps should be easier to find and easier to map. This way you could have several short jumps within scanner range you could go to within a few minutes of travel at 0.2c without having to resort to time or space compression. A good scanner could also give you a rough estimate of the distance and direction a jump point will take you even at long range to give you an opportunity to steer your travels in roughly the direction you want to go.

   Reply
4. 

   seannewboy

   January 29, 2015

   Wonderful show everyone, trying hard to resist the urge to settle for the aurora lx package on sale right now.

   Reply
5. 

   Ostron

   January 30, 2015

   How about we just take it as read that you guys made a great show and I’ll stop mentioning it.

   Dillek beat me to it, but I wanted to reiterate his point: the time compression thing explains the .2c = 10 minutes across the solar system issue. I liked Chris’ description of the intrasystem travel mechanic.
   And I’m going there: I DON”T like the mini-jump point system idea. I think it would either create artificial choke points in systems that would severely limit the ability of an “explorer” profession to exist, or the entry range and pervasiveness of such jump points would have to be so expansive as to make the distinction between that and a BSG-esqe “insta jump drive” academic.

   I haven’t had a chance to watch all of them yet, but I liked the description of the mining mechanic; it’s more in-depth than anything we’ve seen or heard so far, and it very nicely illustrated how something like mining could be interesting and/or dangerous apart from “hey you’re under attack…and you happened to be mining!”

   Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.