Can trainer options (Custom1..5) be renamed?

[Photon]

Without a recompile? I mean the labels presented in the WHD license window.

I see this in a few most recent slaves, and it would be good if it was directly readable what they do, instead of "testing them out" and making notes.

In this case they are not mentioned in the ReadMe.

[Aardvark]

Originally Posted by Photon

In this case they are not mentioned in the ReadMe.

Which game is this? Custom options should always be mentioned in the Readme

[Wepl]

You can set them and overwrite which is possible in the Slave using the Config option.
See https://whdload.de/docs/en/opt.html#Config

[Photon]

Originally Posted by Aardvark

Which game is this? Custom options should always be mentioned in the Readme

I will need to have another look, because the same slave and WHD version produces different results in emu vs real Amiga. On real Amiga about 3/20 games had the Custom1-names instead of named labels.

Originally Posted by Wepl

You can set them and overwrite which is possible in the Slave using the Config option.
See https://whdload.de/docs/en/opt.html#Config

Does Config= work like ToolTypes like QuitKey=? I.e. right-click the exe. It seems I can just turn Custom1 etc on or off with those.

Or (from the examples) I make a small binary file with dc.b and put it somewhere?

I think I just need to spend some time reading the WHD docs.

[Wepl]

You can use it as normal Tooltype:

Config=BW;C1:B:Skip Intro;C2:X:Activate Trainer:0

creates

• Button ButtonWait
• Button "Skip Intro" bound to Custom1
• Button "Activate Trainer" bound to bit #0 of Custom2

[jotd]

with custom options in splash screen, what's now missing is most of the authors (including myself) forget to specify which custom flag does what, which is annoying when creating scripts.

It would be nice if custom option (whdload 17+) could be decoded into something clear by a tool. Well we can still search in the slave binary, never mind.

[Photon]

I've tested all the 20ish latest slaves in latest WHDLoad in WinUAE and real Amiga, and WinUAE displays the custom options correctly, while e.g. the Gravity-Force slave displays Custom1..5 on real Amiga instead of the correctly labeled ones in WinUAE. (This slave has custom1..4 documented in the ReadMe. So this is the only thing this slave can be "accused of", I say great job! )

I think it's a file system difference (and I lose the tooltypes?), because I can get the Custom1..5 behavior in WinUAE by mounting the FAT CF card.

I get no warning of losing file properties when copying from PC to FAT CF card tho.

Is there a way around this? A PC-formatted second CF card (and extracting, copying, and deleting) is my solution for easy access and quick file transfers (and not filling up my important SYS and WORK card with GBs of games and demos).

I'd be happy to change the format of the CF card to something else that both ends can read, because FAT is also OLD, SLOW, and CLUNKY.