GitHub Issue
Neverness to everness game not detected properly as 5.6(Shows as UE5.5 custom fork)+ Not accepting correct AES key to decrypting pak
### SCSKiller version
1.2.1
### Windows version
25h2
### GPU
RX 9070xt
### GPU driver version
26.9.2
### Game
Neverness to everness (its own custom launcher but also has steam version)
### What happened, and what you expected
Game has anti-cheat and is based on UE5.6.
SCSKiller detect it as UE5.5 custom fork or UE5.5. Upon inserting AES key to unlock pak files or exe, it fails.
Here is the AES key that worked for me to unlock pak files with **Fmodel** that contain PCD3D_SM6.stable upipelinecache.
0x390B40DA3E0805AE7397DFA707E7227DBA06C35E95262E7FFF8F8E60CBC7A69C
What I expect: Correctly detect the game as UE5.6 or accepts the AES key.
### Steps to reproduce
1. Open SCSKiller
2. Add HTgame.exe (The actual game exe file instead of the launcher)
3. SCSKiller detect it as anti-cheat game with custom UE5.5 fork (The game is actually UE5.6)
4. Unlock games files with working AES key(confirmed with Fmodel)
5. It fails
### Output or error text
```text
```
View Raw Thread
Developer & User Discourse
BlueHeisenberg • Oct 5, 2026
Thanks! The version detection is fixed in 1.2.3, please update. For the key, could you send the list of files in `HT\Content\Paks` with sizes?
davidbecam12 • Oct 6, 2026
Here you go. If you need exact bytes (Taken from size, not size on disk).
>
global.ucas 5376496
global.utoc 1894
pakchunk0-Windows.pak 8518830194
pakchunk0-Windows.sig 520480
pakchunk0-Windows.ucas 599607136
pakchunk0-Windows.utoc 930230
pakchunk1-Windows.pak 22941140
pakchunk1-Windows.sig 1932
pakchunk1-Windows.ucas 1910082896
pakchunk1-Windows.utoc 3322326
pakchunk2-Windows.pak 334636129
pakchunk2-Windows.sig 20956
pakchunk2-Windows.ucas 2059191872
pakchunk2-Windows.utoc 7831510
pakchunk3-Windows.pak 1971975035
pakchunk3-Windows.sig 120888
pakchunk3-Windows.ucas 11235083312
pakchunk3-Windows.utoc 16996390
pakchunk4-Windows.pak 1119658
pakchunk4-Windows.sig 600
pakchunk4-Windows.ucas 5815148752
pakchunk4-Windows.utoc 15931124
pakchunk5-Windows.pak...
>
global.ucas 5376496
global.utoc 1894
pakchunk0-Windows.pak 8518830194
pakchunk0-Windows.sig 520480
pakchunk0-Windows.ucas 599607136
pakchunk0-Windows.utoc 930230
pakchunk1-Windows.pak 22941140
pakchunk1-Windows.sig 1932
pakchunk1-Windows.ucas 1910082896
pakchunk1-Windows.utoc 3322326
pakchunk2-Windows.pak 334636129
pakchunk2-Windows.sig 20956
pakchunk2-Windows.ucas 2059191872
pakchunk2-Windows.utoc 7831510
pakchunk3-Windows.pak 1971975035
pakchunk3-Windows.sig 120888
pakchunk3-Windows.ucas 11235083312
pakchunk3-Windows.utoc 16996390
pakchunk4-Windows.pak 1119658
pakchunk4-Windows.sig 600
pakchunk4-Windows.ucas 5815148752
pakchunk4-Windows.utoc 15931124
pakchunk5-Windows.pak...
Nao128 • Oct 6, 2026
I tried with the latest version 1.2.3 and it also fails in an instant after entering the NTE Global AES Key.
Could there be a new one on the new patch version?
Could there be a new one on the new patch version?
davidbecam12 • Oct 7, 2026
> I tried with the latest version 1.2.3 and it also fails in an instant after entering the NTE Global AES Key.
> Could there be a new one on the new patch version?
No. The AES key have never changed since the game launched and I can still open with fmodel. I think it would be nice there is a way to integrate fmodel into SCSKiller.
> Could there be a new one on the new patch version?
No. The AES key have never changed since the game launched and I can still open with fmodel. I think it would be nice there is a way to integrate fmodel into SCSKiller.
BlueHeisenberg • Oct 8, 2026
Thanks for the file list!
1.2.4 takes a key when it opens any of the game's encrypted files, not only the first (found by @dkflint723).
Please update and enter the key again, and tell me if it's still refused.
One thing to expect on AMD: an anti-cheat DirectX 12 game needs a community recording there, since its anti-cheat blocks yours.
Without one, the game shows "Not supported" with that reason, even once the key works.
1.2.4 takes a key when it opens any of the game's encrypted files, not only the first (found by @dkflint723).
Please update and enter the key again, and tell me if it's still refused.
One thing to expect on AMD: an anti-cheat DirectX 12 game needs a community recording there, since its anti-cheat blocks yours.
Without one, the game shows "Not supported" with that reason, even once the key works.
SaaS Metrics