#4 Not all dependencies shown

[xorange]

After injecting meta sometimes not all of the item's
dependencies are shown in the dependency swapper.
(I have heard this also occurs with meta that is native
to the map. i.e. not injected)

Tested by extracting elite char meta from newmombasa
& injecting over c_turret_ap vehi in coagulation.

When viewing the elite char meta in newmombasa all
dependencies are shown:
char
bipd
crea
styl
char
weap
weap
weap
weap
jpt!
weap

After injecting the elite char meta into coagulation the
dependencies show as:
char
crea
weap
weap
weap
weap
jpt!
weap

(Missing bipd, styl & char)

Perhaps a problem with how the app thinks
depepndencies are formatted?...considering they are
formatted differently than in Halo. Idk, just a guess.

[Steve Hansen]

Logged In: YES
user_id=900122

What does it show after the tag?
This should have been fixed in v0.5.2 or is it the current
source...

[xorange]

Logged In: YES
user_id=1164641

I'm not sure if I know what you mean by "after the tag?", but
I'm going to take a shot at it.

These are the first 5 dependencies (tag & ID):
char 200695E7
bipd 6C10E2F1
crea FFFFFFFF
styl FF1BCAFE
char 021CCBFE

In my previous example the bipd, styl & a char tag are not
showing up in the dependency-swapper after injecting the
meta.
The commonality I see there is that the bipd, style & one of
the char tags all have a higher numbered identifier.
The app has no problem with those dependencies when
viewing the meta in 03b_newmombasa because it expects the
tag IDs to go that high.
Once you inject that meta into a map with fewer tags then it
has a problem with those dependencies because it doesn't
expect any dependency IDs to be that high...and since it's
not null it doesn't show it as such, and thus it just doesn't
display the dependency at all.

Actually, as I was typing this I experimented to see if this is
in fact the case, and it is.
If a dependency has an identifier that, um, exceeds the
map's identifier range then it will simply not display the
dependency at all.
The manual fix is to open up the meta in a hex editor, either
prior to injecting, or after, and null out the dependency
identifiers (i.e. 0xFFFFFFFF), or of course just replace the ID
with the appropriate one from the new map.

[xorange]

Logged In: YES
user_id=1164641

oh btw, v0.5.2 is what I've been testing.