Skip to content

Make "All Guns in Solo" cheat work in multiplayer#443

Open
blaiz wants to merge 1 commit intofgsfdsfgs:portfrom
blaiz:all-guns-cheat-multiplayer
Open

Make "All Guns in Solo" cheat work in multiplayer#443
blaiz wants to merge 1 commit intofgsfdsfgs:portfrom
blaiz:all-guns-cheat-multiplayer

Conversation

@blaiz
Copy link
Copy Markdown

@blaiz blaiz commented May 20, 2024

This one always frustrated me as a kid. Why is "All Guns" restricted to the single player mode? I'm gonna guess to not overload the N64's RAM. Not a problem anymore on PC so let's make "All Guns" work for all players in all modes. This works for co-op and combat simulator (and probably counter-op too, I didn't test).

We could potentially refine this further to exclude the "Psychosis Gun" in Combat Simulator since it doesn't seem useful there (I didn't test its effect).

Screenshot 2024-05-19 202037

TODO:

  • Change string from "All Guns in Solo" to just "All Guns". I couldn't figure out how to do that. I tried changing the strings in the json asset files but that didn't work. Does anyone know how to do that?

setCurrentPlayerNum(prevplayernum);
break;
case CHEAT_ALLGUNS:
#ifndef PLATFORM_N64
Copy link
Copy Markdown
Author

@blaiz blaiz May 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to make this work in Combat Simulator? I think so, let the user decide. But we could easily turn off that part of the cheat by adding back if (g_Vars.normmplayerisrunning == false) {

@blaiz blaiz force-pushed the all-guns-cheat-multiplayer branch from 155a0c2 to d7c4843 Compare May 25, 2024 00:28
@smashbro596
Copy link
Copy Markdown

i'm trying to get this working but every time i download the fork it doesn't carry over any of your changes

@blaiz
Copy link
Copy Markdown
Author

blaiz commented Jul 10, 2024

Are you in the right branch in my fork?

@smashbro596
Copy link
Copy Markdown

how do i tell it to build your branch? i wanted the branch with all your changes .

@blaiz
Copy link
Copy Markdown
Author

blaiz commented Jul 10, 2024

Ah i see. I have a branch called “all-changes”. You should switch to that one and build that codebase following the instructions in the readme here. That works for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants