Velocity expression not working and docs issues

[Snow-Pyon]

So, I was gonna try some stuff with this expression and realized that it doesn't have any type value, that means you can't get the velocity from anywhere therefore it throws a NullPointerException.

Now, here are some issues with the current documentation:

• This expression doesn't have the correct "since" value, it's "INSERT VERSION" right now:
  http://bensku.github.io/Skript/expressions.html#ExprVelocity

• The world, tree type, time, timeperiod, timespan, experience, item type, item/material, number and enchantment type classinfos has some html tags around it.

• The potion effect type classinfo has null between its values.

• The enchantment classinfo has enchantments.names.sweeping_edge between its values.

• The direction, command sender, entity type with amount and living entity classinfos has a href tag in the pattern.

[bensku]

Oooops, I probably merged this pull request a bit too fast, as it had some other useful features. @Snow-Pyon please post the NPE here fully. I hope @Sashie takes a look at it before next release, as I'm kinda busy.

Docs issues are something that I'll need to check. Thanks for reporting them.

[Snow-Pyon]

Well, I think my memory didn't serve me right, it wasn't a NPE, it was an IndexOutOfBoundsException. Here is it anyways:
https://gist.github.com/Snow-Pyon/c44641627b2a33c37942c5f58f92ff26

[JeepSmash]

More doc issues:
Every expression/condition/event/etc with a link in its description is Broken. 404 error for every link i could find in the docs

[bensku]

@Snow-Pyon Try without addons...

[Snow-Pyon]

@bensku the addons doesn't matter, it's clearly an issue of Skript as how the velocity expression is being registered. A pull request has been made to fix this anyways.

[bensku]

The thing is, addons can override expressions with their own, so if an addon had velocity expressions, it might break stuff. But anyway, doesn't seem to be the cause in this case.

[TheBentoBox]

I believe this has been fixed long ago by now. At least, I personally have used the velocity expression without issue.