{"push_id":2722040579,"size":3,"distinct_size":1,"ref":"refs/heads/master","head":"70f874a559e6ae3cd89586df9094a4332a9a2cb2","before":"e502280b20d41c168eba9c7d531c59b36ea5d3bf","commits":[{"sha":"710e1d014de454ae1055f1d017b1ee141a7fc82c","author":{"name":"Dylan K. Taylor","email":"fbbbfd57f7bafbd20a205858ca5ce4a204c90fb0@gmail.com"},"message":"Entity: fixed 0-length motion vectors being passed to move()\nthis was an interesting bug.\n\nThis was discovered by making a projectile's drag 0, making its gravity a factor of its throw force (such that force / gravity = integer value), and then throwing it directly up. At the apex, an error would occur due to trying to do a ray trace with a zero vector.\n\nThis also led me to realize that there's an edge case in the current movement system - if an entity's motion reaches 0, it will stop getting movement updates. This can be undesirable when things such as gravity cause motion to become zero when throwing a projectile directly upwards. This will need to be fixed separately.","distinct":false,"url":"https://api.github.com/repos/pmmp/PocketMine-MP/commits/710e1d014de454ae1055f1d017b1ee141a7fc82c"},{"sha":"7efe767f1ff5db07aff8e2d03b32da2a3fb219e8","author":{"name":"Dylan K. Taylor","email":"fbbbfd57f7bafbd20a205858ca5ce4a204c90fb0@gmail.com"},"message":"Merge branch 'release/3.0' into release/3.1","distinct":false,"url":"https://api.github.com/repos/pmmp/PocketMine-MP/commits/7efe767f1ff5db07aff8e2d03b32da2a3fb219e8"},{"sha":"70f874a559e6ae3cd89586df9094a4332a9a2cb2","author":{"name":"Dylan K. Taylor","email":"fbbbfd57f7bafbd20a205858ca5ce4a204c90fb0@gmail.com"},"message":"Merge branch 'release/3.1'","distinct":true,"url":"https://api.github.com/repos/pmmp/PocketMine-MP/commits/70f874a559e6ae3cd89586df9094a4332a9a2cb2"}]}
{"actor":{"display_login":"dktapps"}}