So far i havn't found any
I have few fixed and more to fix :(
Bugs/problems in 16.05 fixed now for next version
QuoteFixed: All Gets in Lua returning on/off state now return 1 if on and nil if off (thx bastya_elvtars for report).
Fixed: Pm max lines settings is now really disabled if is set to 0 (thx the_pest for report).
Fixed: Bad chars ( $|<>:?*"/\) in botnames no more allowed (thx Josh_J for report).
Fixed: Most GUI fixes, all text boxses now have checking to disallow bad chars from texts. Text boxses for numbers now accept only numbers.
Fixed: All bots registered by script removed on script stop.
Fixed: No more allowed to change hub/opchat bot nick to nick used by online user. No more allowed to create bot with nick used by online user.
Fixed: Deleting of numeric values in gui, no more crashes if box is empty and lua want number (thx The_Fox for report).
Fixed: Some problems with some things and restrictions working only for 4 top profiles.
Changed: Lua init is now after hub start and not on PtokaX startup, fixes some startup crashes.
It will be wonderful if there be language file support in next version of PX. Can it be realized?
Thanx a lot.
Best regards,
NemeziS
I have a question. Can there be redirect addresses even if there is no redirect enabled, so the APi can return them to the LUA script? As I want to use PtokaX redirect addresses to redirect to using my script, this puts some smaller load on users configuring it.
And yes, I know this is not BUG, just curious.
I imagine that it is bad to do this int THIS thread but I wanna request some API tweaks ...
:: ChatArrival(user, msg)
could/should behave like
user - normal no change...
msg - just the user's msg at the time so that we can get what comes after the bracketed username effortless ( sparing us the string.find ... )
:: ToArrival(user, to, msg)
user - normal no change...
to - the "To:%s(%S+)"
msg - the actual msg after the <> bracketed username...
Those two should enable scripts to be put together easier even for learners ...
pls comment - critisize ...
PS: Sorry for lil-hijacking ...
QuoteOriginally posted by bastya_elvtars
Can there be redirect addresses even if there is no redirect enabled, so the APi can return them to the LUA script?
I check luainterface and is not checked if is redirect enabled, simply if lua request redir address is returned redir address :)) -> Working and not need any changes.
Hi,
It seems the new 16.05 is not accepting connections from BlackDC clients. One of my users alerted me to this, and I confirmed it. Here's the log from the Users/Chat window with CMDs checked:[14:15] (192.168.1.35) > $Key T??? A ????0???QS??AR6Vv??"/%DCN096%/??/%DCN096%/?????#?P|
[14:15] (192.168.1.35) > $Supports UserCommand NoHello NoGetINFO UserIP2 BotList ClientID SecuredExecutor|
[14:15] x User removed: (Socket 828)
Can't figure out if this is Ptokax's or BlackDC's fault... Any idea?
Edit: already answered in http://board.univ-angers.fr/thread.php?threadid=3875&boardid=9&styleid=1 ... sorry ^^
Je suis francais et j'ai le meme probl?me pour les connections des clients BlackDC
I'm french and have the same problem for the Black's connections
I would like to have a trick
Hi chettedeboeuf, sorry, the only trick I know is to use another client... or ask the BlackDC developer to respect the DC protocol.
Salut, y a pas de truc, il faut utiliser un autre client... ou demander au d?veloppeur de BlackDC de respecter le protocole DC.
Merci, je vais utiliser oDC en attendant mieux
Thank you, I will use oDC
Try fulDC. It's very similar to oDC but is more up-to-date. :)
In the Deflood tab, whenever I change a value in Same main chat with multiline messages and Same multiline private messages (e.g Disconnect 2 with 5 lines) and restart PtokaX, i find there the old values (Disconnect 2 with 2 lines). So, the new values aren't saved. Could u check that?
Best regads,
jiten
QuoteOriginally posted by jiten
So, the new values aren't saved. Could u check that?
QuoteChangelog...
Fixed: Saving of same multiline deflood settings (thx Mickey for report).
PPK,
The image below shows you the large amount of CPU usage when loading Ptokax 16.06 having a 200KB permban.dat file, a 90KB userlist.dat file.... and having Robocop 10.01a
running windows 2003 512MB, P4 1.8
(and only running czdc++ and a virus scanner beside it...)
Is it my machine??
Or might it be correct that it takes more than 10 minutes to load Ptokax at this moment, using 100% CPU during those minutes...
If you need more info let me know..
(http://www.u2bloodredskyhub.com/forum/File_Lister/Propaganda/Ptokax1606debugbuild.jpg)
Umm servus people... i dunno if this is a bug (prolly not but what the hell)... if i give in the GUI a name to the hub.. and a descripion... when i fav it within dc++ ... umm i get the descripion same as name.... get it with older versions also ...
anybody have a clue?
Khez
Ptokax 16.06 is runnig whitout any problems
Thanks PPK
Loading Ptokax 16.0x Memory Usage
I think you have to wait for the next RoboCop, some commands are changed.
QuoteOriginally posted by Motivations
The image below shows you the large amount of CPU usage when loading Ptokax 16.06 having a 200KB permban.dat file, a 90KB userlist.dat file.... and having Robocop 10.01a
userlist.dat is not PtokaX file.
Permban is slow, that is known problem but 10 minutes ?(
Please try it without robocop, to check if is really PtokaX problem :rolleyes:
me have the same prob with permban.dat file if it gets to big it takes alooooong time before Ptokax gets loaded.
ugh ugh ppk, i don't say this to make you look bad and make my robo look beter. hehehehe
i can send ya a file to try for ya self but we allready talked about it and you sayd your self banlist no good
- Optimus
PPK,
did another test for you without Robocop 10.01a,
started up ptokax.exe at 11:35 pm, and the ptokax screen finally showed up at 11:43 pm, so this time 8 minutes...
and sorry I did mean: RegisteredUsers.dat = 90KB
The hub started fine after the removal of robocop...
It is only the loading of Ptokax itself, before you are able to press the start the hub button that takes minutes...
with 15.25 debug build,
the loading of the dat files is finished as soon as the tray-icon appears...
maybe this helps you out in finding the loading bug....
;-)
QuoteOriginally posted by Motivations
with 15.25 debug build,
the loading of the dat files is finished as soon as the tray-icon appears...
It is not bug, this only show how is banlist slow. On loading is any new banlist item checked if not already exist, that is why is now too slow :( I remove this check.
umm tried connecting to the hub... with some friends... and we started reconnecting to the hub... pressing ctr + R countless times (i needed a test for a script i was doing + the test itself fot stability works well i guess :P )....
I got " [20:46] x User removed: (Socket 1330530121) " for 2 of my friends friedns..... and then ... everybody who tried the CTRL + R thing got that ... got the same error...
Umm what's the problem? is it a bug or smth ?
QuoteOriginally posted by Khezex
and we started reconnecting to the hub... pressing ctr + R countless times (i needed a test for a script i was doing + the test itself fot stability works well i guess :P )
It looks like connection deflood kill you :D
If connection flood is detected, PtokaX not accept more connections from same ip for 1 minute... any connection try delay this "silent" ban :]
Hmz... interesting... although i was hopeing setting the flood thingie with a higher count/60 secs.... could work past the deflood setting... alas... nevermind
---------------------------14.03.2005 23:14:43---------------------------
Exception 'EIdSocketError' in module PtokaX.exe at 0008EAA0
Socket Error # 10013
Access denied.
Call stack:
:0048FAA0 [PtokaX.exe]
:77E649D3 [kernel32.dll]
:0048FAA0 [PtokaX.exe]
:0051A024 [PtokaX.exe]
Recursive call (2 times):
:0048FAA0 [PtokaX.exe]
:0048F9ED [PtokaX.exe]
:00490A13 [PtokaX.exe]
:0048B08C [PtokaX.exe]
:004937A6 [PtokaX.exe]
:00425F26 [PtokaX.exe] ThubForm::WebStatsStart (frmHub.cpp, line 4221)
:0056740F [PtokaX.exe]
:00425F55 [PtokaX.exe] ThubForm::WebStatsClick (frmHub.cpp, line 4227)
:005677DA [PtokaX.exe]
:0052CE0D [PtokaX.exe]
:0052CE92 [PtokaX.exe]
:0052CDE8 [PtokaX.exe]
:0052CFE7 [PtokaX.exe]
:0056763F [PtokaX.exe]
:77D157BB [USER32.dll]
:77D0612F [USER32.dll]
:77D069A5 [USER32.dll]
:77D069E8 [USER32.dll]
:77D069B9 [USER32.dll]
:77D0695B [USER32.dll]
:77D069E8 [USER32.dll]
:77D069A5 [USER32.dll]
:77D351E6 [USER32.dll]
:77F4605A [ntdll.dll]
:77F427A7 [ntdll.dll]
:77E58D99 [kernel32.dll]
:77E58DB6 [kernel32.dll]
:0056A5E4 [PtokaX.exe]
:77D08F5B [USER32.dll]
:0052CA45 [PtokaX.exe]
:0056740F [PtokaX.exe]
:0056A71C [PtokaX.exe]
:0056AD78 [PtokaX.exe]
Recursive call (3 times):
:0056763F [PtokaX.exe]
:77D069E8 [USER32.dll]
:77D069B9 [USER32.dll]
:77D0695B [USER32.dll]
:77D069E8 [USER32.dll]
:77F47CF2 [ntdll.dll]
:77D351E6 [USER32.dll]
:77D069B9 [USER32.dll]
:77D08EDC [USER32.dll]
:0056A5E4 [PtokaX.exe]
:004F6131 [PtokaX.exe]
:0054A9A1 [PtokaX.exe]
:0056A25F [PtokaX.exe]
:0056A276 [PtokaX.exe]
:0056A5E4 [PtokaX.exe]
:0056A25F [PtokaX.exe]
:004FF4B6 [PtokaX.exe]
:77D0612F [USER32.dll]
:77D069A5 [USER32.dll]
:77D0695B [USER32.dll]
:77D080AB [USER32.dll]
:77D351E6 [USER32.dll]
:77D0881B [USER32.dll]
:77D0887D [USER32.dll]
:77D2E098 [USER32.dll]
:77D2E175 [USER32.dll]
:77D16419 [USER32.dll]
:77D15397 [USER32.dll]
:77D069A5 [USER32.dll]
:77D069E8 [USER32.dll]
:77D069B9 [USER32.dll]
:77D157BB [USER32.dll]
:77D0612F [USER32.dll]
:77D069A5 [USER32.dll]
:77D0695B [USER32.dll]
:77D351E6 [USER32.dll]
:77D08EDC [USER32.dll]
:77D09B7A [USER32.dll]
:0056A6C8 [PtokaX.exe]
:00567BDF [PtokaX.exe]
:00567B57 [PtokaX.exe]
:0056763F [PtokaX.exe]
:00518BA9 [PtokaX.exe]
:00518BD1 [PtokaX.exe]
:0059210D [PtokaX.exe]
:005188B0 [PtokaX.exe]
:77D07520 [USER32.dll]
:0056A516 [PtokaX.exe]
:004F6131 [PtokaX.exe]
:0054A9A1 [PtokaX.exe]
:0056A25F [PtokaX.exe]
:0056A276 [PtokaX.exe]
:004FF4B6 [PtokaX.exe]
:77D08ACC [USER32.dll]
:77D0F4DE [USER32.dll]
:0056A40C [PtokaX.exe]
:744FCCA0 [MSCTF.dll]
:0056A5E4 [PtokaX.exe]
:0052CA45 [PtokaX.exe]
:0056A25F [PtokaX.exe]
:0056A277 [PtokaX.exe]
:004FF4B6 [PtokaX.exe]
:77D0612F [USER32.dll]
Main Thread ID = 0000083C, Current Thread ID = 0000083C
Registers:
EAX = 0012F470 CS = 001B EIP = 77E649D3 Flags = 00000202
EBX = 0048E7B0 SS = 0023 ESP = 0012F46C EBP = 0012F4C0
ECX = 00000000 DS = 0023 ESI = 0012F4F4 FS = 003B
EDX = 0048FAA0 ES = 0023 EDI = 0012F548 GS = 0000
Code at CS:EIP
5E C9 C2 10 00 83 65 C0 00 EB EB 90 90 90 90 90
Stack:
0000271D 0EEDFADE 00000001 00000000 77E649D3
00000000 00000000 77D0612F 0051A005 00DF4F24
005DE90B 00000003 00000000 00000000 0218520C
77D0612F FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
Additional info:
iJoins: 169611, iParts: 168993, iLogged: 609
NicklistLen : 6875
OplistLen : 131
MyInfosLen : 28491
MyInfosTagLen : 53128
---------------------------19.03.2005 13:42:41---------------------------
Exception 'EStackOverflow' in module WS2_32.dll at 0000060D
Stack overflow
Call stack:
:71C0160D [WS2_32.dll]
:71C03B8A [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
:71C03BB5 [WS2_32.dll]
:100037E1 [nl_lsp.dll]
:1000443A [nl_lsp.dll]
Main Thread ID = 00000ECC, Current Thread ID = 00000ECC
Registers:
EAX = 00033008 CS = 001B EIP = 71C0160D Flags = 00010283
EBX = 016F8BD0 SS = 0023 ESP = 00033000 EBP = 00033010
ECX = 00000000 DS = 0023 ESI = 01E656E0 FS = 003B
EDX = 00033054 ES = 0023 EDI = 00033060 GS = 0000
Code at CS:EIP
FF 15 E4 51 C1 71 C9 C3 90 90 90 90 90 90 90 90
Stack:
00033008 0003300C 00000000 00000000 00033020
00000000 00000000 1000443A 0051A005 017A4858
005DE90B 00D12408 00000000 00000000 017D59A0
1000443A FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
Additional info:
iJoins: 212668, iParts: 212142, iLogged: 501
NicklistLen : 5670
OplistLen : 172
MyInfosLen : 23463
MyInfosTagLen : 44218