Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Harry Potter: Find Scabbers quits itself or can't get past the main menu #18

Open
TwoSpacesSG opened this issue Oct 6, 2024 · 1 comment

Comments

@TwoSpacesSG
Copy link

TwoSpacesSG commented Oct 6, 2024

This game is pain.

4 versions exist:

  • Nokia 176x208: this version quits itself after the loading title screen. Previously it used to freeze on said screen.
  • Motorola Triplets 176x182: this version quits itself after the loading title screen. Previously it was playable but with glitches.
  • Nokia 96x65: this version goes into the LCDUI menu, but you can't get past the first screen because it constantly resets itself to the first menu screen. Out of the emus it only works in J2ME Loader (maybe just by miracle).
  • Nokia 128x128: this version quits itself after the loading title screen. Previously you couldn't go past the LCDUI menu because of the resetting issue.

I've noticed some things while observing the 96x65 and 128x128 versions in a decompiler.

  1. The game looks at the microedition.platform and whether it's "Nokia6230". I don't know how to change this property in freej2me (it would be helpful for a few games) but in KEmnnmod changing it to match does not fix the menu resetting issue.
  2. The game looks for the manifest/jad properties "JumpMenuHook: Enable" and "JumpMenuItemText: ", the former makes an option appear in the main menu, the latter sets any text for it. I suspect this was for a "get more games" option that would be set via the JAD, but regardless this does not fix this issue in any way. Also, does FreeJ2ME-plus support JADs? JAD support would be useful for games that expect manifest property lines that aren't actually present in the manifest because they would've been present in the original JAD (the first Doom RPG is an example of a game like that, but in general quite a few games did that).
@AShiningRay
Copy link
Collaborator

Also, does FreeJ2ME-plus support JADs? JAD support would be useful for games that expect manifest property lines that aren't actually present in the manifest because they would've been present in the original JAD (the first Doom RPG is an example of a game like that, but in general quite a few games did that).

FreeJ2ME-Plus doesn't, but zb3's fork does. Personally i didn't pick it from there yet because i want to take a better look and see how it works in more detail, just like i did with TiledLayer.

As for this game's issues. Almost sure they stem from Nokia UI and Form classes in general being mostly stubbed/incomplete. Whenever you get a game that uses either of those, it's almost guaranteed to have issues. Even JBenchmark 2 has issues in one of its tests which consists of updating some basic stuff like progress bars on a Form menu.

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

No branches or pull requests

2 participants