Point system not working correctly


#1

PhantomBot Version: 2.3.9.1-NB-20171129 (Revision: 66e5173)
Control Panel Version 1.1

Control Panel Software
jQuery 1.10.2
jQuery UI 1.11.4
Bootstrap 3.3.6
Font Awesome 4.5.0
Ion.Sound 3.0.7
FlotCharts 0.8.3
FooTable 3.0.10

Java Version: 1.8.0_151-b12
OS Version: Windows 10 10.0 (amd64)
Panel Version: 1.1
PhantomBot Version: 2.3.9.1-NB-20171129 (Revision: 66e5173)

Description of Issue:
Bot is only giving points to itself.
More details:
The payout system if only showing the bot giving points to itself.
Global commands like !points all 1, !points takeall 1 give a quick success response, but checking for points on anyone on chat shows no increments or decrements, only the bot receives or has the points taken. The buttons on the panel don’t do anything.
Points given or taken directly to a user DOES work. As in !points add EdSmcr 1 will give the user one point as expected.

There are no errors reported in the logs.

I tested this using a big database with around 55k users, and around 200 active in chat, for around 4 hours and only the bot got any points.
I also tested it using a clean install with a brand new (empty) database. Console log attached below.

[11-30-2017 @ 01:41:36.752 GMT] edsmcr: !points all 100
[11-30-2017 @ 01:41:36.761 GMT] [CHAT] 100 points have been sent to everybody in the channel!
[11-30-2017 @ 01:41:39.250 GMT] edsmcr: !points
[11-30-2017 @ 01:41:39.253 GMT] [CHAT] @EdSmcr, you currently have 0 points and you have been in the chat for 0 minutes.
[11-30-2017 @ 01:41:41.308 GMT] edsmcr: !points all 100
[11-30-2017 @ 01:41:41.315 GMT] [CHAT] 100 points have been sent to everybody in the channel!
[11-30-2017 @ 01:41:44.118 GMT] edsmcr: !points
[11-30-2017 @ 01:41:44.121 GMT] [CHAT] @EdSmcr, you currently have 0 points and you have been in the chat for 0 minutes.


#2

Can confirm this is still a bug

This also breaks the makeitrain command too

EDIT function giveAll(amount, sender) { is also missing sender so the negative message is broken


#3

This should be fixed in the next nightly build


#4

Fixed in 66e5173


#5

This topic was automatically closed after 30 days. New replies are no longer allowed.