Webnovel.Forum

I started reading at 3pm EDT and my weekly reading time was 1475 minutes with 15 points obtained today. At 4:02pm EDT, my weekly reading time was 1535 minutes and my daily points from reading was 25. If reading points are provided at a rate of 1-5 every two minutes, then according to the weekly reading time statistic, I should have at least gained 29 points, but I only gained 10 points. I was connected to the internet the entire time, and this is not the first time encountering this issue.

I have also captured screenshots that I can send if that is necessary.

See network diagnostic:

Device info :moto x4\9\28\4.4.2
IP : 192.168.1.154
Net TYPE : WIFI
Public Net IP ：0.0.0.0

PING idruid.webnovel.com (49.51.15.11) 56(84) bytes of data.
64 bytes from 49.51.15.11: icmp_seq=1 ttl=55 time=29.8 ms
64 bytes from 49.51.15.11: icmp_seq=2 ttl=55 time=43.1 ms
64 bytes from 49.51.15.11: icmp_seq=3 ttl=55 time=41.5 ms

--- idruid.webnovel.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2012ms
rtt min/avg/max/mdev = 29.835/38.180/43.178/5.939 ms

Target IP：49.51.15.11
1. 49.51.15.11 time=80.823ms
Traceroute complete

PING app.webnovel.com (49.51.20.16) 56(84) bytes of data.
64 bytes from 49.51.20.16: icmp_seq=1 ttl=55 time=25.0 ms
64 bytes from 49.51.20.16: icmp_seq=2 ttl=55 time=37.6 ms
64 bytes from 49.51.20.16: icmp_seq=3 ttl=55 time=130 ms

--- app.webnovel.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 25.055/64.479/130.734/47.131 ms

Target IP：49.51.20.16
1. 49.51.20.16 time=386.071ms
Traceroute complete

PING api.webnovel.com (49.51.20.22) 56(84) bytes of data.
64 bytes from 49.51.20.22: icmp_seq=1 ttl=55 time=28.8 ms
64 bytes from 49.51.20.22: icmp_seq=2 ttl=55 time=50.8 ms
64 bytes from 49.51.20.22: icmp_seq=3 ttl=55 time=119 ms

--- api.webnovel.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2015ms
rtt min/avg/max/mdev = 28.832/66.508/119.883/38.794 ms

Target IP：49.51.20.22
1. 49.51.20.22 time=21.139ms
Traceroute complete

PING img.webnovel.com.tweb.sched.ovscdns.com (23.248.167.26) 56(84) bytes of data.
64 bytes from 23.248.167.26: icmp_seq=1 ttl=55 time=85.0 ms
64 bytes from 23.248.167.26: icmp_seq=2 ttl=55 time=22.3 ms
64 bytes from 23.248.167.26: icmp_seq=3 ttl=55 time=23.1 ms

--- img.webnovel.com.tweb.sched.ovscdns.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2021ms
rtt min/avg/max/mdev = 22.328/43.515/85.058/29.377 ms

Target IP：23.248.167.26
1. 23.248.167.26 time=23.840ms
Traceroute complete

PING ptlogin.webnovel.com (45.113.69.27) 56(84) bytes of data.
64 bytes from 45.113.69.27: icmp_seq=1 ttl=55 time=29.3 ms
64 bytes from 45.113.69.27: icmp_seq=2 ttl=55 time=43.2 ms
64 bytes from 45.113.69.27: icmp_seq=3 ttl=55 time=44.1 ms

--- ptlogin.webnovel.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2021ms
rtt min/avg/max/mdev = 29.332/38.901/44.109/6.775 ms

Target IP：45.113.69.27
1. 45.113.69.27 time=20.462ms
Traceroute complete

PING pay.webnovel.com (45.113.69.27) 56(84) bytes of data.
64 bytes from 45.113.69.27: icmp_seq=1 ttl=55 time=29.2 ms
64 bytes from 45.113.69.27: icmp_seq=2 ttl=55 time=44.0 ms
64 bytes from 45.113.69.27: icmp_seq=3 ttl=55 time=47.9 ms

--- pay.webnovel.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2013ms
rtt min/avg/max/mdev = 29.264/40.421/47.943/8.049 ms

Target IP：45.113.69.27
1. 45.113.69.27 time=53.350ms
Traceroute complete

--The following is the Http request--
checkServer : https://idruid.webnovel.com/app/api/ping

duration = 108ms

ResultCode = 200

checkServer : https://ptlogin.webnovel.com/login/ping

duration = 28ms

ResultCode = 200

checkServer : https://img.webnovel.com/cover.png

Sorry, network error.(-10014)

I was actually testing the timer a few seconds ago because I noticed this bug. I would get on the novel and see the timer in the top right filling up. After it filled up once, it gave me five points in 2 mins. But instead it of continuing after it awarded the points it just sat there, not filling up. So I waited for it to maybe fill up again after a cool down of 2 mins is my thinking for it being stuck, but it didn't do it. So I tapped onto the timer to be taken to the points redemption store and tap the back arrow to start reading again and the timer started filling up again. Once it filled up, the 5 points were awarded and then it got stuck again. I did this process over and over for about 5 times to see if it would fix itself. Needless to say, it did not. I have tried closing and reopening the app, but it still does not work. Although to be honest this WOULD not be a bug in the first place if the developers of this app not focused their attention to things that worked fine, but instead worked on fixing real issues such as the payment problems for coins/SS or the fact that there is only a single payment method. Which extremely limits how we viewers can support our favourite authors and be able to continue reading their chapters besides the fast pass. Now after saying all this. I will point out that I don't know if the previous timer had issues like the above mentioned issues it has now just for a different platform back then. I understand they may have changed the timer for a problem on another platform. Although what I don't understand is why they have to change the whole timer system around to fix that issue. Disclaimer: I don't know if they did have an issue on another platform. I am merely ripping a hole in my b!+ching before someone else does. Besides the payment problems and timer problems now. I have been having a great time on this app. :)

Killbird_2001 it's 300 a day for reading only. I think the ad watching limit is also a couple hundred. There is no limit on maximum points accumulated so far.
I believe there was an exploit found that was being abused prior to the point cap. This new bug may exist to kill the abuse mechanism, but it seems to be overkill.