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

Battle 2k3: Support the random enemy troops option that is hidden in the context menu #987

Closed
Ghabry opened this Issue Aug 11, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@Ghabry
Member

Ghabry commented Aug 11, 2016

No idea which chunk this is but RPG2k3 has a feature that when enabled randomizes the monster party:

screenshot_20160811_215759

Assuming a monster party consists of monster 1, 2 and 3 any combination of that available monsters can appear in the battle

@carstene1ns carstene1ns added this to the 0.6.0 milestone Apr 17, 2017

@Ghabry Ghabry modified the milestones: 0.5.2, 0.6.0 May 15, 2017

@Ghabry

This comment has been minimized.

Show comment
Hide comment
@Ghabry

Ghabry May 15, 2017

Member

Moving this to 0.5.2 because with the chunk identified this is trivial to implement (Candidate function: Game_EnemyParty::Setup).
Things to test in 2k3:

  • Are such monster just hidden (equivalent to right click monster -> hide) and can be brought on the battle with an event command?
  • Is the "monster hidden" flag respected?

@CherryDT do you know any game that uses this feature? I still havn't found any 😢 .

Member

Ghabry commented May 15, 2017

Moving this to 0.5.2 because with the chunk identified this is trivial to implement (Candidate function: Game_EnemyParty::Setup).
Things to test in 2k3:

  • Are such monster just hidden (equivalent to right click monster -> hide) and can be brought on the battle with an event command?
  • Is the "monster hidden" flag respected?

@CherryDT do you know any game that uses this feature? I still havn't found any 😢 .

@rohkea

This comment has been minimized.

Show comment
Hide comment
@rohkea

rohkea May 16, 2017

Member

Are such monster just hidden (equivalent to right click monster -> hide) and can be brought on the battle with an event command?

Just tested this: yes, they are hidden, and can be brought to the battle with an event command.

Is the "monster hidden" flag respected?

Yes. Only non-hidden monsters are randomized. Hidden monsters are not affected by this option. If you have a monster party with 4 hidden and 1 non-hidden monsters, this option will do nothing.

Member

rohkea commented May 16, 2017

Are such monster just hidden (equivalent to right click monster -> hide) and can be brought on the battle with an event command?

Just tested this: yes, they are hidden, and can be brought to the battle with an event command.

Is the "monster hidden" flag respected?

Yes. Only non-hidden monsters are randomized. Hidden monsters are not affected by this option. If you have a monster party with 4 hidden and 1 non-hidden monsters, this option will do nothing.

@rohkea

This comment has been minimized.

Show comment
Hide comment
@rohkea

rohkea May 16, 2017

Member

I’ve found a game using this feature: a Japanese game Default of Default+ (description, download). Monster groups 3, 4, 5, 41, 46, 79, 107, 108 are random.

Member

rohkea commented May 16, 2017

I’ve found a game using this feature: a Japanese game Default of Default+ (description, download). Monster groups 3, 4, 5, 41, 46, 79, 107, 108 are random.

@Ghabry Ghabry self-assigned this May 28, 2017

Ghabry added a commit to Ghabry/easyrpg-player that referenced this issue May 28, 2017

Ghabry added a commit to Ghabry/easyrpg-player that referenced this issue May 28, 2017

Ghabry added a commit to Ghabry/easyrpg-player that referenced this issue Jun 6, 2017

Ghabry added a commit to Ghabry/easyrpg-player that referenced this issue Jun 17, 2017

carstene1ns added a commit that referenced this issue Jun 23, 2017

Ghabry added a commit to libretro/easyrpg-libretro that referenced this issue May 22, 2018

Ghabry pushed a commit to libretro/easyrpg-libretro that referenced this issue May 22, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment