Community project: AlliED "unknowns" repository

[ual002]

Ok, yea just use the link to the spreadsheet and take a screenshot.

[Darksaber]

Why take a screenshot when he can download it as a Excel spreadsheet???

[ual002]

That works too.

[Safe-Keeper]

Some wonderful discoveries here, thank you to all who contributed :O .

This also reminded me I need to check out YOGEME again. Will do so now.

[ual002]

Yogme can still be a little buggy but it has some really cool features being actively developed.

[Safe-Keeper]

For whoever knows, does the "no cargo pods" affect anything? I picture for example a Container Transport without containers. Does it change how some of the ships end up appearing?

And yes, YOGEME does look really promising. Will probably use it in tandem with AlliED in the future.

[ual002]

I wondered that as well. There seems to be a lot of orders im still not entirely sure how to use even nearly 20 years later.

We should have like an allied/yogme workshop. Maybe a series of youtube videos. I could totally do this. I wonder what I should focus on, how long episodes would be and how I would break up subject material between videos. Im no expert but I feel like the basics would be a good start.

[Phoenix Leader]

Just a minor update: Status 27 is used to prevent the objects inside a hangar from being targeted.

[Jaeven]

I'm not sure what that means. How would you target objects inside a hangar?

[Phoenix Leader]

In all the missions of the Prologue there is a hangar container CN/HRG Azzameen.
In missions 1, 2, 3 and 4 this hangar has status 27, whereas in missions 5, 6 and 7 both the status lines are set to normal.
In missions 5, 6 and 7 you can target the 5 containers K and 2 containers L inside the hangar of the Azzameen base, whereas in the previous missions you can't.

However, there is a completely illogical fact: even if those 7 containers belong to your team and you have just left the hangar, they are not only not inspected yet, but they are also unidentified!

[Phoenix Leader]

A partial solution to solve this incoherence could be adding status 27 to CN/HRG Azzameen in those missions, even though the 7 containers will still be displayed in the friendly craft list as unknowns, just like the connector rods in a Cargo Tanker train.

[keiranhalcyon7]

Interesting... those 7 containers in the hangar aren't present in AlliED, and that container/Hgr isn't present in game. It's like the exe is replacing the CN/Hgr with the containers K and L in the Azzameen base hangar.

Note: with status 27, the containers are still targettable with boresights, just not when cycling targets.

[Phoenix Leader]

You are right. Even with status 27 assigned, the containers can still be targeted by pressing Alt+1.
An other interesting fact is that status 27 only works when assigned as Status 1.
If you set Status 1: 200% Shields and Status 2: 27, the containers can still be targeted with cycling targets (T or Y).
Same result if you assign an other status as Status 1 (I've experimented nearly all of them).

[Phoenix Leader]

There are also other objects inside the hangar which cannot be targeted even with Alt+1 regardless of the Status assigned, but you still get the message when you destroy them: for example "NA Pi 4 destroyed".

[Phoenix Leader]

It seems that Status 1: 27 only works with the hangar.
Tried to assign it to a Hyper Buoy but it didn't work.

[Driftwood]

Apparently you've never played any of DTMs planetary missions. Condition 27 works fine, the hyper bouy is probably hard coded to be targetable regardless of conditions.

[JeremyaFr]

The hyper buoy is automatically targetted when pressing the N key.

[Darksaber]

Anyone got any more updates to the Allied text files??

Class.txt
Conds.txt
Status.txt

Would you please share your updated files please

[Bman]

Hi DS, here are mine, WIP, but they "might be" outdated if new things have been discovered/added. You could dump these into Excel file and compare to other versions if that helps.

AlliEDFiles.zip

[Darksaber]

Cheers mate

[Phoenix Leader]

At last the updated Status.txt file.
Thanks Bman, awesome addition.

[Phoenix Leader]

I have just compared the Status list with the numbers and I have only 1 minor question to ask: isn't the Limited Targetability Status number 27, instead of number 28?
As for its function to prevent the player from targeting crafts using cycling targets (T or Y) I have no idea why it works only when it's set in the Status 1 position.

[Mark_Farlander]

The answer to the second thing might be hidden in the order the Status are applied to the Flight Group.
I remember this old post about the order the shield status is evaluated: https://xwaupgrade.com/phpBB3/viewtopic ... 7&start=29
My suspect is that there is something similar about the order already identified/not identified/already inspected/not inspected/Limited Targetability status are evaluated.

[Mark_Farlander]

I don't remember if that shield status evaluation order is a priority-exclusive order or if it's a priority order where the effects of the 2 status are cumulative.

[JeremyaFr]

The status number 27 is only evaluated for status1, not for status2.