How did you get the Minchecker script to work?

Asked by YouKnowWho

Hi,

I saw that the minchecker script is on the list of compatible scripts, but I can't seem to use it properly.

1) It checks for min slots and min share that are set via a core-command, but adch++ has no such properties. How would I set them?

2) I tried to add ApexDC to the list of allowed clients with the line
["ApexDC++"] = {"ApexDC++",1.3.2},
but this results in a message
"[...] Their version 1 of ApexDC++ does not meet our minimum
 version. 1.3.2 for ApexDC++. [...]

Any ideas, guys?

Question information

Language:
English Edit question
Status:
Solved
For:
ADCH++-PtokaX Edit question
Assignee:
No assignee Edit question
Solved by:
YouKnowWho
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
YouKnowWho (jorgosch) said :
#1

Never mind, silly question. I had set all the settings in the script already... somehow I must have had a temporary blackout when I posted this question, sorry.

Revision history for this message
YouKnowWho (jorgosch) said :
#2

Never mind, silly question. I had set all the settings in the script already... somehow I must have had a temporary blackout when I posted this question, sorry.

Revision history for this message
YouKnowWho (jorgosch) said :
#3

Argh... actually, if someone could just point me to the solution about the Apex line...

Revision history for this message
ToniMontana (nformatoni) said :
#4

I am a bit confused cause i dont understand why you get the message:
"[...] Their version 1 of ApexDC++ does not meet our minimum
 version. 1.3.2 for ApexDC++. [...]

When i add a version number like 1.3.2 then i get a error message when i start the script.
I have tested it on PtokaX and with the PX-Bridge and in both cases with the same result.
minchecker.lua:86: malformed number near '1.3.2'

Line 86 in the script is for me the line with ApexDC.

So it seems that this is a bug in the script. The same happens when you add "jucy 0.84" to the client table. The version from this client also dont get determined correctly (cause jucy sends version like this V:0.84 instead of 0.84)

If you wanna use this script and allow ApexDC then you should report this bug to the original creator (Mutor) so he can fix it.

cheers

Revision history for this message
YouKnowWho (jorgosch) said :
#5

Try adding 1.3 instead of 1.3.2, please.

Revision history for this message
ToniMontana (nformatoni) said :
#6

I dont need to try it with 1.3 instead of 1.3.2
cause this can not work (version number from ApexDC gets reported in MyINFO string as 1.3.2
and therefore 1.3 CANNOT match).
With 1.3 instead of the correct version number you will allways get a Version -1 report.
This is defenitly a problem in the script. It cannot handle version numbers like 1.3.2
(so basically numbers with 2 dots).
Report this to the original creator of this script to get this problem fixed.

This script works well with clients that send "normal" version numbers (DC++, BCDC++, StrongDC++, zK++, RSX++ and others). I know only 2 clients this script dont work with: ApexDC++ and jUCY

Revision history for this message
YouKnowWho (jorgosch) said :
#7

Ok, thanks. Mutor will ignore my bug report, though, since I told him that I use adch and not ptokax. I'll just cut the client checker part from the script.