far-trader
SOC-14 10K
And what approach would that be? That before one discards a piece of canon, one tries to come up with a reasonable explanation for seeming inconsistencies, and only if that is not possible does one change it (and then cahnge it as little as possible to make it fit). I'm pretty sure that the original is dated as sent off on 142-1111. But even if it was 142-1112 in the original issue of Challenge, it seems a pretty reasonable assumption that it was supposed to be 142-1111.</font>[/QUOTE]Certainly that's been my approach, but from your post suggesting we ponder the implications of three canonical dispatches I got the distinct impression you were suggesting we need to infer that the only solution is J6 couriers. You didn't mention btw in that post that you presumed to edit the year of the one I pointed out. The way I noted that was largely for comic effect. I was just using the information you pointed us to. Obviously, yes the writers meant 142-1111, correct or not in any other way, I am certain they did not intend the travel time for that message to be zero.Originally posted by rancke:
</font><blockquote>quote:</font><hr />Originally posted by far-trader:
But if we are to believe that and take your approach then the OTU must have Instantaneous communication (and by default perhaps instantaneous travel) across that distance. Check the last report on the page. It's stated as reported at Terra/Sol on 142-1112 and the Regina/Regina date of release is 142-1112! Quick! Detain that Xboat! It has instant infinity drives!
What makes you think the dates don't work (Assuming the third dispatch was sent off on 142-1111)? Using a jump-6 courier network it is possible, although the 346 day run is freakishly fast. You have to assume that the Navy has couriers standing by to jump out the moment the previous courier in the chain arrives and that the data is transferred very quickly. For the 346 day run an uncommonly large number of the couriers has to jump significantly 'short', that is, their jumps must take considerably less than the average time.Originally posted by rancke:
</font><blockquote>quote:</font><hr />Originally posted by far-trader:
...all, and I mean ALL canon must be taken with a grain of salt and liberally spiced with uncommon sense. In this case the dates don't work so ignore them and correct them for YTU and sleep soundly knowing you have done your bit to make the OTU that much safer![]()
However, if you assume the Navy uses pairs of couriers rather than singletons, you shave an average of 6 hours off each jump, which helps a lot. (No, there's no canonical source that says the Navy uses courier pairs. But it's a useful idea and there is nothing that says they don't).
Hans </font>[/QUOTE]And here you confirm my suspicion above that you mean we must accept that the messages came by some super efficient J6 courier. That is why I say the dates don't work. I won't argue that such couriers exist or not, that is not the point at all for this case. The point is that the TNS is a service provided for members of the Travellers' Aid Society and as such goes by the quickest public distribution, the J4 Xboat routes. There is no way[1] the message could travel that distance in that time by that method. So before I'd discard that piece of canon, I'd try to come up with a reasonable explanation for the seeming inconsistencies, and only if that is not possible would I change it, and then as little as possible to make it fit. The possible changes are the dates are wrong or they came at quicker than J6. Gee, let's see, which is the smaller change. I think I'll just change the dates, either the date sent or the date of arrival. Keeping the date sent (and in this case 'correcting' the one that is obviously in all likelyhood a typo) makes the most sense since that way the meta-story stays rational and I (or anyone else) can determine when that particular story hits the players' hand comp no matter where in the Imperium they are when they log in for their TAS subscription. In fact this seems to only be an issue because those three items start with:
I'm not sure what the source of those is but a quick look through some old JTAS and Challenge as well as the current online TNS by SJG only finds one date for each dispatch, presumably the date of publication for the star system listed which also seems to be the star system of original filing of the news item. So the default and sensible format of 'reporting' TNS dispatches with the original filing star system and date was broken here, and with the obvious result of broken canon. So again the obvious and easiest fix is to change the dates.A dispatch from Terra/Sol (O207-A867A69-F) dated 130-1111 reads:![]()
[1] - Ok, there is at least one way. An Xboat (well more like three in this case) misjumps, and by luck survives and ends up farther along the route and in a link system. That is patently absurd of course since the service of each Xboat in each link and the use of only Xboat Tender Fuel Lab processed LH is all designed to eliminate any misjump chance.