When mapping in Kontakt, sometimes you want to map articulations to be selected by the script. This could be used for scripted keyswitches, round-robin, and much more. Scripting how articulations are selected gives you a lot more power than using Kontakt's native group selection conditions. This following trick will show you how to efficiently map the samples into groups.
If you're creating a sample library that uses many articulations, it can become impractical to map each articulation into a separate group. Kontakt's interface is unwieldy when having to manage dozens of groups. However, if you discard Kontakt's native volume-velocity modulation, you can use the velocity dimension to expand each group's capacity. This technique essentially gives you 127 articulations per group.
While this allows you to create well-organized groups, you have to account for velocity affecting volume by using the "change_vol" function in Kontakt--which is a good idea anyway, because it gives you greater control over the volume curve than using Kontakt's volume modulator. As for selecting the articulation, KSP gives you two options: use the "change_velo" function to change the event velocity to the desired velocity number (which relates to the articulation), or to ignore the MIDI event and use the "play_note" function to manually play samples.
This technique reduces CPU usage too, especially when using group effects. Also, using many groups in Kontakt can slow the program's response time, which makes mapping and editing the NKI patch tedious.