Railjack Salvage incorrectly rewarded as finished item #1645
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Somewhat related to #911, Railjack components obtained as Salvage as... reward missions? are rewarded instead as completed items that... seem to be treated like skins?
Which results in a completely cosmetic, non-stat changing item:

Components obtained as enemy drops, on the contrary, are handled as CrewshipSalvage:
I am unsure if the vastly different item paths are still correct for either and if it's just being put in the wrong place, or if it's rewarding the wrong item altogether.
/Lotus/StoreItems/Upgrades/Skins/RailJack/ReactorLavanA
has product categoryCrewShipWeaponSkins
, so from what I can tell, the server is adding this in the correct array?It should be being added into Salvage to be identified, then repaired, then finally added to the list of usable components with their unique stats.
The Lavan Reactor Mk1 should have a random Duration bonus of 20 to 40%, compared to the Sigmar Reactor's 0% bonus on all stats. As you can see in the screenshot provided in the issue, it has no stats. Same applies for every other piece of non-Salvage equipment, which are all being treated as skins with no stats rather than items with semi-random stats like Kuva Weapons.
It means that no, it's not in the correct array. It should all be being added to
CrewShipRawSalvage
alongside parts obtained from killing enemies.I tested Railjack drops again. Drops work and salvage is the correct item type (unlike whatever is going on here?), however salvage identification is unimplemented.
Shall I open a separate issue for it?
The issue isn't drops, it's mission rewards specifically.
Also, identification already has an issue: #911, which... you opened yourself, and I've already linked to here before.
Apologies, it's been a bit since I opened that issue. Forgot about that.