Command [TL=03:40:49]:[3570] (?=Help)? : 4798
<Move>
Warping to Sector 4798

That Warp Lane is not adjacent.
Do you want to engage the TransWarp drive?

Who's Playing

Rear Admiral Thor [1]

Do you want to engage the TransWarp drive? Yes
Sector 4798 is 11 hops away from here.
You do not have any fighters in Sector 4798.
*** WARNING *** No locating beam found for sector 4798
Do you want to make this jump blind? Yes

-=-=-=- TransWarp Drive Engaged! -=-=-=-
YOUR SHIP MATERIALIZED IN A SOLID MASS!
For losing this ship,
you LOSE 10 experience point(s).
Your Imperial StarShip has been destroyed!

Your trusty Escape Pod is functioning normally.
For getting blown up you LOSE 58014 experience point(s).
You have been demoted to Commodore!
Sector 4798 will now be avoided in future navigation calculations.

You barely make it into your trusty escape pod.


I haven't ever had much problem with smartmove--I was running TWXProxy's keepalive along with this, which sends a periodic "#" character. I don't see how that could cause this to happen though... doh.

You can actually "over-ride" Swath's blind warp safety if you hit enter twice, very quickly.

Slow down!

Yeah, take it from Cruncher. I've seen her do it repeatedly. (snicker)

It may be a case since you were using it in conjunction with TWX that if helper mode was off, the safety to prevent blind warp may have been off.

I have not experienced that directly for twarping, but have made fatal errors where it did not prevent moving me into a sectors that were heavily defended.

I didn't do that... I'm referring to the smartmove script--press ctrl-m and it moves you to the sector you type in in the best way possible. If you have figs nearby, it twarps there. It does its best to be on the lookout for hostile sectors between here & there.

Actually, it seems to sometimes blunder into hostile sectors. Oh well...

Did you have the parser turned off? (The light bulb button.)

I normally wouldn't turn it off. I sometimes turn it off if my hard drive is going bananas because the incoming text is going too fast. But I'll double check.