Skip to content

Possible corruption in Tech Hub Mission 4 on Staging #520

@ghramsey

Description

@ghramsey

This is a vague report. I'm not 100% sure what is really going on.

I've edited Tech Hub to speedup tranist cars, add an extra alien in M3, M4 and M10.
I moved the access tuner upgrade chip and locked the data archive room.
And I closed several Vent Traversal Markers inside the tunnels where extra aliens spawn and get stuck during Mission 10.

All of the above works finem but I have a bug. In Mission 4 the transit car is supposed to be arriving as
we enter the transit station. For some reason after the above changes something breaks that scripting.

In initially edited all of the transit cars from C# . When this issue first appeared I thought that was the cause.
It's not. I edited manually on Staging. All delays on the transit cars set to 0.1 and same on the composite instances.
Saved all of the changes and when I get to that part of mission 4 the transit car is not on arrival and the button is
locked out with a restore power message. A work around this potential soft lock is to pass through shopping or
engineering to sci hub. But the problem is this doesn't fix the issue. The transit car condition is saved and the car
is locked on the sci hub transit side too.

I backed up my work and substituted vanilla unaltered tech hub folder. I passed from Tech Comms to get a clean entry.
The car is on arrival and works normally. I subbed back the other files and it is broken again. So the issue is not following
a save file I don't think. Since there's no autosave on the entry to Tech Hub from Tech Comms that's probably a good thing.

I scrapped the entire tech hub file work and began anew using Master branch.
After that the entire issue has ceased. So I'm drawing a conclusion that something incorrect is
being introduced while editing from staging. It might not be but I have nothing else to go by.

I'm attaching the commands. pak editing from Staging.
GitHub refuses to allow posting of PAK file type so I'm fudging it by naming it as a ZIP.
Remove .ZIP extension. It's a normal Commands.PaK.

TechHub-COMMANDS.PAK.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    [TOOL] Script EditorThis issue applies to the script editor within OpenCAGE.bugSomething which causes issues when using the tools.only in staging branchThis bug is only found in the staging branch of OpenCAGE.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions