DCurrent / openbor

OpenBOR is the ultimate 2D side scrolling engine for beat em' ups, shooters, and more!
http://www.chronocrash.com
BSD 3-Clause "New" or "Revised" License
894 stars 119 forks source link

Options at pause menu #314

Open dbaldan opened 3 months ago

dbaldan commented 3 months ago

Is your feature request related to a problem? Please describe. Watching some gameplays of one of my games, I realized that a lot of people who aren't used to OpenBOR (and I've also seen people who have experience with the engine going through the same problem) don't know that if you press F12 during the pause , you go to the options menu.

In one of the cases, the person wanted to reconfigure the control and instead of pressing F12, they exited the game to access the options and then used Load Game to return to where they were.

Because this isn't available in the manual, for example.

Describe the solution you'd like We could add a third option to the pause menu (which only has Continue and Quit) called Options, which would take us to the same menu that we access when we press F12.

Describe alternatives you've considered I know that there is the possibility of accessing this either by pressing F12 during the pause (which does not seem intuitive to me, especially on Android, as it is the Screenshot button) and there is also the possibility for the game developer to add this to his game via script. However, this is a basic feature of the engine, and should not be conditioned on the developer's need to program this via script, as it is not a customized menu like in SORX, but something trivial.

DCurrent commented 3 months ago

@dbaldan

My only concern is not wanting to add too much more hard coded cruft to the native menu system, since we'll have to turn around and depreciate it if we make things a bit more adjustable in the future. The other thing is that options viewed in game look tend to look very busy and unprofessional, which of course gets blamed on the engine and might be why they are obfuscated (IDK, I didn't add the ScreenShot->Options trigger so I can't say what its reasoning was). Other than that, this is a very good suggestion.