Wormhole controller in Forgotten enemies.

[Annihilator]

Hi everybody!
Sorry for my english, but i have a problem in Battlezone 2 Combat Commander: Forgotten enemies.
In mission called "two-minute-warning" or something like that, in the end of mission we have to enter the access code (856 if i remember) to somewhere... And if hit "i" key while looking at wormhole controller the message says : "Logging onto alien network..." And nothing happens then...
I dont know what to do, how to finish mission!
Help me please!

--------------------------------------------------------------------------------
Annihilator

[Ded10c]

Which version of BZ2, and which version of FE? I assume PB6.2 and FE13. If so, then yeah, that mission's broken.

[Annihilator]

Emm where to find it? in main menu of BZ2 forgotten enemies i see FE 1.3 PB6
So what does it mean? and what to do next

[Ded10c]

Since FE was made years ago and released on 1.2, it requires a lot of updating to get it to work with the current patch. Red Devil is currently the one doing that; he knows about the problem and he's working on it (and the multitude of others). So the best thing you can do right now is to sit tight and find more bugs.

[Annihilator]

Yahoooo i have found the way to complete the mission!!!

[Annihilator]

I have completed the mission!
1: When the rebel officer gave you the passcode you must take him to his dropship back. (I took him with tug and brought to the droppoint).
2:Quickly (very-very) build a fotress around the wormhole controller. It must be ONLY GUNTOWERS!
P.S: You can do №2 before №1. It will be easier, because after you take rebel to his ship YOUR UNITS are escaping out of your control! Its okay, and you cant do anything with it. In objectives its said that the pilots will be taken to Earth,so...
3: After you completed №2 you d better take ALL your units to recycle.
4: There MUST NOT be ANY units exept you, buildings, scavengers (deployed), and gun towers.
P.S: If you find a unit which is stuck in a wall or trying to get over it its better to destroy that unit. And you cant activate the wormhole until there is even 1 unit (exept you)
5: When you ve done everything i told before (^) you must activate Wormhole controller. Its not simple. Hit "i" button while looking at wormhole conrtoller (the message"logging to alien network" must appear), then move forward or somewhere aroud controller with that message (logging to alien network) until the window of wormhole appears. Press some buttons (i dont know what to do exactly), then the window will say :"enter the passcode". we click the mouse button on the 0 , then we type : "852". then press enter or ok i dont remember. If you wrote everything right, there must be choice: 1 of 3: Activate, Shutdown, Log off. DONT PRESS SHUTDOWN, press activate.
6: Than the wormhole is starting to activate. It will activate in 10 minutes, but you must stay near wormhole for 8 mins. than you will have 90 secs to escape. The condor landed to take you out of the planet. (It landed near the place, where the rebel officer landed). Run there as fast as you can.
7: When you will fly into a condor you will see how your guntowers are protecting your wormhole controller. you can bravery press SPACE and we will see a process like going through the wormhole. General says :"Good job,John. Lets go home"
THE END OF MISSION!
!!! P.S.: before №1 you must be in Hacker Scout! And after №1 you MUST NOT get out of it, because general will say that you have lost it. DONT TRY!!!
the enemy waves of enemies will be very very big and dangerous! Build as many guntowers as you can!!
Well, its over. Thank you for reading!

[Ded10c]

First couple of points are simply the mission not playing as it should (scripts get buggered very quickly when you move them from 1.2 to 1.3). Some need additional notes, though.

5. You need to be fairly close, as the Hacker Scout's systems only have a certain range. Can't remember what it is, but I'm fairly sure it's mentioned somewhere. Probably the briefing.
6. That 10-minute period is supposed to be where the Hadeans assault the wormhole controller in an attempt to get you out of the system; are the attacking, or are you just left waiting?
7. Could you explain that a little more? It sounds like the first bit is playing fine and then something gets jiggered and something from the end of BZ2 gets swapped in (the main character in FE is called Joe, not John).

End point; if you get out of a vehicle, the way the script sees it is changed. This isn't the exact coding, but I imagine it's pretty similar (not looked at the script so I can't be sure)

Player's pilot is marked as "player".
Vehicle that player's pilot got in to (technically, the pilot no longer exists) is marked as "player_vehicle".
If the player gets out and the object "player" is created again, the player's vehicle becomes "vehicle".

So, in short, if you get out of the Hacker Scout it's not *your* Hacker Scout any more. The way the script sees it changes, but since the script is looking for *your* hacker scout, not just *a* hacker scout, it assumes it was destroyed.

[Nielk1]

Labels shouldn't change on game objects.

[Ded10c]

The scriptor does allow you to change that using GetByLabel and similar commands, so it could be that.

[Nielk1]

The scriptor does allow you to change that using GetByLabel and similar commands, so it could be that.

I don't think the DLL has had write access to the label of an object till recently. Certainly not before the scriptor was around.

Read access, as you posted, is irrelevant, since we are talking about the label changing, which it never should.

[Ded10c]

It's been a long time since I used the scriptor, but I'm fairly sure you can change how the scriptor refers to objects (it may not directly change its label and instead use some other variable of its own, I'm not sure.)

[Nielk1]

The only reason for a scriptor based DLL to have an issue when you hop out is insufficient coding.

[Annihilator]

Alright i see. I will write as soon as i can.

[Annihilator]

4. Units that are present but are out of the player's control do not matter. Only the units that the player has control of must disappear.

6. Hadeans were attacking as they should.

7. Sorry for my mistake. The voice says "Joe", not "John".

More strange things I noticed in this mission:

1. The tech officer's behavior looks inadequate. He obviously tries to reach some point but gets stuck in the walls. To continue, I had to pick him up with a tug and pull him to the landing zone where he flew away with the ship.

2. Some pipes are real, some are virtual and cannot be destroyed.

3. The battery tray, the Eyes of Xyr and some of the nearby guntowers near the player's base cannot be destroyed with AT Stabber. Some of them can be destroyed with plasma. Most of them can be destroyed only with the bomber but not all (I am not completely sure about this).

4. One of the turrets that guard the enemy resourcerer is located inside of a pipe. The player cannot make damage to the turret until he is pushed through the pipe -- but the turret can damage the player's ship.

5. The situation with the hacker scout remains unclear. If the player is supposed not to leave the scout during the whole mission, it should be mentioned somewhere. Because the first desire is to leave the scout and use another vehicle.

[Ded10c]

Those pipes really shoudn't be that size. Red Devil regenerated the XSIs for no apparent reason, and now they're too big. The old meshes still work, so they can just be copied in. They screw up the map real good at that size.