Page 7 of 7

Re:

Posted: Thu Jul 05, 2012 10:58 pm
by Rese249er
Ark wrote:
The pi42sandwichboard is not a billboard. It is a custom escape capsule
Which can be scooped. amusingly enough.

Re: Re:

Posted: Sat Jul 07, 2012 6:18 am
by BuggyBY
Rese249er wrote:
Ark wrote:
The pi42sandwichboard is not a billboard. It is a custom escape capsule
Which can be scooped. amusingly enough.
Yep, I've always enjoyed the opportunity to ransom the poor constore clerks to their employers if I wasn't interested in the escort mission (which I always suspected would have them end up working for less than minimum wage until they'd paid it off)—or to sell them at the main station anyway if the escort reward turned out to be unexpectedly high.

Re: Oo-Haul - random escort missions (v.1.5)

Posted: Wed Oct 03, 2012 6:10 am
by BuggyBY
This particular Oo-haul mission ended (?) rather earlier than expected. The L-crate hauler had just completed one of its odd midway course correction maneuvers (involving first coming to a stop and starting in a completely different direction, then stopping again and turning approximately in the direction of the station beacon) when I got this message:
"Thanks. Your pay will be deposited now"

I paused the game to take a screenshot, so cannot confirm if abandoning the hauler to its fate and heading to the main station (still a considerable distance) on my own now will still get me payment, but this looks like it's either a bug or a supremely overconfident Oo-haul pilot.

Edit: Indeed we were (or rather I was) not only ambushed by a large group of pirates on the way to the station after this message, but also there was a large furball going on when we got to the Aegis, which even involved the destruction of a [wiki]HammerHead[/wiki] carrier whose cargo sleds had been in the process of reattaching. My own military shields were downed and I lost 2TC of valuable cargo, but the hauler did not get attacked. When I docked, I was rewarded with 4330 ₢ (the size of the payment being another reason why I had been reluctant to abandon the hauler midway and make a beeline for the station on injectors in the noble cause of bug documentation).

Re: Oo-Haul - random escort missions (v.1.5)

Posted: Wed Oct 03, 2012 4:29 pm
by Tricky
I notice you have multiple planets in that system. The AI sets a course to the nearest planet and not the main planet and then sets a course to the system station. I'm guessing a delayed DESIRED_RANGE_ACHIEVED was acted upon when going to the system station.

Re: Oo-Haul - random escort missions (v.1.5)

Posted: Thu Feb 28, 2013 5:15 pm
by Tricky
Actually using v1.6

Under v1.77 (Deployment and trunk rev 5642), I am getting the now familiar description text replacement errors.

Image
Click thumbnail for larger version.

Re: Oo-Haul - random escort missions (v.1.5)

Posted: Thu Feb 28, 2013 8:26 pm
by Eric Walch
Tricky wrote:
Under v1.77 (Deployment and trunk rev 5642), I am getting the now familiar description text replacement errors.
It is not 100% the same bug as the others. When I remember correct, it was the intention that this expansion should still work for old legacy code. And this particular oxp still uses legacy code for it's mission screens. This could mean an Oolite bug as it breaks old code. And in legacy code there is also no alternative way of displaying the station name.

And the string is even recognised in the script itself:

Code: Select all

            conditions = ("status_string equal STATUS_DOCKED"); 
            do = (
                {
                    conditions = (
                        "dockedStationName_string oneof Pi-42 Con Store, Tescoo Con Store, Mall-Wart Con Store, Star Con Store, Sainsboory's Con Store"
                    ); 
                    do = (
Or the mission screen would not been visible. But in the expansion of the mission text itself, it becomes unknown.

In this particular OXP, it was on my list to replace the legacy code at some point as it is so small that it is hardly any trouble.

Re: Oo-Haul - random escort missions (v.1.5)

Posted: Thu Oct 20, 2022 4:17 pm
by Cholmondely
Am I correct in presuming that this is broken?