Is it possible to create qualification system by using RName so Airio can split racers in Divisions (Serie A, Serie B...) if is possible then new command is needed like RSerieNo (for selecting how many racers in each division (serie). And if its possible to remember that in separate file so if its needed can be deleted.
In Airio FREE you cannot use limads level 1, 3, and 5, they are always converted to levels 0, 2, and 4. The solution is to change level needed for stats manipulation. In CFG file set EnableStats=4, then all admins can use stats manipulation commands. Also Airio restart is never necessary, !rld always works...
Is this some sort of punishment for using !exr? It seemed to happen the first time I did it, not just after I spammed it. I did give it enough time to show "Your current LFS Experience Index : 714.6" but it wouldn't come up, which is why I did it more than once in the first place.
Edit: Then I typed !ex after this and it showed up as 714.1
No, there is no punishment (although people should use !exr reasonably). What you see is a side effect of showing the updated index, while the update fails or has insufficient time to respond.
When you type !exr, first your current EI is shown. It is then locally decreased by 0.1, so that updated EI can be shown. If current and new EI would be the same, there'll be no message. After local decrease an update is expected. If it doesn't come, locally the index stays a bit lower and will be lowered on each !exr. But once update happens (with successful !exr or reconnect), it is back where it is supposed to be.
!exr or generally EI generation could fail for several reasons. The usual one is incorrect LFSW key configuration in Airio (one key used also somewhere else), but also breakdown of communication with LFSW or airio.eu. You should always give enough time to the update, depending on server load and Airio setup it may take one to dozens of seconds to get the updated value...
Back to two older issues, I promised to address them:
Well, I do not want to completely disclose the formula, for two reasons: 1) It may yet change in the future (although currently it works pretty well). 2) If known, I'd be probably flooded with complains about how bad it is and what more it should take into account and what not and in what way and how people could cheat. For that reason I made public the things taken into account, but I leave the specifics hidden.
However I can disclose as an example one, the simplest part of EI. Traveled distance index is in ASP.NET calculated like this:
double dex = Math.Pow(kms * 4, 1D / 3) * 1.5
Total distance in kms (as reported by driver's online LFSW stats) is multiplied by 4 and a cubic root is calculated from the value. The result is multiplied by 1.5, which is a weighing factor. For example if somebody traveled 250,000 kms, the distance index would be exactly 150.
The cubic root is the calculation core, because it has strong regressive effect. D index rises fast from the beginning, but the more someone has driven the slower this index rises. The other indexes work in much the same fashion. From start all indexes rise quite quickly, but as the input values raise, index growth slows.
While there is no theoretical limit to overall experience index, I believe 1200 points would be the practical limit for someone who spent many many years in LFS, did tens of thousands of races on all track/car combinations, is fast in all types of cars and is also active concerning offline hotlapping.
Hard to comment on this one, I did not see any substantial troubles. I do not think lowering of the LFSW key number could have any real impact on connection troubles, just as asking for LFSEI. What could be causing connection troubles though is the buttons displayed right after connect. They're all send right after the driver appears at the server and if something isn't optimal, lost connection could result.
People are losing connection with or without Airio, after connect and during track changes as well. Anyway, soon I'll add two more events usable for big or small button display: On first race join and on every race join. The first one, if I succeed in proper implementation, could replace buttons shown after connect, thus limiting the initial load.
Correctly, but it isn't as bad as it is now. After 2.3.7 (or .8?) problems started to occur and the track change is the best part where it shows up because I can't remember I've seen that many reproducible loss of connections at a change of track.
And I don't understand it because I send no data during or after a track change. No special windows, no nothing.
Sadly I cannot downgrade to do ultimate testing because LFSEI is one of the latest (great) additions but if it gets out of hand I will
Unfortunately kick/ban voting in LFS is very underdeveloped. It is not possible to activate only kick (without ban) voting and also it is not possible to cancel a running kick/ban vote. Too bad developers got lost in new tyre physics and do not have time or strength to improve LFS voting.
To have what you require (and which would many appreciate as well, no doubt), it would have to be a completely separate Airio kick/ban voting system. But it would have its catches. It would be e.g. possible to show Kick (or even Ban) button in !pl to everyone, if configured, and the click would start the vote, with appropriate message shown to everyone.
It is not possible however for other people to just press 1, that event cannot be captured. An alternative could be sending e.g. /i 1 from client to server. It is a hidden message that could be used for identifying the voter and sending new message with voting state.
The downside is people would have to define /i 1 as a custom hot key sent by one key press, but communicating this info could prove to be a bit complicated, at least from the start. On the other hand all newer FULL/PROS Airio would use the same, so it is just one hotkey (bind) defined...
What do you think from the practical/user perspective? Any chance this requirement would be understood and used?
Airio system would be the best because a kick, managed by Airio, would imply a configured drop in safety rate as well. If the driver is already in the database of course. (Need timestamp sorting too, cr.txt already gets way out of hand even with the current PB threshold :schwitz
I think it's fairly easy communicated. As a voter, you can type that message as well isn't it? So; "^7send ^3/i 1 ^7to vote yes" and people will understand what they have to do. Maybe use 0 instead of 1. Keyboard layout wise...
That its also possible to bind that command is of later concern. I think it's even better like this, maybe people start thinking first before they vote without knowing for what.
If it's Airio based you could use LFSEI ranking as well instead of point ranking or a combination. Maybe not sending that vote message to people without sufficient level...
Lots of things possible, I think it would be great