Foohy / jazztronauts

Jazztronauts is a cooperative theft-em-up for Garry's Mod, also known as prop hunt 2.
122 stars 35 forks source link

Cats wont acknowledge props/mission progress #185

Closed benjaminpants closed 1 year ago

benjaminpants commented 1 year ago

Cleared my save data and started playing on the latest version(on the main branch), however, I'm unable to progress, as none of the cats acknowledge my props.

image

(Bartender giving me the "having trouble finding crates" message despite me having enough crates) image

Commenter25 commented 1 year ago

I attempted to replicate this myself, both with cheats and naturally, with the same amount of props, with no luck. Would you be willing to try running the cheat jazz_missions_add 1 and see if you're suddenly able to progress? This will simply add one more to your progress on each of your missions. The oil drum gods will let it slide ;D

benjaminpants commented 1 year ago

Nope, doesn't work. I've tried calling the refresh console commands and despite my best efforts it won't let me progress. I've already tried restarting the file from scratch before creating this issue and this issue persists. I have no clue why this is happening to me specifically, as I have all other addons disabled. (Excluding some local ones, which as far as I know should not be interfering, since I made all of them.)

image

benjaminpants commented 1 year ago

Removed all my local addons to be sure, still not working.

benjaminpants commented 1 year ago

Looks like I have a duplicate instance of Jazztronauts installed somewhere, as I deleted my local copy and I'm currently unsubscribed from the workshop copy, so this looks like a problem on my end, thanks for responding quickly though!

EDIT: putting this here incase anyone has the same problem, i left jazztronauts in my mount.cfg

benjaminpants commented 1 year ago

Re-opening issue, as after clearing the extra copy it still doesn't work. The version on the workshop, does work properly however, so this is a bug with the version on the repo.

Commenter25 commented 1 year ago

Gotcha, if you find out anything more just mention it, I'll try again in the morning, maybe I messed something up myself.

Just want to say thank you for giving such thorough details! It's greatly appreciated and makes things far easier :D

benjaminpants commented 1 year ago

When I was in the workshop version, I completed Singer's mission. I switched back to the github version of the repo without completing the cutscene, and it appears like the cutscene and I was able to get the next mission(though I was unable to complete it). Seems like specifically completing a mission is broken?

And, no problem with providing details, I love this gamemode for one, and I know as someone who also has a few projects of their own, that vague issue reports are annoying. image

Commenter25 commented 1 year ago

I'm sorry, I keep trying, but I really can't replicate this; even after unsubscribing from the workshop addon and clearing the workshop cache from steamapps/workshop/content/4000/1452613192, and even completely decoupling the addon from the workshop by removing the ID from gamemodes/jazztronauts/jazztronauts.txt. All things which should eliminate possibility of duplicate installs overriding anything. I can't think of anything else to try.

I doubt it's relevant, but what operating system are you running, and which branch of Gmod are you on? Can you try the things I mentioned above and see if something miraculously changes?

benjaminpants commented 1 year ago

Windows 10 Pro 21H2, and I'm on the standard branch of Garry's Mod. Both of the things you suggested hasn't fixed the problem for me. In a few hours when I have the time I'm going to try to manually download every commit inbetween the workshop version to the latest commit, and see which one causes it to break. I appreciate your patience and I hope we can figure this out.

benjaminpants commented 1 year ago

Weird, looks like the issue fixed itself... strange. If it occurs again and I can track down which commit is causing it I'll re-open this issue but I appreciate the time you spent trying to help, apologies for any wasted time trying to debug this weird bug.