https://hack64.net/ Fri, 17 Apr 2026 13:21:39 +0000 MyBB https://hack64.net/Thread-Ai Sun, 25 May 2025 03:44:31 +0000 https://hack64.net/Thread-Ai
Why would anyone bring some robot into their house too let alone from some random user digitally.

What do you folks say? Would you rely on a bot android from someone you are unfamiliar with?

I know tech giants like Meta, Amazon, and Standard Unions are working on a platform for this, although I am not sure if I would trust these businesses in my house.]]>
Why would anyone bring some robot into their house too let alone from some random user digitally.

What do you folks say? Would you rely on a bot android from someone you are unfamiliar with?

I know tech giants like Meta, Amazon, and Standard Unions are working on a platform for this, although I am not sure if I would trust these businesses in my house.]]> https://hack64.net/Thread-Luigi64 Tue, 07 Mar 2023 20:38:11 +0000 https://hack64.net/Thread-Luigi64 I Made A Luigi64 Rom Hack In HackerSM64 (It's Like A New Decomp Repo It's Hard To Explain) I Added Attachment (Attachment Has Patch Download For Luigi64)

---

If You Don't See The Attachment (I Don't) Here It Is On Google Drive: https://drive.google.com/file/d/19juCHrW...-srdv/view]]> I Made A Luigi64 Rom Hack In HackerSM64 (It's Like A New Decomp Repo It's Hard To Explain) I Added Attachment (Attachment Has Patch Download For Luigi64)

---

If You Don't See The Attachment (I Don't) Here It Is On Google Drive: https://drive.google.com/file/d/19juCHrW...-srdv/view]]> https://hack64.net/Thread-ProjectGMan-Still-In-Development Mon, 27 Feb 2023 17:57:34 +0000 https://hack64.net/Thread-ProjectGMan-Still-In-Development

]]>

]]> https://hack64.net/Thread-In-a-permanent-loop-that-cannot-be-exited-Verify-ROM-and-ROM-Settings Fri, 10 Dec 2021 12:15:55 +0000 https://hack64.net/Thread-In-a-permanent-loop-that-cannot-be-exited-Verify-ROM-and-ROM-Settings So today, I was busy making a sm64 ROM hack just because I was bored, and it worked to start for a while, but today, when I tried to launch my ROM hack, a message came on the screen saying "In a permanent loop that cannot be exited, Verify ROM and ROM Settings"


If somebody has a fix for this error, please reply ASAP.


Programs I ROM hack with (incase that helps): SM64 Text Manager, Quad64 and N64 Sound Tool.
Emulator I use: Project 64


Thanks! - Artorol]]> So today, I was busy making a sm64 ROM hack just because I was bored, and it worked to start for a while, but today, when I tried to launch my ROM hack, a message came on the screen saying "In a permanent loop that cannot be exited, Verify ROM and ROM Settings"


If somebody has a fix for this error, please reply ASAP.


Programs I ROM hack with (incase that helps): SM64 Text Manager, Quad64 and N64 Sound Tool.
Emulator I use: Project 64


Thanks! - Artorol]]> https://hack64.net/Thread-Importing-Blender-File-into-Mod-Manager-I-need-to-replace-some-NPC-Models Mon, 01 Nov 2021 23:49:46 +0000 https://hack64.net/Thread-Importing-Blender-File-into-Mod-Manager-I-need-to-replace-some-NPC-Models
How can I use Mod Manger to relace the models for the characters listed above?

The only tutorial that I could find about this is this: https://www.youtube.com/watch?v=xtgMXFeVHuQ
But this tutorial dose not show what model he is importing into Rom Manager or How the model was made, and what software was used to create the model.

Any advise will be appreciated!]]>
How can I use Mod Manger to relace the models for the characters listed above?

The only tutorial that I could find about this is this: https://www.youtube.com/watch?v=xtgMXFeVHuQ
But this tutorial dose not show what model he is importing into Rom Manager or How the model was made, and what software was used to create the model.

Any advise will be appreciated!]]> https://hack64.net/Thread-Replacing-the-black-Bob-omb-model-Please-help Tue, 19 Oct 2021 02:25:36 +0000 https://hack64.net/Thread-Replacing-the-black-Bob-omb-model-Please-help
For my rom hacking project, I need to replace the models of some of the enemies in the game, with custom models. While replacing the models for Mario, Goomba and King Bob-omb was simple enough, using the instructions from these videos.

https://youtu.be/2esvnWE3QsE
https://youtu.be/hsRK8mzbABg

I need extra help replacing the model for Bob-omb. The first attempt, Ubuntu gave me an error that said something along the lines of "No reference to bobomb_buddy_geo". So then I looked at the Fast 64 menus, and the menu for the actor exporter told me save the model in a separate folder if a Geo file contains 2 objects. (The bob-omb geo file contains the geo data for both Black bob-ombs and Bob-omb Buddies). After exporting the model to a new folder and compiling, Ubuntu gave me these errors. 

"build/us/actors/common0_geo.0: (data+0x65c): undefined reference to 'bobomb_seg8_dl_08022D08'
build/us/actors/common0_geo.0: (data+0x684): undefined reference to 'bobomb_seg8_dl_08022D08'"

There was a 3rd and final attempt before craving in to my inherit need to ask for help - but I got the same errors. I used the DL Exporter tool to save the model's header.h and model.inc.c files to a folder where I keep all of the assets for my rom hacking project. seemingly I could put the contents of the header.h file in a group file that's in the .h format. and I could place the contents of the model inc file in the bob-omb's model inc file, similar to how you'd replace the title screen logo in this tutorial. I feel like this is the way I have to replace the black bob-omb model, but I could be wrong. 

https://youtu.be/EqJde2Hh340

Any attempt to compile the game  after the model was exported after that last attempt would not let the level where the bob-omb object was put in, not change the level. So the Bob-omb would not spawn as if the level itself was never edited. 

I've tried everything that I have learned and unfortunately none of those things that I've learned worked, but has seemingly gotten me closer to success (maybe). 

This is where I am stuck, the point to where I need to ask for help. Any advice will be appreciated. 

My apologies for poor grammar, it is currently 10:22 PM (the dead of night) and I just feel tired and exhausted from working on this project all day.

Tools/ software I am Using:
Blender w/ Fast64 plugin
Visual Studio Code
Notepad++
Project 64]]>
For my rom hacking project, I need to replace the models of some of the enemies in the game, with custom models. While replacing the models for Mario, Goomba and King Bob-omb was simple enough, using the instructions from these videos.

https://youtu.be/2esvnWE3QsE
https://youtu.be/hsRK8mzbABg

I need extra help replacing the model for Bob-omb. The first attempt, Ubuntu gave me an error that said something along the lines of "No reference to bobomb_buddy_geo". So then I looked at the Fast 64 menus, and the menu for the actor exporter told me save the model in a separate folder if a Geo file contains 2 objects. (The bob-omb geo file contains the geo data for both Black bob-ombs and Bob-omb Buddies). After exporting the model to a new folder and compiling, Ubuntu gave me these errors. 

"build/us/actors/common0_geo.0: (data+0x65c): undefined reference to 'bobomb_seg8_dl_08022D08'
build/us/actors/common0_geo.0: (data+0x684): undefined reference to 'bobomb_seg8_dl_08022D08'"

There was a 3rd and final attempt before craving in to my inherit need to ask for help - but I got the same errors. I used the DL Exporter tool to save the model's header.h and model.inc.c files to a folder where I keep all of the assets for my rom hacking project. seemingly I could put the contents of the header.h file in a group file that's in the .h format. and I could place the contents of the model inc file in the bob-omb's model inc file, similar to how you'd replace the title screen logo in this tutorial. I feel like this is the way I have to replace the black bob-omb model, but I could be wrong. 

https://youtu.be/EqJde2Hh340

Any attempt to compile the game  after the model was exported after that last attempt would not let the level where the bob-omb object was put in, not change the level. So the Bob-omb would not spawn as if the level itself was never edited. 

I've tried everything that I have learned and unfortunately none of those things that I've learned worked, but has seemingly gotten me closer to success (maybe). 

This is where I am stuck, the point to where I need to ask for help. Any advice will be appreciated. 

My apologies for poor grammar, it is currently 10:22 PM (the dead of night) and I just feel tired and exhausted from working on this project all day.

Tools/ software I am Using:
Blender w/ Fast64 plugin
Visual Studio Code
Notepad++
Project 64]]> https://hack64.net/Thread-Strange-SM64-Decomp-Error-Please-Help-me Fri, 08 Oct 2021 01:23:04 +0000 https://hack64.net/Thread-Strange-SM64-Decomp-Error-Please-Help-me
src/game/level_update.c: In function 'init_level':
src/game/level_update.c:1322:1: error: expected declaration or statement at end of input
 1322 | }
         | ^

The error has nothing to do with the code the page told me to edit, and I have no clue on how to fix it! The error has something to do with a formatting issue revolving around missing brackets (These symbols: {}), but there is no missing or out of place brackets, so what's causing the error and preventing me from compiling the rom? 

Tweaks Page I am referring too:
https://hack64.net/wiki/doku.php?id=supe...comp_tweak

The Romhacking Tools I am using:
Blender
Fast64
SM64 Decomp
Ubuntu]]>
src/game/level_update.c: In function 'init_level':
src/game/level_update.c:1322:1: error: expected declaration or statement at end of input
 1322 | }
         | ^

The error has nothing to do with the code the page told me to edit, and I have no clue on how to fix it! The error has something to do with a formatting issue revolving around missing brackets (These symbols: {}), but there is no missing or out of place brackets, so what's causing the error and preventing me from compiling the rom? 

Tweaks Page I am referring too:
https://hack64.net/wiki/doku.php?id=supe...comp_tweak

The Romhacking Tools I am using:
Blender
Fast64
SM64 Decomp
Ubuntu]]> https://hack64.net/Thread-Black-screen-when-entering-castle Wed, 08 Sep 2021 05:31:06 +0000 https://hack64.net/Thread-Black-screen-when-entering-castle When I enter the castle it doesn't use the inside castle level instead it just uses a black screen, I'm using Mupen64 0.5.1, What emulator can prevent that? ]]> When I enter the castle it doesn't use the inside castle level instead it just uses a black screen, I'm using Mupen64 0.5.1, What emulator can prevent that? ]]> https://hack64.net/Thread-After-Applying-Patch-or-Changing-Textures-In-A-Rom Wed, 04 Aug 2021 16:33:18 +0000 https://hack64.net/Thread-After-Applying-Patch-or-Changing-Textures-In-A-Rom https://hack64.net/Thread-How-To-Detect-SM64-ROM-Versions-In-C Sun, 04 Jul 2021 03:04:00 +0000 https://hack64.net/Thread-How-To-Detect-SM64-ROM-Versions-In-C {
// Read byte by byte so endian-ness is irrelevant
    fseek(rom, 0, SEEK_SET);
// 59th byte starts region ID
    fseek(rom, 59, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
    
    if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x4A) //NSMJ in hex, both OG japan and shindou ROMs contain this
    {
    fseek(rom, 0, SEEK_SET);
// 35th byte starts ER M in OG japan and ERMA in shindou, how convenient. This is because shindou says the game name is SUPERMARIO64, all other versions say SUPER MARIO 64
    fseek(rom, 35, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
        if(rom_byte_1 == 0x45 && rom_byte_2 == 0x52 && rom_byte_3 == 0x20 && rom_byte_4 == 0x4D) //ER M in hex
        {
        printf("Validated ROM as .z64 Japan\n");
        }
        else if(rom_byte_1 == 0x45 && rom_byte_2 == 0x52 && rom_byte_3 == 0x4D && rom_byte_4 == 0x41) //ERMA in hex
        {
        printf("Validated ROM as .z64 Shindou Edition\n");
        }
        else
        {
// Should be impossible
        printf("Error: Can not figure out if this is the original Japan or the Shindou Edition ROM!\n");
        end_input = TRUE;
        }
    }
    else if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x45) //NSMJ in hex
    {
    printf("Validated ROM as .z64 USA\n");
    }
    else if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x50) //NSME in hex
    {
    printf("Validated ROM as .z64 PAL\n");
    }
    else
    {
    fseek(rom, 0, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
        if(rom_byte_1 == 0x37 && rom_byte_2 == 0x80 && rom_byte_3 == 0x40 && rom_byte_4 == 0x12) // First 4 bytes of a little endian sm64 rom which is NOT supported
        {
        printf("This is a little-endian, .n64 format SM64 ROM file. SM64GSW requires a big-endian, .z64 format SM64 ROM file.\n");
        end_input = TRUE;
        }
        else
        {
        printf("Error: This does not appear to be a valid SM64 ROM!\n");
        end_input = TRUE;
        }
    }
}

This is a little snippet of the SM64GSW v1.4 I'm working on, and I thought this could be useful to others. The above code was figured out by myself using a hex editor on various .z64 (A.K.A Big-Endian PROPER file format ROMs). This is 3-BSD licensed as SM64GSW is 3-BSD licensed (but does not include this code yet) https://github.com/alex-free/sm64gsw . Of course simple file markers are not copyrightable so feel free to use them in other software, no matter the license ]]> {
// Read byte by byte so endian-ness is irrelevant
    fseek(rom, 0, SEEK_SET);
// 59th byte starts region ID
    fseek(rom, 59, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
    
    if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x4A) //NSMJ in hex, both OG japan and shindou ROMs contain this
    {
    fseek(rom, 0, SEEK_SET);
// 35th byte starts ER M in OG japan and ERMA in shindou, how convenient. This is because shindou says the game name is SUPERMARIO64, all other versions say SUPER MARIO 64
    fseek(rom, 35, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
        if(rom_byte_1 == 0x45 && rom_byte_2 == 0x52 && rom_byte_3 == 0x20 && rom_byte_4 == 0x4D) //ER M in hex
        {
        printf("Validated ROM as .z64 Japan\n");
        }
        else if(rom_byte_1 == 0x45 && rom_byte_2 == 0x52 && rom_byte_3 == 0x4D && rom_byte_4 == 0x41) //ERMA in hex
        {
        printf("Validated ROM as .z64 Shindou Edition\n");
        }
        else
        {
// Should be impossible
        printf("Error: Can not figure out if this is the original Japan or the Shindou Edition ROM!\n");
        end_input = TRUE;
        }
    }
    else if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x45) //NSMJ in hex
    {
    printf("Validated ROM as .z64 USA\n");
    }
    else if(rom_byte_1 == 0x4E && rom_byte_2 == 0x53 && rom_byte_3 == 0x4D && rom_byte_4 == 0x50) //NSME in hex
    {
    printf("Validated ROM as .z64 PAL\n");
    }
    else
    {
    fseek(rom, 0, SEEK_SET);
    fread(&rom_byte_1, 1, 1, rom);
    fread(&rom_byte_2, 1, 1, rom);
    fread(&rom_byte_3, 1, 1, rom);
    fread(&rom_byte_4, 1, 1, rom);
        if(rom_byte_1 == 0x37 && rom_byte_2 == 0x80 && rom_byte_3 == 0x40 && rom_byte_4 == 0x12) // First 4 bytes of a little endian sm64 rom which is NOT supported
        {
        printf("This is a little-endian, .n64 format SM64 ROM file. SM64GSW requires a big-endian, .z64 format SM64 ROM file.\n");
        end_input = TRUE;
        }
        else
        {
        printf("Error: This does not appear to be a valid SM64 ROM!\n");
        end_input = TRUE;
        }
    }
}

This is a little snippet of the SM64GSW v1.4 I'm working on, and I thought this could be useful to others. The above code was figured out by myself using a hex editor on various .z64 (A.K.A Big-Endian PROPER file format ROMs). This is 3-BSD licensed as SM64GSW is 3-BSD licensed (but does not include this code yet) https://github.com/alex-free/sm64gsw . Of course simple file markers are not copyrightable so feel free to use them in other software, no matter the license ]]> https://hack64.net/Thread-More-Objects-Patch-4-Future-Patches Tue, 23 Mar 2021 03:49:35 +0000 https://hack64.net/Thread-More-Objects-Patch-4-Future-Patches
Note that this only works for SM64 ROM Manager, and not SM64 Editor or Decomp. That said I may probably port this to Decomp and Bowser's Blueprints eventually.  (I already ported Boo Key/Door and Sunshine Dive Last year to decomp)
It is also 90% backwards compatible with MOP 1-3 (ROM Manager Versions), minus Purple ! Box and Beta Shells

It includes 6 new objects for SM64:
Name - Is Global? - Model - Behavior
Boo Key - Non-Global - 0x55 - 0x13001744
Boo Door - Global - Works with any door model - 0x13000F14
Red Koopa - Non-Global - Refer to included docs or set to 0 - Koopa Behavior
Red Koopa Shell - Global - Refer to included docs or set to 0 - Koopa Shell Behavior
Purple ! Box - Not Global? - Refer to included docs or set to 0 - ! Box Behavior (Bparam 2 = 4)
Creeper (Aw Man) - Global - Refer to included docs or set to 0 - 0x130022D8

Release Trailer/Download: 





I've contacted Pilz to see if he can integrate this into RM as well, so it should work with Global Object Bank soon and what not. If anyone has any ideas for future patches I could make HMU with some ideas, such as a More Collisions Patch or a More Powerups/ ! Blocks Patch, etc, etc.]]>
Note that this only works for SM64 ROM Manager, and not SM64 Editor or Decomp. That said I may probably port this to Decomp and Bowser's Blueprints eventually.  (I already ported Boo Key/Door and Sunshine Dive Last year to decomp)
It is also 90% backwards compatible with MOP 1-3 (ROM Manager Versions), minus Purple ! Box and Beta Shells

It includes 6 new objects for SM64:
Name - Is Global? - Model - Behavior
Boo Key - Non-Global - 0x55 - 0x13001744
Boo Door - Global - Works with any door model - 0x13000F14
Red Koopa - Non-Global - Refer to included docs or set to 0 - Koopa Behavior
Red Koopa Shell - Global - Refer to included docs or set to 0 - Koopa Shell Behavior
Purple ! Box - Not Global? - Refer to included docs or set to 0 - ! Box Behavior (Bparam 2 = 4)
Creeper (Aw Man) - Global - Refer to included docs or set to 0 - 0x130022D8

Release Trailer/Download: 





I've contacted Pilz to see if he can integrate this into RM as well, so it should work with Global Object Bank soon and what not. If anyone has any ideas for future patches I could make HMU with some ideas, such as a More Collisions Patch or a More Powerups/ ! Blocks Patch, etc, etc.]]> https://hack64.net/Thread-models-and-animations Sat, 20 Mar 2021 16:41:27 +0000 https://hack64.net/Thread-models-and-animations

I want to import the unused star dance and other animations, i want the beta penguin, if anyone here can help me, please reply to me.]]>

I want to import the unused star dance and other animations, i want the beta penguin, if anyone here can help me, please reply to me.]]> https://hack64.net/Thread-SM64GSW-Updated-For-Linux-Windows-Write-GameShark-Codes-To-USA-ROM-Modify-CIC-Check Wed, 13 Jan 2021 07:34:49 +0000 https://hack64.net/Thread-SM64GSW-Updated-For-Linux-Windows-Write-GameShark-Codes-To-USA-ROM-Modify-CIC-Check
You can write a list of GameShark codes in a txt file, and SM64GSW can write each code line by line into a ROM file. Alternatively, you can type each code into SM64GSW.

As of version 1.1, Linux x86, Linux x86_64, and Windows 95-Windows 10 builds are available on the official web page (which also contains the complete documentation.








]]>
You can write a list of GameShark codes in a txt file, and SM64GSW can write each code line by line into a ROM file. Alternatively, you can type each code into SM64GSW.

As of version 1.1, Linux x86, Linux x86_64, and Windows 95-Windows 10 builds are available on the official web page (which also contains the complete documentation.








]]> https://hack64.net/Thread-Lower-the-100-coins-star Sat, 28 Nov 2020 11:14:49 +0000 https://hack64.net/Thread-Lower-the-100-coins-star https://hack64.net/Thread-Invisible-walls-Flickering-Textures Tue, 24 Nov 2020 19:12:27 +0000 https://hack64.net/Thread-Invisible-walls-Flickering-Textures
First is that when I build a ramp with a similar setup to the one at the start of Bob-omb battlefield (floor underneath ramp) I always encounter an invisible wall in game while walking up or down it.
I've tried extended boundaries with the death floor but this doesn't fix it, it happens with flat planes and cubes regardless within a certain height.

The second , lesser issue I'm having is that when adding textures such as windows to a building it will flicker and show the wall behind it from a distance in game.
I notice this is an inherent problem from extending the ROM but what is the best solution people have found to stop it showing up?]]>
First is that when I build a ramp with a similar setup to the one at the start of Bob-omb battlefield (floor underneath ramp) I always encounter an invisible wall in game while walking up or down it.
I've tried extended boundaries with the death floor but this doesn't fix it, it happens with flat planes and cubes regardless within a certain height.

The second , lesser issue I'm having is that when adding textures such as windows to a building it will flicker and show the wall behind it from a distance in game.
I notice this is an inherent problem from extending the ROM but what is the best solution people have found to stop it showing up?]]> https://hack64.net/Thread-Decomp Wed, 18 Nov 2020 16:26:35 +0000 https://hack64.net/Thread-Decomp https://hack64.net/Thread-Incorrect-depth-rendering--303 Tue, 10 Nov 2020 16:29:05 +0000 https://hack64.net/Thread-Incorrect-depth-rendering--303
I've begun using blender and the ROM manager, I feel I have a grip on using blender for basic geometry and texturing (using original Mario 64 textures)

I've successfully imported levels, however there is an issue I can't currently figure out where all the textures can be seen, regardless of if they are behind a wall, including Mario's model, which disappears when he moves over a texture besides his shadow.

I have made sure all faces are pointing out and triangulated but beyond that right now I am lost.

I've watched a number of tutorials but none I found describe or resolve this problem.

Can somebody put me out of my misery with this?]]>
I've begun using blender and the ROM manager, I feel I have a grip on using blender for basic geometry and texturing (using original Mario 64 textures)

I've successfully imported levels, however there is an issue I can't currently figure out where all the textures can be seen, regardless of if they are behind a wall, including Mario's model, which disappears when he moves over a texture besides his shadow.

I have made sure all faces are pointing out and triangulated but beyond that right now I am lost.

I've watched a number of tutorials but none I found describe or resolve this problem.

Can somebody put me out of my misery with this?]]> https://hack64.net/Thread-Bowser-s-Church-Release Sat, 10 Oct 2020 15:28:51 +0000 https://hack64.net/Thread-Bowser-s-Church-Release Do you save the church, or destroy it? It is your choice, my friend. 
Explore 8 New Areas (2 Levels, 6 Sub-Areas), coupled with new music and textures, to bring in a fresh new look at the Nintendo 64 Classic.
Here is a video of me playing it! https://www.youtube.com/watch?v=zL056IW1rWo

Wanna play it? Here is the Download Link! Just click "DOWNLOAD ALL", and then follow the directions in README.txt, and you will be on your way to enjoying the enriching experience of "Bowser's Church"!
https://drive.google.com/drive/folders/1...sp=sharing


After playing it, I would greatly appreciate it if you could give feedback! Click on this Google Form link, and then fill it out if you feel so inclined! 
https://docs.google.com/forms/d/e/1FAIpQ...sp=sf_link


  Bowser's Church - Project64 2.3.2.202 10_8_2020 4_21_49 PM.png (Size: 197.73 KB / Downloads: 1442)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_13_49 PM.png (Size: 154.31 KB / Downloads: 1830)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_17_50 PM.png (Size: 138.24 KB / Downloads: 1395)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_15_20 PM.png (Size: 191.67 KB / Downloads: 1027)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_16_05 PM.png (Size: 225.69 KB / Downloads: 964) ]]> Do you save the church, or destroy it? It is your choice, my friend. 
Explore 8 New Areas (2 Levels, 6 Sub-Areas), coupled with new music and textures, to bring in a fresh new look at the Nintendo 64 Classic.
Here is a video of me playing it! https://www.youtube.com/watch?v=zL056IW1rWo

Wanna play it? Here is the Download Link! Just click "DOWNLOAD ALL", and then follow the directions in README.txt, and you will be on your way to enjoying the enriching experience of "Bowser's Church"!
https://drive.google.com/drive/folders/1...sp=sharing


After playing it, I would greatly appreciate it if you could give feedback! Click on this Google Form link, and then fill it out if you feel so inclined! 
https://docs.google.com/forms/d/e/1FAIpQ...sp=sf_link


  Bowser's Church - Project64 2.3.2.202 10_8_2020 4_21_49 PM.png (Size: 197.73 KB / Downloads: 1442)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_13_49 PM.png (Size: 154.31 KB / Downloads: 1830)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_17_50 PM.png (Size: 138.24 KB / Downloads: 1395)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_15_20 PM.png (Size: 191.67 KB / Downloads: 1027)

  Bowser's Church - Project64 2.3.2.202 10_9_2020 4_16_05 PM.png (Size: 225.69 KB / Downloads: 964) ]]> https://hack64.net/Thread-SM64GSW-Write-GameShark-Codes-To-USA-ROM Mon, 14 Sep 2020 04:08:40 +0000 https://hack64.net/Thread-SM64GSW-Write-GameShark-Codes-To-USA-ROM Edit: I will no longer be using this account, my new account is alex_free

and this project has moved to GitHub.

SM64GSW by Alex Free

==Info==
An open source (3-BSD) console program that can write GameShark/Xploder64 codes directly into a
Super Mario 64 USA ROM.

SM64GSW performs Messiaen64's manual hex editing method written at https://sites.google.com/site/messiaen64...hark-codes in software automatically so you don't
have to hex edit your SM64 ROM manually.

==Requirements==
- The Windows version is a 32-bit binary compatible with Windows 95 and above.
- Windows 95 requires MSVCR.dll (Windows 95 OSR2.5 and above already include it). One way you can get this is by updating Internet Explorer to version 4.0.
- A Super Mario 64 USA ROM in .z64 or .N64 (N64 SDK) format. The .n64 and .v64 formats are not supported.

==Usage==

1) Start SM64GSW in one of 2 different ways.

Command line method:
- Open cmd.exe or command.com.
- Execute the 'sm64gsw' command with your ROM as the argument. For example, the complete command could be
"sm64gsw C:\sm64.z64".

Windows Explorer method:
- Drag your ROM file on top of the sm64gsw.exe file.

2) Select your code input preference at the input selection menu.

SM64GSW can write codes contained in a txt file of your choosing, or you can input them with the keyboard.
In keyboard mode after each code is entered, it will be written to the ROM and you will be asked if you want to enter another code or to exit.
In file mode, you will be prompted to enter the file path (that must not contain spaces!) for a txt file containing codes. The txt file
can contain a code or multiple codes, one code per line. The file 'gs.txt' in this release is an example of this.
You can manually type in the file path, drag and drop the rom into the SM64GSW.exe window, or copy - paste the file path if in cmd.exe.

If SM64GSW tells you 'Attention: At least one code invalidates the internal ROM checksum, run checksum64
on your ROM before playing' you MUST run the 'chksum64' program on the ROM file after writing your codes. You
can do this by dropping your newly modified ROM on top of the chksum64 executable (Chksum64 is written by Andreas Sterbenz).

3) Test the ROM.

==What Codes Work?==

There is an incomplete list of some codes that work in the file named 'known_working_codes.txt' in this release.

Supported RAM range is 80246000-80333000. The 3rd-8th digits of a code must be a hexadecimal value in the
range of 246000-333000 to work.

Not all N64 GameShark/Xploder64 code types are supported. This is due to certain code types not translating
into just hex writes for various reasons, such as codes that:
- Require physical hardware (like a GS button).
- Perform live checks and or dynamic modification.
- Simply not being appliable (Expansion pack releated, non-Super Mario 64 security chip related).

Code types are defined by the first 2 hexadecimal digits of a code. For example, in the level select code
'A032D58C 0001' 'A0' is the code type. For multi-line codes, if any lines contain an incompatible code type
the entire code can not be written into ROM. See the table below for specifics.

Supported codes include 80, A0, F0, 81, A1, and 2A. 80, A0, and F0 must be in the X0XXXXXX-00XX format.

==License==
- This is open source software, released under the 3-Clause BSD license (read license.txt). It **should** compile
and work on other little-endian Operating Systems.

==Changelog==
==Version 1.0.1==
- Fixes a bug which prevented codes from being entered by the keyboard, after an invalid code was entered.
[color=var(--color-text-secondary)][url=https://github.com/][/url]
[/color]]]> Edit: I will no longer be using this account, my new account is alex_free

and this project has moved to GitHub.

SM64GSW by Alex Free

==Info==
An open source (3-BSD) console program that can write GameShark/Xploder64 codes directly into a
Super Mario 64 USA ROM.

SM64GSW performs Messiaen64's manual hex editing method written at https://sites.google.com/site/messiaen64...hark-codes in software automatically so you don't
have to hex edit your SM64 ROM manually.

==Requirements==
- The Windows version is a 32-bit binary compatible with Windows 95 and above.
- Windows 95 requires MSVCR.dll (Windows 95 OSR2.5 and above already include it). One way you can get this is by updating Internet Explorer to version 4.0.
- A Super Mario 64 USA ROM in .z64 or .N64 (N64 SDK) format. The .n64 and .v64 formats are not supported.

==Usage==

1) Start SM64GSW in one of 2 different ways.

Command line method:
- Open cmd.exe or command.com.
- Execute the 'sm64gsw' command with your ROM as the argument. For example, the complete command could be
"sm64gsw C:\sm64.z64".

Windows Explorer method:
- Drag your ROM file on top of the sm64gsw.exe file.

2) Select your code input preference at the input selection menu.

SM64GSW can write codes contained in a txt file of your choosing, or you can input them with the keyboard.
In keyboard mode after each code is entered, it will be written to the ROM and you will be asked if you want to enter another code or to exit.
In file mode, you will be prompted to enter the file path (that must not contain spaces!) for a txt file containing codes. The txt file
can contain a code or multiple codes, one code per line. The file 'gs.txt' in this release is an example of this.
You can manually type in the file path, drag and drop the rom into the SM64GSW.exe window, or copy - paste the file path if in cmd.exe.

If SM64GSW tells you 'Attention: At least one code invalidates the internal ROM checksum, run checksum64
on your ROM before playing' you MUST run the 'chksum64' program on the ROM file after writing your codes. You
can do this by dropping your newly modified ROM on top of the chksum64 executable (Chksum64 is written by Andreas Sterbenz).

3) Test the ROM.

==What Codes Work?==

There is an incomplete list of some codes that work in the file named 'known_working_codes.txt' in this release.

Supported RAM range is 80246000-80333000. The 3rd-8th digits of a code must be a hexadecimal value in the
range of 246000-333000 to work.

Not all N64 GameShark/Xploder64 code types are supported. This is due to certain code types not translating
into just hex writes for various reasons, such as codes that:
- Require physical hardware (like a GS button).
- Perform live checks and or dynamic modification.
- Simply not being appliable (Expansion pack releated, non-Super Mario 64 security chip related).

Code types are defined by the first 2 hexadecimal digits of a code. For example, in the level select code
'A032D58C 0001' 'A0' is the code type. For multi-line codes, if any lines contain an incompatible code type
the entire code can not be written into ROM. See the table below for specifics.

Supported codes include 80, A0, F0, 81, A1, and 2A. 80, A0, and F0 must be in the X0XXXXXX-00XX format.

==License==
- This is open source software, released under the 3-Clause BSD license (read license.txt). It **should** compile
and work on other little-endian Operating Systems.

==Changelog==
==Version 1.0.1==
- Fixes a bug which prevented codes from being entered by the keyboard, after an invalid code was entered.
[color=var(--color-text-secondary)][url=https://github.com/][/url]
[/color]]]> https://hack64.net/Thread-Trouble-Adding-Certain-Unique-Objects-in-Quad64 Sun, 19 Jul 2020 02:25:26 +0000 https://hack64.net/Thread-Trouble-Adding-Certain-Unique-Objects-in-Quad64