I would suggest having the options in a readme.txt and most useful options included but commented out in the Workbench icon as tooltypes.
The only difference is that the tooltype doesnt need the dash prefix, as from command line it does:
ex: "RogueFootballCardGame AOS3.exe" -WINDOW -WINHEIGHT=1 -WINWIDTH=1 -BORDERLESS
BTW I bundled your game with other games to be available on AmigaLive desktop app (downloadable from amigalive.com) you can find the game under the configuration "AmiGameJam 2024" so we can test them all easily.
I did a trick to throttle the CPU just before launching your game and revert it just before returning to the main menu.
Let me know what you think.
PS. Your submission doesn't have a main image in the entries page. https://itch.io/jam/amigamejam/entries
Viewing post in Rogue Football CardGame - AmiGameJam jam comments
Thanks for adding to that AmigaLive.
So how does that system actually work? I mean, it reads A4000 68040, but I guess that is not actually emulating the real speed of A4000/040 machine? Or is it? For that game seems to be working too fast for it to be on actual existing 68040? For my understanding is that due to scaling currently happening, it should be tough even for X5000 to run it since it will be done on CPU on Amigas. PCs have no problem since they use GFX cards for that, but Hollywood to my understanding doesn't have similar support to GFX cards in Amigas, hence reverting to raw CPU.
The configuration is set to a A4000 68040 with 256MB and a 4MB Picasso IV RTG (your game required 128MB not to cause the weird crashes so I took it a step more)
I am using a MUI requester, and when the user selects to run your game the script enables JIT using uae-configuration tool and throttles the CPU to 32000 (I think most computers these days can handle a 24000 I dont use Max settings because it will desync netplay as this is used for streaming and multiplayer, same reason I dont use UAEGFX but Picasso IV).
Then the script pushes another startup file and reboots.. then the new startup loads the game, when you exit the game with ESC the startup script continues and disables JIT, sets the throttle to 0.0, removes itself from startup and reboots.
This makes it run with normal performance for the other games in the list.
Using an 060 CPU would not benefit the emulation as it requires another plugin (not included yet with AmigaLive) and its also costly in CPU on the host performance without benefiting much in speed due to how emulation works, that's why I am throttling an 040 to achieve faster speeds. The instruction sets of an 060 are rarely used and I believe when devs compile for 060 they also do for 040 and 020 systems.
PS. Does the game have music or sound? I havnt configured the AHI device, so if its missing let me know and I can check.