Nemesis system (might) not be working correctly on imported inventories. #2118

New Issue

Ghost · 2025-06-06T11:15:19-07:00

Ghost commented

2025-06-06 11:15:19 -07:00

I initially suspected it could've been due to #2113, but that unfortunately wasn't the entirety of my issue. I should preface this by stating that I am not familiar with the current state of the nemesis system in SNS; however, after reviewing commits and PRs, I assume it to be in a functional state.

Upon doing the requisites to activate a nemesis on (my) imported inventory, whether it be Coda, Corpus, or Kuva, the data will reflect that in MongoDB. Completing nodes listed under the InfNodes field will be removed from the array. The MissionCount field will increment as well. However, there is nothing in-game to reflect that anything related to the nemesis system is happening.

When leaving the mission after activating a nemesis, the pop-up animation that shows the name of the nemesis plays, but it will never activate. There is no menu to view the nemesis, there are no influence nodes visible, no enemies relating to the nemesis will spawn, etc. This remains true after restarting the server and the game.

My first assumption would be that the imported data was missing a relevant field or value that would allow the Nemesis system to function properly.

I used the AlecaFrame Inventory Parser to initially import my inventory, as I already had AlecaFrame installed.
I have completed all story quests before The Lotus Eaters, and The Hex on live. Both story quests were then completed on SNS.
I have extensively used the Nemesis system on live and obtained several weapons from them before import.
I have included my latest combined.log file, which contains the results of my testing, and I can provide my current inventory data upon request.
I have tested this on the latest commit 01492f4f16.
I am using stripped assets.
I am on the latest game client as of writing.

I initially suspected it could've been due to #2113, but that unfortunately wasn't the entirety of my issue. I should preface this by stating that I am not familiar with the current state of the nemesis system in SNS; however, after reviewing commits and PRs, I assume it to be in a functional state. Upon doing the requisites to activate a nemesis on (my) **imported** inventory, whether it be Coda, Corpus, or Kuva, the data will reflect that in MongoDB. Completing nodes listed under the `InfNodes` field will be removed from the array. The `MissionCount` field will increment as well. However, there is nothing in-game to reflect that anything related to the nemesis system is happening. When leaving the mission after activating a nemesis, the pop-up animation that shows the name of the nemesis plays, but it will never activate. There is no menu to view the nemesis, there are no influence nodes visible, no enemies relating to the nemesis will spawn, etc. This remains true after restarting the server and the game. My first assumption would be that the imported data was missing a relevant field or value that would allow the Nemesis system to function properly. - I used the AlecaFrame Inventory Parser to initially import my inventory, as I already had AlecaFrame installed. - I have completed all story quests before The Lotus Eaters, and The Hex on live. Both story quests were then completed on SNS. - I have extensively used the Nemesis system on live and obtained several weapons from them before import. - I have included my latest `combined.log` file, which contains the results of my testing, and I can provide my current inventory data upon request. - I have tested this on the latest commit https://onlyg.it/OpenWF/SpaceNinjaServer/commit/01492f4f16980f174eea865078930164843dc414. - I am using stripped assets. - I am on the latest game client as of writing.

combined.log.2025-06-06.log

169 KiB

Sainan referenced a pull request that will close this issue

2025-06-06 13:12:45 -07:00

fix: swapped operands #2119

Sainan added the

bug

pr'd for

labels 2025-06-06 13:12:52 -07:00

Sainan closed this issue

2025-06-06 13:13:36 -07:00

Sainan referenced this issue from a commit