@Alex360 EOF is suffering from a legacy that it has to maintain and an engine that is outdate now. But even with this EOF is incredibly good at what it's supposed to do and i know that what i control in EOF will properly translate over RS the way i expect it too.
Thing is... sometimes you need no actual control over certain things ( recall those horrible interfaces with huge screen of config parameters )
That's arguable, it's kinda like FHP in EOF, the user could have no control over it and it could simply be auto generated without actually making CDLC that much worse. I don't mind that something is automatically generated by an algorithm, as long as the result actually work in all use cases. When it doesn't i want to be able to adjust it to fit my expectation
Note that we are talking about something that won't make a chart break or impossible to play, it's a very small detail that i can easily live without control over as long as i know who actually control it.
I have intention but have no time\skill to perform this coverage thing along with documentations stuff. sorry about that.
Don't be sorry, i don't expect the toolkit to have a quality control and i don't mind that the users are the one doing it. My issue isn't so much with that than with the fact there is something that the toolkit control without anyone knowing about it except the few devs with insight on the code.
I'm sure @Rockfirstlast can provide you with files that correspond to his test and that this can be sorted out pretty easily.
Also if the logic was based on the lesson it might good to probably review a bit how things have evolved in general cause lessons are now quite different or doesn't use something that we now see in oDLC.