Skip to content

DirectMenuPatch - Implementation issues #3578

Description

@Mimigris

More info about DirectMenuPatch at #3192.

Currently EasyRPG has some issues with the implementation:

  • If a party member is pointed that is not in the party for the Skill, Equiment or Status menu, and that the party is not empty, DirectMenu defaults to the first party member (currently EasyRPG displays a warning and ignores it).
  • If a party member is pointed that is not in the party for the Skill, Equiment or Status menu, and that the party is empty, DirectMenu just opens the normal menu (currently EasyRPG displays a warning and ignores it).
  • If the Order menu is requested and that the party is empty, DirectMenu just opens the normal menu (currently EasyRPG displays a warning and ignores it).
  • Pointing at a hero that is in the party by its ID (by referencing a negative value) should allow scrolling between pages for the Equipment and Status menus, which currently EasyRPG doesn't allow.
  • If the Order menu is attempted to be opened with only one member, EasyRPG displays a warning and do not open it (because of course it doesn't make sense to do that since it will give no result ultimately). DirectMenu accepts it and considers it to be valid and has no issue with this scene being opened.

Additional info with a DirectMenu bug:

  • Pointing at a hero not in the party by referencing it by ID (by referencing a negative value) for the status scene will not make the FaceSet be displayed (since it loads the face from cache, which doesn't exist in this case).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions