Chau

It automatically updates. [Colorfulstan's RiotRateLimiter-node](https://github.com/Colorfulstan/RiotRateLimiter-node) handles this under the hood.

Custom rate-limits: the dependency (RiotRateLimiter-node) also supports it, but the interface is not completely designed, so use it at your own risk. [Neamar's own library](https://github.com/Neamar/riot-lol-api) is good for this.

Awesome... the Realms endpoint seems to contain the old rune/mastery versions as well.. I wonder if there is an issue that is already raised.. ``` { item: '9.16.1', rune: '7.23.1',...

In v0.8.21: ```javascript DDragon.Champion.getDataById(championName: string) DDragon.Champion.getDataByIdWithParentAsId(championName: string) DDragon.Champion.listDataById() DDragon.Champion.listDataByIdWithParentAsId() DDragon.Champion.listFullDataById() DDragon.Champion.listFullDataByIdWithParentAsId() ```

Currently experimenting with an optional `version` where the version, for each endpoint, is derived from whatever version map (Realm.list) is currently cached, or from your default region.

v0.8.22 Adding a manual `version()` call to DDragon requests for data (champion.json, item.json, etc) is now optional. It works off either your default region, or a manual `region()` call passed...

I'll make an issue, since this one is kinda feature-packed as well as old.

Hi there, Yes, the reset function will do that as a start. Note that if you want to ignore caching, you just don't have to pass a cache option in...

this will be revisited on the weekend

League API responses seem to not have optional member fields (there is no Static API anymore). It might be worth considering a pull request.