Yanfly's Enemy Target Info - help please

These queries relate to Yanfly's Enemy Target Info script, found here: https://github.com/Archeia/YEARepo/blob/master/Battle/Enemy_Target_Info.rb

1. The info revealed about the enemy is shown on 3 separate pages: parameters, elements and states.  To switch between the pages, the default help window says "Press L or R", with L and R standing for left and right respectively.  A number of players have found this confusing, thinking it means using the arrow keys (which actually change the enemy being targeted) but if I put Q and W instead (which is the default for left and right) this will not help those who do not use a QWERTY keyboard e.g. if the keyboard is French.  Is there any way to get this script to use Page Up and Page Down instead for that task?
2. The elements page has space for 8 elements. I, however, have more than the default elements.  Has anyone found a way of e.g. adding another elements page to accommodate more?  It's a question that was often asked on Yanfly's site, but never answered.
3. Another question often asked there, but never answered, was exactly how to get this working as a skill, rather than as a default.  Can anyone help me here?

Thanks.

1) You'd need first an extra script that allows full keyboard bindings if you want that...


and you can always have a key binding tutorial early on the game anyways so that they know what the L/R and other button symbols that Ace uses translate on the default bindings


3) Maybe just find a scan skill then?

I'd like to avoid getting yet another script, if possible, but maybe I'll have to, as a tutorial won't explain to e.g. a French speaker where the equivalent keys are.  I'm using French as an example because I know that the Q and W are actually located somewhere else on the keyboard.

The only scan script on the Master Script List is neon Black's, which appears to provide the info as default, rather than as a skill.  If someone knows of a scan skill script I'd be grateful to hear about it.

The different keyboard layouts are one of the reason why the keyboard mapping (under F1 ingame) is local.


Unfortunately RM is limited in the options what can be mapped and what not. but I think your best solution is to point the player to that part of the engine and allow him/her to select the best compromise for which keys to use.


The alternative would be for you to install a full keyboard script and to provide the key mapping yourself, which is not only a lot more preparation work, but can also cause incompatibilities if one of your other script handles the keys in a different manner...

Okay, I think that pointing out F1 is going to be the most practical way of handling this.

If anyone can come up with something for the other 2 queries (extra element page and scan skill), I would be very grateful.

Bump.

I am particularly interested in finding out how to get this script working as a skill, rather than as scan, so if someone could have a look at this for me, I would be very grateful.  I've been over the configurable bits so many times, trying with different combinations of true/false, but nothing I do seems to get this right.  And yes, I have done it with what I think is the appropriate note tag for the skill i.e. <scan info: all> and the note tag in the enemy tab <show info: all>

Thanks.