The only thing this script system does is send commands, there's already a way of automating commands issued on a server (Insim).
1) "last_lap". The race leader begins his last lap. It's a pit notice, really, and would help during races where a pit is required. It's an extra bit of warning, to help avoid being disqualified. I've been disqualified a couple of times, being metres behind the race leader, who clears the finish just ahead of me when I'm a lap or 2 down. Advance warning of the imminent race end would be a bonus.You asked for ideas, and these are mine
2) "car_left" and "car_right". Essentially a pit-spotter event. In cars where peripheral vision is limited, or if you drive with a narrow field of view, knowing a car is adjascent to you would help very much.
3) "low_fuel", plus value. I suppose this might be better placed as a low fuel warning light on the dash, and actually my friend has used OutGage to provide this feedback. I don't have the money that he has for an LCD panel, nor the wiring expertise or programming knowledge he has in order to author it, so capturing a low fuel event would be nice.
4) "pit_at", plus value/s. Another pitlane shout, really. Probably could be covered by #3, I mostly drive longer league races, and my fuel and pit strategies vary. It would be really useful if before beginning a race, I could programmatically plot my race as far as pit strategies are concerned. I already plot them, but to be able to program my own RCMs to warn me that a pitstop is due would be great.