PtokaX 0.3.3.1 released... - Page 8
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

PtokaX 0.3.3.1 released...

Started by PPK, 10 June, 2005, 02:21:13

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Jerry

#175
QuoteOriginally posted by dragos_sto
one little bug
in function NewUserConnected(User)
when one operator connect it seen at reg user
not to be operator
Try: OpConnected(User) function for this ;)

Jerry

QuoteOriginally posted by Mutor
Or the ever popular function saving shortcut
OpConnected = NewUserConnected
....when appropriate

Yes, or this way.  :D   :))   :]

dragos_sto

i deed this OpConnected = NewUserConnected
but when i use curUser.iOpHubs it not seen to be an
operator

uffetjur

Back from holiday, very nice to se that my hubs still running after 3 weeks!!!


------------------------------------------------------------
Current stats:
------------------------------------------------------------
Version: PtokaX DC Hub 0.3.3.1 [debug] built on Jun 10 2005 01:35:21
Uptime: 21 days, 18 hours, 11 minutes
Users (Max/Actual Peak (Max Peak)/Logged) : 1000 / 391 (391) / 322
Chat messages: 13983 x
Unknown commands: 0 x
PM commands: 14700 x
Key commands: 150207 x
Supports commands: 147703 x
MyINFO commands: 85010 x
ValidateNick commands: 148752 x
GetINFO commands: 0 x
Password commands: 30326 x
Version commands: 30179 x
UserIP commands: 20020 x
GetNickList commands: 30343 x
Search commands: 2434573 x
SR commands: 1715114 x
CTM commands: 99500443 x
RevCTM commands: 20266963 x
BotINFO commands: 149 x
------------------------------------------------------------
CPU usage (60 sec avg): 3.37%
CPU time: 10:17:30
Mem usage (Old style): 2306 kB
Mem usage (Peak): 7.22 MB (30.30 MB)
VM size (Peak): 11.44 MB (32.81 MB)
------------------------------------------------------------
SendRests (Peak): 0 (0)
RecvRests (Peak): 0 (6)
Data sent: 62.47 GB
Data received: 6.71 GB
Tx (60 sec avg): 48.76 kB/s (42.86 kB/s)
Rx (60 sec avg): 2.85 kB/s (4.16 kB/s)
Somewhere in Cyberspace

exlepra

Hi guys, dcdm opchat commands doesnt seem to work with 0.3.3.1 (ie -help -info -reportspeed etc, sent to opchat) , If I switch back to  0.3.3.0 17.09 they are working again.

PPK

PtokaX have nothing to do with DCDM and not have any support for DCDM commands... :rolleyes:
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Pothead

#181
This isn't a problem with either.  PtokaX has stopped wasting bandwidth on sending you stuff which you send to it.
Using 0.3.3.1 and typing one of them commands i see a message from every OP who's client supports them, except my own.

exlepra

#182
I know ptokax has nothing to do with dcdm commands, but something had to be changed, because with older versions the dcdm client listens/reacts properly to the commands entered to opchat while with 0.3.3.1 nothing happens.

But I think I found a strange thing which could be leading to find the problem:
I started a hub on local pc, and made a few op accounts, logged in to the hub with 2 clients as op, and what a surprise in the opchat every client only sees their own message in the opchat but nothing from the other typing, back to 0.3.3.0 and opchat works like before.

In my hub the dcdm client is on the same machine as the hubsoft, for a test logged in with the dcdm client from another ip and it is working.

So lets forget about the dcdm, it looks like 0.3.3.1 doesnt "like" the clients  from the same PC/IP where the hubsoft is.


exlepra

LOL guys, sorry for being lamer :)

changelog:
Added: Checkbox to profile manager to enable OpChat per profiles.


A few checkboxes had to be clicked and problem solved :)

Though it was funny that the we didnt realize the opchat wasnt working, perhaps it was due to that ops usually use the vipchat  and very seldom talk on opchat .

dragos_sto

some little problem whit ptokax
when user whit no nick whant to connect
i kant disconnect him in function MyINFOArrival(User, Data) , but when try to send a messege to tale him it a stupid ... whitout nick name
the messege it not receive

i try whit command SendToNick(Nick, Data)

SMF spam blocked by CleanTalk