News:

Don't forget to visit the main site! There's lots of helpful docs, patches, and more!

Main Menu

M2 Randomizer

Started by liamnajor, September 01, 2018, 06:47:38 AM

Previous topic - Next topic

liamnajor

I made a randomizer. It's browser based, so you don't have to download anything (well, besides the ROM and randomized ROM)

https://liamnajor.github.io/Metroid-2-Randomizer/

I might ad pickup randomizing in the future, but that won't be for a long time, if ever, since objects have to be replaced on an individual basis.

it automatically sets acid damage to 0, so if you need to go forward to get a necessary item, that is an option


Gravity

#1
I never thought I'd see a Metroid 2 randomizer, so congratulations on actually making one. :^_^:

The save button doesn't seem to do anything though. I tried loading a rom, typing a filename, hitting randomize, and then tried to save. Also tried decoding and then hitting save again. Nothing happens. How do you get the randomized rom so you can use it other than on the browser?

Also, being able to automatically include the seed at the end of the filename would be nice.

Edit: It's saving a file on Chrome when I hit randomize. But not Firefox.

Edit 2: What Chrome is saving when you randomize is corrupt anyway.

Used Metroid II - Return of Samus (W) [!].gb

Tried three times but they're always corrupt.

Here's the errors from bgb emulator:

---------------------------
loading rom succeeded with warnings
---------------------------
Unsupported ROM size

Rom size in header does not match actual rom size.

Header checksum fails.

Logo check fails.

ROM checksum fails.

Unsupported cart type: DD

Unsupported RAM size

This rom would not work on a real gameboy.
---------------------------


Edit 3: Okay, if I hit save on Chrome, then it does actually save. And it does put out a valid rom.

I don't know what it's automatically saving when you hit randomize on Chrome. But if you don't put a filename I noticed the automatic save is called "data.bin". Hopefully all that info helps to figure out why it's acting so strange.

Edit 4: Playing a game, acid was still damaging. I know that wasn't supposed to happen so I checked the crc's of the original rom and the randomized ones I got from hitting save in Chrome. All of them had the same crc. It's saving the original rom instead of putting out a randomized one.

Edge behaves the same as Chrome (invalid file when randomizing, saves original unrandomized rom when hitting save).

liamnajor

you're using the wrong ROM. use the one specified on the wiki.

Gravity

#3
I didn't know the wiki listed a rom.

But after checking, it is the same rom as the wiki. It has a slightly different name for some reason. Checking the crc and sha-1, they match the ones on this page which call for the same rom name as the wiki.

Quote---------------------------
Checksum information
---------------------------
Name: Metroid II - Return of Samus (W) [!].gb
Size: 262144 bytes (0 MB)

CRC32: DEE05370

CRC64: 3C57E56F89AE723C

SHA256: 3080BCC2EB9965DE463F5F4E02F0DABBB13B060E1654A18DA8B50948C10AF4A6

SHA1: 74A2FAD86B9A4C013149B1E214BC4600EFB1066D

BLAKE2sp: C6BC7A524DFD72105952C33D5064473916AFA4F9946F1D165D358276ED6A5C57

---------------------------

It seems there's the same rom floating around with several different names, but always the same checksums:
https://www.romhacking.net/hacks/4049/
https://www.romhacking.net/hacks/204/

To avoid rom confusion the wiki definitely needs to list the checksums. It doesn't look like I have an option to edit so I can't put those in myself.


EDIT: I tried hitting decode before hitting randomize, and that saved a valid randomized rom. It's not very intuitive to know you have to hit decode before hitting randomize. I'd suggest putting an explanation about that on the site.

It looks like you've updated something as there's no save button anymore. Just a fyi that it's still only saving in Chrome for some reason. Firefox isn't saving anything when hitting randomize.

One other observation. I'm guessing there's bombs where your shots hit the walls so you can actually get stuff without having bombs. That goes away if you get something like wave beam, so you have no way to bomb anything after that. Plus bomb on beam doesn't help when you need to get through a tunnel where you have to be morphed. As there's no alternative to regular bombs in Metroid II and the areas aren't as connected as other Metroid games, it really might be worth it to have an option to either not randomize bomb location or to start with bombs.

liamnajor

Quote from: Gravity on October 14, 2018, 12:18:09 PM
I didn't know the wiki listed a rom.

But after checking, it is the same rom as the wiki. It has a slightly different name for some reason. Checking the crc and sha-1, they match the ones on this page which call for the same rom name as the wiki.

Quote---------------------------
Checksum information
---------------------------
Name: Metroid II - Return of Samus (W) [!].gb
Size: 262144 bytes (0 MB)

CRC32: DEE05370

CRC64: 3C57E56F89AE723C

SHA256: 3080BCC2EB9965DE463F5F4E02F0DABBB13B060E1654A18DA8B50948C10AF4A6

SHA1: 74A2FAD86B9A4C013149B1E214BC4600EFB1066D

BLAKE2sp: C6BC7A524DFD72105952C33D5064473916AFA4F9946F1D165D358276ED6A5C57

---------------------------

It seems there's the same rom floating around with several different names, but always the same checksums:
https://www.romhacking.net/hacks/4049/
https://www.romhacking.net/hacks/204/

To avoid rom confusion the wiki definitely needs to list the checksums. It doesn't look like I have an option to edit so I can't put those in myself.


EDIT: I tried hitting decode before hitting randomize, and that saved a valid randomized rom. It's not very intuitive to know you have to hit decode before hitting randomize. I'd suggest putting an explanation about that on the site.

It looks like you've updated something as there's no save button anymore. Just a fyi that it's still only saving in Chrome for some reason. Firefox isn't saving anything when hitting randomize.

One other observation. I'm guessing there's bombs where your shots hit the walls so you can actually get stuff without having bombs. That goes away if you get something like wave beam, so you have no way to bomb anything after that. Plus bomb on beam doesn't help when you need to get through a tunnel where you have to be morphed. As there's no alternative to regular bombs in Metroid II and the areas aren't as connected as other Metroid games, it really might be worth it to have an option to either not randomize bomb location or to start with bombs.
Firefox doesn't support some of the javascript that chrome does, so stick with chrome. And I will add what you suggested next time I get a chance/am not working on ROSE, which is a higher priority. I am also working on having the randomizer modify the chunks to make it truly non linear. I only got to area 3, so there is a chance of the ROM breaking as of now. I will get to it at some point, but don't expect it anytime soon(because I'm busy with ROSE, as I said earlier)

trudbol

#5
Awesome idea, thank you for making this as well!

Could you please create a quick documentation with just one working example on how to properly use this? Thanks.

liamnajor

Quote from: trudbol on March 07, 2020, 07:48:01 AM
Awesome idea, thank you for making this as well!

Could you please create a quick documentation with just one working example on how to properly use this? Thanks.
This is long abondoned. It works in it's current state, but it's so old I would honestly just recommend waiting for me to merge this and ROSE's codebase.

MSR1701

Question, is there a Metroid II Randomizer currently in development other than the one mentioned at the beginning of this thread?

liamnajor

Quote from: MSR1701 on July 27, 2020, 03:03:23 PM
Question, is there a Metroid II Randomizer currently in development other than the one mentioned at the beginning of this thread?
Not by me, so that's pretty much no. Hopefully I escape the bog of stagnation this year...