ADAPTER-DRIVEN BY DESIGN
Your schema. Understood.
An adapter describes what your data means to the scorer. Field mappings, transforms, filters, bucket definitions, and profiles live in one inspectable configuration.
Start with what you have
Work from your actual CSV or row objects. Declare the fields that identify a compatible dataset.
Define the interpretation
Map inputs into canonical metrics and group signals into meaningful buckets. Configure weights without hiding the rules in application code.
Reuse the model
Run the same adapter from the library, CLI, or Gateway. Package it in a StatPack when you want the configuration and dataset to travel together.
Adapters in this source.
Generated from the canonical adapter catalog for v4.0.0rc6.
| Adapter | Model | Version | Aliases |
|---|---|---|---|
e302.players | EBA/Elevate302 Players | 4.0.0 | e302 |
eba.players | EBA/Elevate302 Players | 4.0.0 | eba_player, eba, ebap, eba_p |
eba.teams | EBA Teams (GP + form weighted) | 4.0.0 | eba_power, eba_t, ebat, eba_team |
example.pairwise_elo | Six-Driver Pairwise Elo | 1.0.0 | |
urrl.players | United Rogue Rocket League - Players | 1.0.0 | urrlp |
A new data domain needs an appropriate adapter and a validated model. StatLine provides the infrastructure; a meaningful scoring policy comes from your data and requirements.