New testing version is here (http://www.ptokax.org/files/0.3.5.2d.7z).
Quote from: ChangelogAdded: Mising $Close Direct Connect command + arrival to lua + permission for profiles.
Fixed: Memory corrupting on registering to udp-debug.
Fixed: Memory corrupting on big hubs when opchat is enabled.
Fixed: Memory corrupting when script tryed to use user:something and user is no more online.
Fixed: Max private message length limit checking (thx CrazyGuy/Fane for report).
Full online PtokaX changelog is available in Wiki (http://www.ptxwiki.psycho-chihuahua.net/doku.php/changelogs/ptokax/changes_after_0.330_15.31).
Thanks a lot PPK!!! :)
I got some errors in scripts, like if in this version function DelRegUser is not returning 1 when successful anymore.
Could that be so?
Yes true, bug caused that returning 1 from DelRegUser was cleared from stack before function ends ::)
Quote from: Josecar222000 on 12 January, 2007, 21:17:44
I got some errors in scripts, like if in this version function DelRegUser is not returning 1 when successful anymore.
Could that be so?
tested with following code
ChatArrival = function(User,Data)
local sMess = DelRegUser(User.sName)
SendToAll(frmHub:GetHubBotName(), sMess)
return 0
end
result on success
Quote
<PtokaX> CrazyGuy
result on failure
Quote
<PtokaX> -1
but I see PPK already replied while i was writing this 1 ;-)
Hello PPK,
Some of my users are getting this message
Quote
Sorry, search request not send because have wrong IP.
Could anyone help me in this plzz......thanx in advance...
Quote from: speedX on 20 January, 2007, 17:13:47
Hello PPK,
Some of my users are getting this message
Could anyone help me in this plzz......thanx in advance...
On the tab Options, you have a checkbox saying "Check user IP in commands".
When you enable this, it will check the IP stated by the user in $Search and $ConnectToMe against the IP the user connected to the hub with.
If the user has an invalid (or at least different) IP in his clients' settings than with which he connects, his search/download request will be blocked and the user receives this message.
This feature increases security and reduces possible protocol breach attempts.
It can be overridden per profile in the Profile Manager by checking the box for "Dont check IP for DC Commands" ( or "No IP check" as it was called when first introduced )
Mutor: feel free to fix the language file.
Thanx CrazyGuy and Mutor for the help ;)