The issue is in the updatePoints function in Core.js. This bug has already been fixed in the master branch of the project in issue #17. What is the ETA for release of this fix? I am currently testing against a clone of the master branch. However, I am using node for distribution to my production server and the last available release is 0.6.0 which still has the bug in it.
The issue is in the updatePoints function in Core.js. This bug has already been fixed in the master branch of the project in issue #17. What is the ETA for release of this fix? I am currently testing against a clone of the master branch. However, I am using node for distribution to my production server and the last available release is 0.6.0 which still has the bug in it.