Double-post for strange, minor bugs of my own with the /randbats command. If you do /randbats [pokemon], [generation] for a generation where the Pokemon doesn't exist in randbats, you get inconsistent results. I didn't test with every Pokemon for sanity.
If the randbats gen is 8, and the Pokemon doesn't exist in gen8 rands, I consistently got the correct "no moves data", whether the mon was cut, CAP, eternamax, etc.
If the randbats gen is 1, and the Pokemon is a gen2 mon like Ho-Oh, correct message.
If the randbats gen is 1, and the Pokemon is a gen3/4/5/6/7/8 mon, the command defaults to the most recent valid movepool (e.g. Sceptile's gen 3 movepool), and you have to click the "Randomized moves" tab before seeing that.
If the randbats gen is 2, and the Pokemon is a gen3/4/5/6/7/8 mon, correct message.
If the randbats gen is 3/4/5/6/7, and the Pokemon is from a later gen, it defaults to the most recent valid movepool (e.g. Serperior's gen 4 movepool), but doesn't have a "Randomized moves" tab you have to click.
BUG STATUS: CONFIRMED - CHAT (SERVER) (DaWoblefet)