lambdan / cp2077_hiddenpackages Goto Github PK

would be nice to be able to jump around.
maybe a dropdown menu? i think ImGui has that

https://forums.nexusmods.com/index.php?showtopic=10823708/#entry106016653

even after stripping out creation mode, there's probably a lot of crap that can be taken out

To reproduce:

1. collect some "packages1" packages
2. save (in-game)
3. apply & load a different packages file ("test")
4. collect 1 package from "test"
5. apply & load "packages1" again
6. reset progress for "packages1" (clearProgress())

(at this point, userData.collectedPackageIDs only contains 1 from "test")

7. apply & load "test" again
8. collected package spawns again CET overlay says 0 collected
9. (collecting the package again puts it twice in collectedPackageIDs)

i think GameSession has a playthrough id or something that could be used

first need to make a function for figuring out nearest package

then after that just have a spawn when in range and despawn when out of range

spawning all packages at once has been going well so the range threshold can probably be pretty big

for the randomizer

probably doable through Cron

is possible to do through NativeSettings by like toggling a button or something, but it would be kinda janky.
honestly thinking i might just ditch them and hope no one wants to reset progress (or they could do it by removing their session file)

memory leak in GameSession probably

i think its because we both use GameSession. if you have both mods loaded, and DEBUG mode enabled for this mod, you can see that userData collected gets set when loading a save as it should (it loads what packages are collected), but as soon as youre in game it gets set to 0 again (no packages collected). at the same time, you get a "JB mod loaded" message in the console.

probably due to this line: local transform = Game.GetPlayer():GetWorldTransform() in spawnObjectAtPos() ... i'm guessing its using V's rotation

ideally it would be spinning too

random or nearest?

honestly thinking i might just remove it and just have a separate script to generate files for performance testing. figuring out a way to determine if a package is reachable seems pretty impossible right now.