llywelyn | |||||
Had not moved this ship for awhile and had amassed 300 tus. Was, as can be seen, located in Yank to begin with. I run Quick Snack (1123) so, that's not a problem. My ships do have access rights, so that's ruled out. Starting Location: Lunk (603) Orbit - Quadrant Gamma 13 - Yank System (146) >TU 300: Move to Starbase {1123} {Dock - No} >TU 300: Pickup {1123} {80} {22} {} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 290: Pickup {1123} {98} {20} {} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 280: Pickup {1123} {30085} {600} {} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 270: Pickup {1123} {30336} {400} {} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 I've double-checked my inventory and all the items are there. 1 week wasted unless I can determine a reason (other than espionage ![]() | 27 Heavy Hull (80) - 100 mus 27 Bunks (98) - 10 mus | 600 Cyprian Wines (30085) - 1 mus 400 Detinus Media (30336) - 1 mus If anyone has an idea on the problem, I would be interested to know, as it is, I'm fed up with my captain and about to keel-haul him ![]() Larry | |||||
Steve-Law | |||||
Is this right? >TU 300: Move to Starbase {1123} {Dock - No} >TU 300: Pickup {1123} {80} {22} {} {Install - No} It doesn't seem to have moved at all, but there was no message for the move order? Where did the ship END it's turn? Error - Target is not accessible. usually means that the target, in this case {1123} is not in the same location as the ship (in other words the ship isn't at that starbase). | |||||
Mica Goldstone | |||||
Market Report for: RIP Quick Snack (1123) Location: Spritzer (256), Yank (146) System This does leave the question, why didn't you change orbits from Lunk? | |||||
llywelyn | |||||
Exodus (37820) Her ending orders had her jumping to Aurora (2145) and she ended up at Quadrant Gamma 10 - Blagard System (172) -- not enough tus to get there, so that isn't an issue. Looking over my orders, about 6 of my ships have had problems finding Quick Snack. Also, I checked my update on Quick Snack, and the items attempted to be picked up are there, so that wasn't an issue. As Mica asked "... Why didn't you change orbits from Lunk". I don't know ![]() ![]() As to Steve's question, as you see the orders, that's what I got back. Her ending orders had her jumping to Aurora (2145) and she ended up at Quadrant Gamma 10 - Blagard System (172) -- not enough tus to get there, so that isn't an issue. Should I e-mail the full turn and let it be disected? ![]() I could understand a transposation of #'s, that's easy enough to do, but that's not the case. Llywelyn | |||||
nortonweb | |||||
I had the same thing today: >TU 93: Move to Starbase {xxxxx} {Dock - Yes} >TU 93: Deliver {xxxxx} {100} {10} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 83: Deliver {xxxxx} {98} {11} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 73: Deliver {xxxxx} {350} {1} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 63: Deliver {xxxxx} {164} {15} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 53: Deliver {xxxxx} {175} {4} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 43: Deliver {xxxxx} {308} {5} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 33: Deliver {xxxxx} {160} {32} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 >TU 23: Deliver {xxxxx} {161} {38} {TUET} {Install - No} Error - Target is not accessible. Total TU cost for this action is 10 I was in orbit of xxxxx and had the TU's to land.... xxxxx has orbit docks big enough for me as another ship landed fine the same turn. xxxxx is a small hidden outpost :-) the ship was in orbit before the first order could that be the issue? Peter | |||||
clif_lawrence1982 | |||||
Steve: I like you but it sounds like you're defending somthing that at this point is screwed up. I sent in a copy of my turns yesterday because of the same problem. It happened again today. I landed at the right x y and it belonged to me and I tried to deliver and it said target inacessable. This is not a player error. Evidently when the new combat rules went into effect somthing screwed up in the computer and now we're wasting sometimes HOURs doing our turns and then wasting the money we paid for it. I never thought I'd be throwing that up, I figgured if the computer screwed up everynow and then and I didn't get my turns that since it is role playing, things like that happen. But the other day I went from Friday to Wedsday with no record of my turns coming in. Mica did send them all on Wendsday which was nice and now they're coming in, but still I wasted alot of time. Then theres this problem with the turns being stopped when you don't put in the command "if error stop" or "if error continue". Its supposed to give you an option. Thats why that order is in there. But presently I don't have that option. Its not me. Its not larry. and its not anybody else. Its the computer(s) that are screwing up. I think the right thing to do, other than the obvious fixing the bug, is to credit us for one week. But, I am not going to push that. Its just stupid to waste HOURS on your turns only to have to do them all over again due to computer error. Since this has been going on at least a week, I'm curious as to if anyone is doing anything about it. clif | |||||
Steve-Law | |||||
Erm, what am I defending? I thought I was helping to define the problem (i.e. it's a movement problem not a pickup problem). Oh well, there you go, it's a funny old world.
| |||||
David Bethel | |||||
That was the whole issue - i fixed a squadron bug that cause the more complex orders to fail under certain circumstances. So it never moved you to the location you wanted and did not fail as it should have done. The problem itself is resolved now but i was out of contact on thursday before going to see mica on friday - hence the delay. | |||||
David Bethel | |||||
Can you explain this a bit more ? Is the option not there? or do you think it failed to do what it says ? The issue with the move to starbase/planet orbit/planet XY was bugged and just did not stop no matter what was put, but i think that was introduced eariler in the week. Is there something else to worry about here or was that the problem? | |||||
nortonweb | |||||
Hi David I'll check to see if its fixed (I'll use the same ship and run the same orders etc) but this ship (and the others) we not part of a squadron. Would that routine still effect other ships? cheers Pete | |||||
David Bethel | |||||
squadron orders run through the same functions as normal orders its just a acase of how you run them. Thats why fixing squadron things can screw normal things. |