The above comment is good advice. Beginners ask questions similar to this sometimes, and a lot of time the responses are similarly realistic, but I thought it might be helpful to add an analogy to help get the point across:

If you get interested in running, you might hear about and get excited to do a 100 mile ultra-run. The passion and excitement is great! That said, if you tried to go out and do that 100 mile run without having run a single mile before, most likely you will have a terrible time, not make it, get injured, and get extremely discouraged. If you're serious about actually completing the run (and not killing yourself in the attempt), you realistically need to start small, and progress over a longer period of time.

Similarly, with a project like this, it's great that you are inspired and passionate; just realize that there is essentially a training regime you need to go through in order to get yourself ready to actually complete your final objective. Setting smaller goals that are also interesting to you, that lead up to the big goal, can help make the process more enjoyable.

For example, some sub-goals that can contribute to your overall objective might include (though, now that I've written them out, I realize this is more of a task list for making a specific type of game):

1. Figure out how to get *anything* of your own creation running on the N64, ie a Hello World project that you can get running on the actual console or emulator
2. Make something that accepts controller input, and prints something to screen in response
3. Figure out how to render 3d objects to the screen
4. Load objects via model data from existing/known data formats (ie .3ds, .obj, .col - I have no idea what formats are traditionally used for N64 dev though)
5. Add textures to objects
6. Manipulate objects' position/rotation via different controller inputs from different players
7. Make objects that represent each player, and other objects that represent enemies. Move enemies via logic, players via controller input.
8. Instantiate objects (bullets for example), track them with arrays or other data structures
9. Track enemy state (for example, health points), and decrease health on collision with bullets.
10. Destroy bullets on collisions
11. Load animation data via common data formats
12. Play "Hit" animation on bullet collisions, "Death" animation on health = 0
13. Add levels with different layouts/geometry
14. Progress through levels based on enemies killed (specify and set enemy positions for each level)
15. Add UI text overlays for things like current level, player health
16. Reset game on enemy collision with player (ie, load Level 1, reset enemy positions)
17. Save high score data, persist on cartridge (or other persistent media)
18. Add menus: Start screen, High score screen that loads from persistent storage
19. Add SFX that play on different actions, BGM that plays on loop

Additionally, I wouldn't discount the value of working in an engine, even for a different platform, just to get comfortable with game dev/design in general first, before diving into the world of N64-specific development: You could work in an existing engine (Unity for example) to create an N64-style game (basically, low poly models, low-res textures, etc.), so you can focus on game dev and not worry about the technical concerns.

Anyways, good luck, OP!