Cannot identify Railjack Weapon #1729

Closed
opened 2025-04-18 13:48:59 -07:00 by VampireKitten · 3 comments
Contributor

This error popped up in a fully updated server.

2025-04-18T22:41:29:752 [0.1.0] error:  TypeError: Cannot read properties of undefined (reading '0') while processing /api/crewShipIdentifySalvage.php request
    at crewShipIdentifySalvageController (C:\Games\Warframe - Server Emulator\SpaceNinjaServer\src\controllers\api\crewShipIdentifySalvageController.ts:45:50)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2025-04-18T22:41:29:753 [0.1.0] http:   POST /api/crewShipIdentifySalvage.php?accountId=67bcb55f31fac393062d59a0&nonce=895069757794464&ct=MSI 500 8.264 ms - -

The item I was trying to identify was the following:

  "CrewShipRawSalvage": [
    {
      "ItemType": "/Lotus/Weapons/CrewShip/Laser/Blaster/VidarBlasterTierA",
      "ItemCount": 1
    }
  ],
This error popped up in a fully updated server. ``` 2025-04-18T22:41:29:752 [0.1.0] error: TypeError: Cannot read properties of undefined (reading '0') while processing /api/crewShipIdentifySalvage.php request at crewShipIdentifySalvageController (C:\Games\Warframe - Server Emulator\SpaceNinjaServer\src\controllers\api\crewShipIdentifySalvageController.ts:45:50) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-04-18T22:41:29:753 [0.1.0] http: POST /api/crewShipIdentifySalvage.php?accountId=67bcb55f31fac393062d59a0&nonce=895069757794464&ct=MSI 500 8.264 ms - - ``` The item I was trying to identify was the following: ``` "CrewShipRawSalvage": [ { "ItemType": "/Lotus/Weapons/CrewShip/Laser/Blaster/VidarBlasterTierA", "ItemCount": 1 } ], ```
Sainan added the
bug
label 2025-04-18 13:51:51 -07:00
Owner

From what I understand, "Vidar Carcinnox MK I" should not have random stats, so does not need to be identified?

From what I understand, "Vidar Carcinnox MK I" should not have random stats, so does not need to be identified?
Author
Contributor

All component drops need to be identified, as far as I'm aware. Give me a moment to test out on live.

All component drops need to be identified, as far as I'm aware. Give me a moment to test out on live.
Sainan added the
pr'd for
label 2025-04-18 14:01:55 -07:00
Author
Contributor

In-mission components drops still need to be identified, even if they don't possess random stats:
image.png
image.png

In-mission components drops still need to be identified, even if they don't possess random stats: ![image.png](/attachments/e7a65bf1-86d5-44c9-b8bd-3f33c82a2f92) ![image.png](/attachments/593c1b20-4709-4596-b91f-15654033620b)
543 KiB
156 KiB
Sign in to join this conversation.
No description provided.