so, i’ll skip the fact that both me and @Debayan001 already made around 10 bug reports in the life span of a year SINCE the merge.
and since apparently bug report are not worth a damn,
guess there’s nothing left for me to do but to make it into a suggestion at this point.
the main Issue:
so, the main issue is that since first update AFTER the merge, the following items:
attachable_wear_planetree_summer_tunic_01_ger_summer_item &
attachable_wear_planetree_autnum_tunic_01_medic_ger_item
are broken ever since.
these is how they used to look like, ( and how they should look like )
this is how they instead, look today:
and without using photos that may look fabricated:
as you can see, they changed and “broke” the camouflage.
to instead, a pea dot camouflage.
why is this a problem?
well, because they broke one of the very few matching sets available that were there.
it was horrid enough to have mismatched splintertarn sets, or not so many complete pea dot camouflages.
now you only have pea dots left and right.
and, i’m going in more technical details to prove this.
so, the item in questions that are broken, as previously hinted,
attachable_wear_planetree_summer_tunic_01_ger_summer_item &
attachable_wear_planetree_autnum_tunic_01_medic_ger_item
and if we take a look in the editor with the property panel, here is what we can see:
this is the unedited base planetree_autnum_tunic_01
as you can see, it’s orange looking. and not actually a pea dot.
but if we go and take a look at the medic one, it has the same name yet it looks different:
as it goes for the default planetree_summer i can only show how it used to look when i started cataloguing cosmetic items for modders to use and curious people:
and if we take a look at the same tunic today:
it uses instead a pea dot camouflage/texture.
speaking of pea dot, the other issue that these bugged plane tree causes, is that they created a duplicates items:
the actual pea dot camouflage:
so what’s the point of changing plane tree camoflages to pea dots and have doubles / clones ?
no effing idea.
what can it be done? how can it be fixed?
very, and i’m not joking, very easily.
long story short, the error was made by someone when linking the path to the texture.
and even you can fix it in your own basement like i did.
but the following method will be done for developers, as it’s going to change the official pool of cosmetics since it’s there that needs to be changed.
the fact that it took developers so many frikkin updates it’s not funny anymore.
regardless here is a step by step on how to fix it;
- head over ww2_ger_items.blk
look for:
attachable_wear_planetree_summer_tunic_01_ger_summer_item{
_use:t="attachable_tunic"
_use:t="attachable_wear_tunic_m43_peadot_01_ger_summer_item"
}
[…]
attachable_wear_planetree_autnum_tunic_01_medic_ger_summer_item{
_use:t="attachable_tunic"
_use:t="attachable_wear_tunic_01_medic_ger_summer_item"
"animchar__objTexReplace:object"{
"ger_tunic_3_tex_d*":t="ger_tunic_peadot_tex_d*"
"ger_tunic_3_tex_n*":t="ger_tunic_peadot_tex_n*"
}
}
- change both TO:
attachable_wear_planetree_summer_tunic_01_ger_summer_item{
_use:t="attachable_tunic"
_use:t="attachable_wear_tunic_01_ger_summer_item"
"animchar__objTexReplace:object"{
"ger_tunic_3_tex_d*":t="ger_tunic_planetree_summer_tex_d*"
"ger_tunic_3_tex_n*":t="ger_tunic_planetree_summer_tex_n*"
"ger_tunic_3_tex_mask*":t="ger_tunic_cloth_tex_mask*"
}
}
attachable_wear_planetree_autnum_tunic_01_medic_ger_summer_item{
_use:t="attachable_tunic"
_use:t="attachable_wear_tunic_01_medic_ger_summer_item"
"animchar__objTexReplace:object"{
"ger_tunic_3_tex_d*":t="ger_tunic_planetree_tex_d*"
"ger_tunic_3_tex_n*":t="ger_tunic_planetree_tex_n*"
"ger_tunic_3_tex_mask*":t="ger_tunic_cloth_tex_mask*"
}
}
easy peasy.
it’s not rocket science.
Fun Fact
and it’s rather interesting how it’s taking this long, yet some of the “controversial” textures were edited in less than a hour:
if any of you could kindly pass it to developers yet again, would be great:
@Euthymia07-live
@MajorMcDonalds
@KitsuneLord91
@Shiivex
even though, to my understanding was already sent (?):
