ConnectToMeArrival is never called from adchpp-ptokax

Asked by Janne

I am trying to use a download blocker script but ConnectToMeArrival/MultiConnectToMeArrival/RevConnectToMeArrival is never called from adchpp-ptokax.
Oddly, SearchArrival is called shortly after download is started.

Question information

Language:
English Edit question
Status:
Expired
For:
ADCH++-PtokaX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
poy (poy) said :
#1

indeed, download handling hasn't been implemented yet in ADCH++-PtokaX. however, search handling has, quite extensively.

it's in my plans to add that, but part of the reason i haven't been very motivated to do so is that download requests don't go through the hub (in both NMDC and ADC): the hub helps establish the connection between 2 peers with ConnectToMe etc, but then these 2 peers communicate between each other to decide what to download. as a result, the hub never knows what file 1 user is downloading from another one.

on the other hand, search requests are sent to hubs; so they can see what each user is searching for. however, search results aren't returned via hubs; they are communicated to the searching peer directly (similarly to downloads). therefore, for similar reasons, i have focused my efforts on perfecting the SearchArrival event but haven't bothered yet with SRArrival.

nevertheless, it would still be handy to be able to block download requests from PtokaX scripts and that should not be too hard to add. it's definitely planned, but not a huge priority.

Revision history for this message
Janne (jannesdata) said :
#2

Thank you for the quick answer.
Is it possible to give this a higher priority? We are running some very large hubs and are in need of the possibility to block users that doesn't follow the rules from downloading.

Revision history for this message
poy (poy) said :
#3

added in rev 102.

Revision history for this message
Janne (jannesdata) said :
#4

 can you get an op chat also ? there are some scripts that need an op chat

Revision history for this message
poy (poy) said :
#5

i've added an op chat bot in rev 105 but it hasn't been well tested. its settings can be controlled with +cfg px_opchat, +cfg px_opchatcid, +cfg px_opchatdescription, +cfg px_opchatemail.

Revision history for this message
Janne (jannesdata) said :
#6

Hello again. We've tried to the OpChat now but we have not gotten the script to post in opchat. what are we doing wrong?

Revision history for this message
poy (poy) said :
#7

thanks for the report, i hadn't tested that. should work fine in rev 108.

Revision history for this message
Janne (jannesdata) said :
#8

how can i run this script in Adch++??? ShoutStats2.01LUA5.1x[Strict][API 2]

Revision history for this message
poy (poy) said :
#9

ShoutStats seems to be running correctly here. what problems are you having with it?

Revision history for this message
Janne (jannesdata) said :
#10

it wont work in status bar in adch. Main and topic is ok but not in status bar

Revision history for this message
Janne (jannesdata) said :
#11

it was this script ShoutStats 2.03 LUA 5.1x [Strict] [API 2]

Revision history for this message
poy (poy) said :
#12

as i explained in bug 571248, it isn't possible to modify clients' status bars from the hub. try to tweak the settings of the ShoutStats script to modify the hub topic instead of using status bars.

Revision history for this message
Janne (jannesdata) said :
#13

hey we have a problem with TagCheck 2.01LUA5.1x [Strict] [API 2]. lua.
it does not work in Adch + + if you have many user. we have 500-1100 users .the users dont get any info why they get kicked.is this a script or software problems ?

Janne

Revision history for this message
Launchpad Janitor (janitor) said :
#14

This question was expired because it remained in the 'Open' state without activity for the last 15 days.