etc_onlinecounter_v1.4 (english)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
Research direction
Start by reading the online-counter script and inspecting how it updates etc_onlinecounter.tbl and usr_uptime.tbl. Reproduce the issue with the +onlinecounter toponline command and the username RC command, then trace why SessionTime changes while TotalTime remains 0. Done means total uptime is recorded and reported without the “Only 0 users in table” error.
Written by the indexing model from the issue text.
Description
Hello, i'm newbie and have a question about this script. When is updating Total online time? For a few days I see that the Session time at "etc_onlinecounter.tbl" is updated, but the Total time is 0 constant:
[ "SessionTime" ] = 562,
[ "TotalTime" ] = 0,
When i use RC ... [command] +onlinecounter toponline i recive this in main chat:
[09:03:09] <[BOT]HubSecurity> *** Error: Only 0 users in table, 1 is too high!
When I use an RC on a username, it always tells me this:
[2019-06-02 09:15] <[BOT]HubSecurity>
========================================
Stats:
--------------------------------------------------------------------------------
- Nick: Jetion
- Total uptime: 0 minutes
I stop the Hub, deleted (and then put them back in their original first state at the same place) and started from the scratch both files: "etc_onlinecounter.tbl" and "usr_uptime.tbl", but the result is the same. I can not understand, am I wrong in the settings or elsewhere is the problem? Sorry, my question may be stupid, but I would be grateful if anyone could explain me in more detail about this script and how to use it.
Thanks in advance!
- Dominant language
- Lua
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from luadch/scripts
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
HenrikBengtsson/CBI-software#134 ·
-
Nmap
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
secondlife/slua#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100