-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(T/F) board to destroy cargo order doesn't work completely in game #117
Labels
external
Issue with child DLL or other utility, not item itself
Comments
It's "Destroy Cargo", not "Destroy Target". The craft doesn't explode, but
the boarded craft's cargo is removed without being transferred to the
boarding craft.
|
I just tested it and all that happens is the craft docks and the cargo on the ship that is docked with remains |
Hmm, went to the TIE95 code base, and it appears to be a generic boarding,
with no real action taken. The targeted craft is given a FullStop order
upon completion, and that seems to be it.
|
I assume that the order should work like it does in XVT |
Yes. TIE95 uses the same flight engine as XvT, and for the most part
everything behaves the same minus whatever additions XvT made. There are
times where something was apparently in-progress during TIE's development,
but then got abandoned or disabled along the way, sometimes to be finished
in XvT. This particular order looks like one of those. Not an order that
gets used a lot which explains why this got by for so long.
|
yeah, I think it's only used in one mission I believe B9M1 |
Updated to "Board with no Effect" via Platform.dll commit. Will be in the next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I was testing this order and I found that in original game that a craft with this order will dock with it's target but after it finishes the target won't blow up, so maybe a note on the descriptions that in T/F that how the order works rather than what it says.
The text was updated successfully, but these errors were encountered: