Traveller Store CotI Features New Posts Mark Forums Read Register


Go Back TravellerRPG.com > Citizens of the Imperium > General Traveller Discussions > Software Solutions

Software Solutions Discussions on Traveller related software.

Reply
 
Thread Tools Display Modes
  #61  
Old January 16th, 2013, 07:59 PM
Enoki Enoki is offline
Citizen: SOC-14
 
Join Date: Nov 2010
Posts: 1,764
Gallery : 29
Enoki Citizen++Enoki Citizen++Enoki Citizen++Enoki Citizen++
Default

Question: In terms of the game and a scenario where does this play a major role in one?
Reply With Quote
  #62  
Old January 16th, 2013, 08:39 PM
aramis's Avatar
aramis aramis is offline
Administrator
 
Join Date: May 2001
Location: Anchorage, AK, USofA
Posts: 29,420
Gallery : 56
Visit aramis's Blog
aramis has disabled reputation
Send a message via ICQ to aramis Send a message via AIM to aramis Send a message via Yahoo to aramis
Default

Quote:
Originally Posted by Enoki View Post
Question: In terms of the game and a scenario where does this play a major role in one?
If you use both the complex motion tracking, and the 100 diameter limits of stars, and T5 style jump line interference (any crossing of any 100 diameter limit at any point in the week drops you at the closest 100 diameter limit intersection to your origin point that your jumpline crossed), it means that at least* 1/10th of the time, mainworld to mainworld travel is blocked by a star at one end, resulting in an addition 0.5-2 weeks travel time at either end.

Taking, for example, CT/MGT's [Aramis:] The Traveller Adventure (TTA)... your choice of systems to travel to along the Aramis Trace is much more limited than may orignaly appear.

You can approximate it by, for a given system, rolling an initial setup. Let's presume for the moment all systems are G0-G5 class Size V stars (simply to make the math easier) and block 1 hex-side.

Take this small sample of space.
Code:
   \_____/       \_____/       \_____/ 
   /     \       /     \       /     \ 
__/   o   \_____/   o   \_____/       \
  \       /     \       /     \       /
   \_____/   o   \_____/   o   \_____/ 
   /     \       /     \       /     \ 
__/       \_____/       \_____/   o   \
  \       /     \       /     \       /
   \_____/   o   \_____/       \_____/ 
   /     \       /     \       /     \ 
__/   o   \_____/       \_____/   o   \
  \       /     \       /     \       /
   \_____/   o   \_____/   o   \_____/ 
   /     \       /     \       /     \ 
__/       \_____/       \_____/       \


I'll roll the blockages... Doubles indicate blocks
Code:
   \_____/       \_____/       \_____/ 
   /     \       /     \       /     \ 
__/   o   \_____/   o   \_____/       \
  \      //    \\       /     \       /
   \____//   o  \\_===_/   o   \_____/ 
   /     \       /     \       /     \ 
__/       \_____/       \_===_/   o   \
  \       /     \       /     \\      /
   \_____/   o   \_____/       \\____/ 
   /    \\      //     \       /     \ 
__/   o  \\____//       \_____/   o   \
  \       /     \       /    \\      //
   \_____/   o   \_____/   o  \\____// 
   /     \      //     \       /     \ 
__/       \____//       \_____/       \

This was in fact random rolled.
You'll notice that J1 traffic no longer can treat this as a J1 main. Sure, J1 can get there, but it means having to treat it for finances as 1.5 to 2 jumps worth of travel time. It means financial breaks.

2 months later...
Code:

   \_____/       \_____/       \_____/ 
   /     \       /     \       /     \ 
__/   o   \_____/   o   \_____/       \
  \       /     \\      /     \       /
   \_===_/   o   \\____/   o   \_____/ 
   /     \      //     \\      //    \ 
__/       \____//       \\____//  o   \
  \       /     \       /     \       /
   \_____/   o   \_____/       \ ____/ 
   /     \       /     \       /     \ 
__/   o   \_===_/       \_____/   o   \
  \      //     \       /     \       /
   \____//   o   \_____/   o   \_===_/ 
   /     \       /     \      //     \ 
__/       \_===_/       \____//       \
You'll note that this means up to a 4 month gap for a given world. Truth is, it should be more.



-=-=-=-=-=-=-=-=-=-
* Noting that for a main sequence star in the G range, and mainworlds being preferentially in the habitable zone, it's going to be a hair over 1/6 of the time for a 3D universe, and 1/4 of the time for a 2D one. Small but bright massive stars could cover less.
__________________
~ Aramis
aramis.hostman.us /trav
Smith & Wesson: The Original Point and Click interface!

Archduke of Sylea (CORE 2118)
Duke of the Third Imperium (SPIN 0534)
Count Terra (SOLO 1827)
Count Gorod (REFT 1302)
Count of the Third Imperium (SPIN 2232)
Viscount of Adabicci (SPIN 1824)
Marquis of the Solomani Rim (SOLO 0606)
Marquis of the Third Imperium (SPIN 2410)
Baron of the Third Imperium (SPIN 2231)
Knight of the Iridium Throne (CORE 1434)
Sir William Hostman (OLDE 0512)
Sir William Hostman (DAGU 0622)
Knight of Deneb (REFT 2239)
Knight of Deneb (Spin 2532)
SEH w/Diamonds for Extreme Heroism - Battle of Boughene
MCG - Battle of Boughene
TAS: William Hostman (CORR 2506)
TAS: Bearer (DAIB 1326)
IMTU ct+ tm++ tne tg-- tt+ tmo+ t4- t20+ to ru+ ge+ 3i+ c+ jt au ls pi+ ta he+ st+
Wil Hostman 0602 C539857-9 S A724
OTU: 95% 3i an+ au+ br- cpu± dt± f+ fs++ ge± ih- inf± j± jf+ jm+ jt+ ls- n= nc+ pi+ pp-- tp+ tr+ tv- vi-- xb+-
Unless there is bold red text, presume my posts to be my personal material only.
Reply With Quote
  #63  
Old January 16th, 2013, 11:38 PM
whartung whartung is offline
Citizen: SOC-14
 
Join Date: Nov 2004
Posts: 2,591
Gallery : 0
whartung Citizen+whartung Citizen+whartung Citizen+
Default

That's a great way to model this pretty simply. Block a hex side randomly, every 2 months the block moves clockwise. To calculate the time, draw a line from hex A to hex B, if the path crosses a blocked hex side in either the source and/or destination hex, add N time to the trip (thus if you cross blocks on both hexes, it's 2N).

The problem isn't solely the delay in travel. The problem is the economic system and fees (as mentioned in the rules) do not take absolute travel time in to account. Because, again, it's not like these blockages are a "surprise". It's not a "Oh my gosh, a sudden space storm". It's a predictable, seasonal "truth" about travel.

It's actually an interesting dimension to the speculative trade game, as it gives another decision point as to whether to visit a system or not.
Reply With Quote
  #64  
Old January 16th, 2013, 11:51 PM
aramis's Avatar
aramis aramis is offline
Administrator
 
Join Date: May 2001
Location: Anchorage, AK, USofA
Posts: 29,420
Gallery : 56
Visit aramis's Blog
aramis has disabled reputation
Send a message via ICQ to aramis Send a message via AIM to aramis Send a message via Yahoo to aramis
Default

Quote:
Originally Posted by whartung View Post
That's a great way to model this pretty simply. Block a hex side randomly, every 2 months the block moves clockwise. To calculate the time, draw a line from hex A to hex B, if the path crosses a blocked hex side in either the source and/or destination hex, add N time to the trip (thus if you cross blocks on both hexes, it's 2N).
Actually, the intervening systems are so unlikely to matter as to be ignorable. All you need to look at is if the two end systems are blocked from each other. And if they happen to block, they will permanently block on the timescales involved.
__________________
~ Aramis
aramis.hostman.us /trav
Smith & Wesson: The Original Point and Click interface!

Archduke of Sylea (CORE 2118)
Duke of the Third Imperium (SPIN 0534)
Count Terra (SOLO 1827)
Count Gorod (REFT 1302)
Count of the Third Imperium (SPIN 2232)
Viscount of Adabicci (SPIN 1824)
Marquis of the Solomani Rim (SOLO 0606)
Marquis of the Third Imperium (SPIN 2410)
Baron of the Third Imperium (SPIN 2231)
Knight of the Iridium Throne (CORE 1434)
Sir William Hostman (OLDE 0512)
Sir William Hostman (DAGU 0622)
Knight of Deneb (REFT 2239)
Knight of Deneb (Spin 2532)
SEH w/Diamonds for Extreme Heroism - Battle of Boughene
MCG - Battle of Boughene
TAS: William Hostman (CORR 2506)
TAS: Bearer (DAIB 1326)
IMTU ct+ tm++ tne tg-- tt+ tmo+ t4- t20+ to ru+ ge+ 3i+ c+ jt au ls pi+ ta he+ st+
Wil Hostman 0602 C539857-9 S A724
OTU: 95% 3i an+ au+ br- cpu± dt± f+ fs++ ge± ih- inf± j± jf+ jm+ jt+ ls- n= nc+ pi+ pp-- tp+ tr+ tv- vi-- xb+-
Unless there is bold red text, presume my posts to be my personal material only.
Reply With Quote
  #65  
Old January 17th, 2013, 09:24 AM
whartung whartung is offline
Citizen: SOC-14
 
Join Date: Nov 2004
Posts: 2,591
Gallery : 0
whartung Citizen+whartung Citizen+whartung Citizen+
Default

Quote:
Originally Posted by aramis View Post
Actually, the intervening systems are so unlikely to matter as to be ignorable. All you need to look at is if the two end systems are blocked from each other. And if they happen to block, they will permanently block on the timescales involved.
I mentioned to take in to account only the source and destination systems.

The blocks aren't permanent as they're based on the orbital positions of the planets, which "change every month", that's why I suggested moving the blocks 1 hex side every two months.

It hand waves away different orbital speeds, but odds are for habitable worlds around G stars, their years will be close enough that the timings of the hex side blocks will likely not really change for 5 or 10 years.
Reply With Quote
  #66  
Old January 18th, 2013, 05:25 AM
DangerousThing DangerousThing is offline
Citizen: SOC-13
 
Join Date: Aug 2011
Posts: 721
Gallery : 0
DangerousThing Citizen
Default

Quote:
Originally Posted by Enoki View Post
Question: In terms of the game and a scenario where does this play a major role in one?
This is mainly for my private use, because as a GM I like to be consistant within the reality of the game. I was hoping that somebody else had written it, but I can do it.

Unfortunately the simplifying assumptions don't work all that well. Planets in the life zone may have radically differently timed orbits. I just want to be consistent for my players. However, since the time I asked the question and now, I have changed the drive assumptions for the campaign and no longer need worry about this.

Thanks much all, it has been an interesting discussion.
__________________
A little learning is a dangerous thing.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Blank sector map? skyth Software Solutions 7 February 13th, 2009 11:14 PM
sector map - known space Malenfant The Lone Star 2 February 27th, 2004 02:27 PM
Ley Sector Map AndreaV T20 - Traveller for the D20 System 24 September 30th, 2002 10:04 AM

This website and its contents are copyright ©2010- Far Future Enterprises. All rights reserved. Traveller is a registered trademark of Far Future Enterprises .
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2010-2013, Far Future Enterprises. All Rights Reserved.