At a starbase you're allowed to select the Fix mission
(but not Recycle) for allied ships, but that shouldn't be
allowed since you can't fix any ships but your own.
I know for sure that you are allowed to fix allied ships in
PHost, and that you are allowed to fix /any/ ship in older
THosts. I don't know about newer THosts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I first came across this in Donovan's help pages - http://www.xs4all.nl/~donovan/help/starbases.htm#fixrecycle
- which I looked up because I had a damaged allied ship at
my base, and I wasn't sure if allied fixing was allowed. So I
set the base mission to fix that ship, and it was NOT fixed, at
least in TimHost v3.22.047.
Ah - after some digging in the TimHost changelog I found this: http://www.vgaplanets.com/hst321.htm
HOST 3.22.024
* Cheat Stopped: Check added to make sure that when you
are fixing a ship from a starbase that the starbase is really
under the ship. (People were cheating by fixing ships from
distant starbases using a 3rd party player side program.) Also
you can not fix another players ships with your base.
So Tim says you can't fix allied ships after THost v3.22.024 :)
I'm not sure if VPA is aware of the THost version, but it
should be (at least from the PBP message if not anywhere
else). Perhaps VPA can disable allied fixing only for THost
v3.22.024 and newer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know if there's a better way, but it should be really
easy to parse the priority-build-points message for the host
version. Make that a feature-request :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=138639
...says who?
I know for sure that you are allowed to fix allied ships in
PHost, and that you are allowed to fix /any/ ship in older
THosts. I don't know about newer THosts.
Logged In: YES
user_id=429434
I first came across this in Donovan's help pages -
http://www.xs4all.nl/~donovan/help/starbases.htm#fixrecycle
- which I looked up because I had a damaged allied ship at
my base, and I wasn't sure if allied fixing was allowed. So I
set the base mission to fix that ship, and it was NOT fixed, at
least in TimHost v3.22.047.
Ah - after some digging in the TimHost changelog I found this:
http://www.vgaplanets.com/hst321.htm
HOST 3.22.024
* Cheat Stopped: Check added to make sure that when you
are fixing a ship from a starbase that the starbase is really
under the ship. (People were cheating by fixing ships from
distant starbases using a 3rd party player side program.) Also
you can not fix another players ships with your base.
So Tim says you can't fix allied ships after THost v3.22.024 :)
I'm not sure if VPA is aware of the THost version, but it
should be (at least from the PBP message if not anywhere
else). Perhaps VPA can disable allied fixing only for THost
v3.22.024 and newer?
Logged In: YES
user_id=138639
Okay.
(I think the last HOST version I played with was .020, hence
I didn't know about the new ones)
Currently, VPA does not have any idea about the host
version. Maybe that can be changed. In this case we can
probably also add an appropriate check.
I have a feeling that Tim only added that restriction
because VPA was able to set fix-allies orders :)
Logged In: YES
user_id=429434
I don't know if there's a better way, but it should be really
easy to parse the priority-build-points message for the host
version. Make that a feature-request :)