Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi !
Thanks for your nice work! I was really happy to find out that some people started working on such an api and making it as open as it can be for the community!
I noticed that you tool didn't fully support spells (and read #19 later), I was interested in such a feature so I started an implementation today.
There is probably still many work to do: at least support the english language (also touch/wakfu... :() and probably a lot of other things I missed. However I already got a nice result, I think now is a good time to ask if I am going in the right direction.
Here are some issues I can think of so far:
--maxItem
limits the number of spells outputed, but they will occur once for each possible level. For example if maxItem is set to 2 and the two outputed spells can reach level 3, there will be 6 items in the output. The reason for this is that I didn't find any cheap way to find out what was the maximum level of each spell of a class.The structure of resulting data is currently like so:
Here is the result of a full run: spell.json.gz