Hi all,

So I'm modifying Lapper to allow us to set race grid order via a GUI interface and the problem is that there does not seem to be any way wihtin InSim to detect what the "/start" mode is (fixed, random, finish, et al). InSimSniffer doesn't show any kind of state change or other packet when you type "/start random" or other mode in game, so has anyone figured a way to find this out?

If not, then I suppose I need to assume that people will contorl it via the Lapper app and do all of the ordering, mode change tracking and other ousekeeping in the script. Then I can replace the "/start" command with "!start" with the same params. The problem there is if someone uses the original "/start" command, I lose track of the state.

Any ideas, or do I just rely on people using the right method?

From reading the docs

Quote from InSim.txt :

You can send [IS_REO] to LFS before a race start, to specify the starting order.
It may be a good idea to avoid conflict by using /start=fixed (LFS setting).
Alternatively, you can leave the LFS setting, but make sure you send your IS_REO
AFTER you receive the IS_VTA. LFS does its default grid reordering at the same time
as it sends the IS_VTA (VoTe Action) and you can override this by sending an IS_REO.

So basically wait until you have a received a IS_VTA, then send your REO packet, which should successfully overwrite any order LFS has decided. When your app first connects to a host it can send a /start=fixed command for good measure, but from reading the docs it seems it won't matter much.

Note that IS_VTA does not exist as a packet (this seems to be an error in InSim.txt), instead it's a IS_SMALL with a SubT of SMALL_VTA and a UVal of VOTE_RESTART.

That's what I'm doing currently. What I'm trying to do is to detect if an admin has used the "/start <mode>" command to set the race order rather than use the GUI interface.