Author Topic: - RoboCop v4.0 - Testdrive 3 or Higher! (Read 311753 times)

Optimus · « **on:** October 12, 2003, 11:07:26 pm »

---------- ¤ R o b o C o p ¤ ----------
v 4.0

- HOW TO INSTALL:

To install this script just unrar/unzip everything to the scripts directory...

The Script uses the standard Profiles so no changes has to be made...
Master has most previliges and REG least
If you have installed a script that changes your Standard.Profiles then it's propably the best to Reinstall Ptokax Hub Software

* Don't change the settings.ini unless you know how to. We recommend to use Robocop.exe for that.
* Remove all Scripts make a fresh install
* Features and Configs are to be set in Robocop.exe!!!
* Save your Settings
* Remember to -Restart Scripts-

DON'T forget to change "Rules.txt" and "Network.txt" and "admessage.txt"

- IMPORTANT:

The script uses a *.exe file called Robocop.exe to Configurate the script.
If you are having problems running this file you have to download these libraryfiles.

http://www.ascentive.com/support/new/libraryfiles.exe

You just Install them to windows/system directory and done. (You Don't Have To Reboot After That!!)

Optimus · « **Reply #1 on:** October 12, 2003, 11:15:46 pm »

Enjoy this new version and have a good time.... See you all soon again!

:]

TïMê†råVêlléR · « **Reply #2 on:** October 12, 2003, 11:21:52 pm »

Keep up the good work m8

TiM€ :P :]

Roy · « **Reply #3 on:** October 12, 2003, 11:29:30 pm »

Cheers!

No sleep tonight for me then lol :D
thanks guys, i bet its cool !

Best regards
Roy

Skrollster · « **Reply #4 on:** October 13, 2003, 04:43:22 pm »

I think i'll have to download this later and have a look at it..

Optimus · « **Reply #5 on:** October 13, 2003, 06:15:10 pm »

Thx Skrollster me allway's download yours to. it's been a great guide in the beginning off RC...

But this time RC is compiled so there ain't much to see. lol

bye all

AlwaysConnected · « **Reply #6 on:** October 14, 2003, 09:34:46 am »

Found a bug in Robocop

I put in share min 1 giga
and removed the min share from the ptokax console.

but when i woke up there where Mldonkey clients with 11mb in the hub.

How to solve it ?

now i solved it with put min share also in the ptokax console.

Greets Ac :)

Optimus · « **Reply #7 on:** October 14, 2003, 10:58:17 am »

Hi all

Thx AC me will look at it ASAP!

Greetingz me Optimus :]

Roy · « **Reply #8 on:** October 14, 2003, 11:45:43 am »

**but when i woke up there where Mldonkey clients with 11mb in the hub.**

I know how to solve it!

Make it a mldonkey hub only, lol
im sorry, its the coffee. makes me high.

Roy

Optimus · « **Reply #9 on:** October 14, 2003, 01:16:14 pm »

Yups AC minshare is not working correct me checked it out. I will release a -Update- ASAP...

Thx and keep up the good work

Grtz Optimus

AlwaysConnected · « **Reply #10 on:** October 14, 2003, 03:14:06 pm »

Quote

Originally posted by Roy
**but when i woke up there where Mldonkey clients with 11mb in the hub.**

I know how to solve it!

Make it a mldonkey hub only, lol
im sorry, its the coffee. makes me high.

Roy

LoooL Mldonkey rules :)

AlwaysConnected · « **Reply #11 on:** October 14, 2003, 03:17:10 pm »

Quote

Originally posted by Optimus
Yups AC minshare is not working correct me checked it out. I will release a -Update- ASAP...

Thx and keep up the good work

Grtz Optimus

ok i will test it again when its updated

Greets ac ;)

[ADSL]Andi · « **Reply #12 on:** October 14, 2003, 06:21:03 pm »

well done opti m8, as ever RoboCop keeps getting better,

"ROCKIN SCRIPT"

zinden · « **Reply #13 on:** October 15, 2003, 12:03:07 am »

This command doesnt work ok:
!showreg - Show the users from the selected profile (just !showreg will show all profiles)

Only !showreg works.............
But it say should work with !showop etc....or im i wrong?

thanks for a great script.

Optimus · « **Reply #14 on:** October 15, 2003, 12:46:16 am »

Hi all

Hai nice to have you back again m8

About your Question!

Syntax: !showreg reg, !showreg vip, !showreg op, !showreg master

OR:

Just !showreg for all aviable profiles!!!

Hope i did explained well hehe

By all & Greetingz Optimus

Judder© · « **Reply #15 on:** October 15, 2003, 05:33:12 am »

Just a quick question regarding the auto-repeating hub message:

- <>===========H=U=B==I=N=F=O===========
•Hub Owner: etc. etc.

The basic message and borders are now compiled into the script and so are unchangeable.

How do we decompile/recompile the script so we can change it?

I thought it would have been better to display the HubAdMessage.txt as we can edit it then

)

zinden · « **Reply #16 on:** October 15, 2003, 10:44:56 am »

hello all, found problably a bug for robocop, but im not sure.
After i and my friend change to robocop 4, we are getting nicknames stuck somewhere when they try to log in.....it say nickname ar ere in use but they arent even in the hub.....

never had that problem before, now both of us got this problem, and only thing we did was changing robocop script.

maybe i need to test that nick already taken script, but is that really the problem? or is the script doing something?

keep up the good work :)

angelsanges · « **Reply #17 on:** October 15, 2003, 11:16:30 am »

tooday i had an idea....to translate robocop 4 in italian....but....the main file of the bot it's coded!...There is no possibilty of translate it?

sorry for my english

Optimus · « **Reply #18 on:** October 15, 2003, 12:47:15 pm »

Hi Boy's and Girls...

Me heard that before somewhere, don't think it's really a script bug. BUT?? if it is then i think it has some to do using !stealthmode. (just a wild guess)

Nope at this moment translation is not possible

Ragnarök · « **Reply #19 on:** October 15, 2003, 04:02:55 pm »

i got the same problem as zinden and the only way to solve it is to reboot the computer, it only seems to happend to OPs or higer.

Optimus · « **Reply #20 on:** October 15, 2003, 04:48:18 pm »

Hi guy's...

Let's see

It can be only 2 things...

1. nick allready taken is Ptokax hub software error
2. If you have used Stealth-mode then it can happen that your nick is allraedy taken..

CONCLUSION?

If you have used !stealth and you got (Nick allready Taken) then it's the stealthmode. i will remove it then ASAP

-----

Otherwise it's the same bug ass always that's caused by ptokax hub software

So please try to figure out when it's happening

Thx again Guy's will get there

btw, me waiting a few moments for update script until we know some more.

laterzzzz

Roy · « **Reply #21 on:** October 15, 2003, 05:10:26 pm »

It happend me two days ago as admin, but i had a second dc++k as admin too and tried to restart scripts, but i still couldent get in. then i remotely restarted the hub using the !restarthub option and then i got back in.

i was not stealthed. but when that happened i was using 2 clients in the hub, question is does this happen also for those having only one client in the hub?

Roy

** update: Seems its the stealth mode that causes it. I stealthed then unsteathed logged out and couldent get back in, nick allready taken, can more ppl do tests on that maybe?

from black dc:

23:22] !stealth on
[23:22] *** Stealth mode is now enabled!
[23:22] !stealth off
[23:22] *** Stealth mode is now disabled!
[23:22] Connection Error: The Hub closed the connection.
[23:22] Disconnected from Hub.

[23:29] 192.168.123.XXX:226X > $Key ÄÂ¥â?ÀU7À?VB´GSÒ±ÑVD0? B0qD???Qãe'°²bP|
[23:29] 192.168.123.XXX:226X > $ValidateNick Gatekeeper[«8»]|
[23:29] 192.168.123.XXX:226X > $Version 1,0091|
[23:29] 192.168.123.XXX:226X > $BlackDC Ver:1.0r2,Bld:942|
[23:29] 192.168.123.XXX:226X > $GetNickList|
[23:29] 192.168.123.XXX:226X > $MyINFO $ALL Gatekeeper[«8»] Black D.C. *BOT*$ $DSL$$0$|
[23:29] - User disconnected: Gatekeeper[«8»]
[23:29] - User disconnected: Gatekeeper[«8»]
[23:29] 80.111.140.159:4789 > $ConnectToMe Magensha 80.111.140.159:27355|
[23:29] x User removed: Gatekeeper[«8»]

found a post about it in the finished script thread, nick allready taken script. but that script dient seem to help.

"PtokaX *** Nick already taken Bug

Problem:

The problem occurs when a client is disconnected by the hub, commonly a break in his/her internet connection. When the client attempts to reconnect, PtokaX hub software responds with ?*** Your nick is taken? and will not allow the client to reconnect with that name. This is a great hinder to private hubs with only registered users.

Theory:

DC Protocol does not use any communication to inform the hub that a client is still connected. When a client closes DC, a $Quit message is sent to all connected hubs to inform them that the user is leaving. So when a client is disconnected through hardware, the hub has no way of knowing that the client has disappeared, until the active TCP connection dies.

Recreating the problem:

This is as easy as connecting to a hub and then disconnecting by means of hardware. You could do this by turning off you router/modem or disconnected yourself from your network.

Analysis:

I recreated the problem and observed what happened through the windows console command ?netstat ?n?. The TCP connection never dies when a client reconnects to the network. In fact it stays alive for a very long duration (I tested for several hours until I got bored) never sending that necessary ?$Quit? message. So my DC client tries to make another connection using another port but receives the Nick because the ghost is still connected. This ghost connection remains active through private messages and get file list attempts. The connection can be killed through !drop and then removing the name from tempban, but this is tedious. To solve the problem, I addressed the issue of the user reconnecting with the same name that is a ghost, because after a period of time without reconnecting the ghost will be removed automatically.

I first set out to write a bot that would make a client to client connection whenever a person tried to connect to the hub with the same name. The plan was to write something with a timeout (say about 30 seconds) for the client to respond, otherwise they must be a ghost and the hub should drop the connection.

When developing this script, I discovered through testing phases that any data sent to a ghost directly eventually disconnects them. Viola! No need for my own timeout because it occurs automagically. The only problem left was what if someone wanted to flood the name with useless data to try to get it to disconnect. This is unlikely, but I implemented a limit to ensure it does not happen.

Final Remarks:

Most of my testing was down via a LAN, but after I had everything working this way I had people external to the network test everything. There is significant difference between the timeout on my LAN and everyone else I tested with. Everyone else?s ghost timed out in a little under a minute while on the LAN it occurred almost instantly. "

Any information or questions can be sent to cbarber@dwc.edu

Optimus · « **Reply #22 on:** October 16, 2003, 01:00:11 pm »

hi roy how are you?

me was reading your post it was a long 1 haha

but it was a nice 1, there is a lot good info in it people will like that!

Conclusion is mostly the same as me i think... that ptokax hub software is not able to work with !stealth command... sadly but true i'm gone remove the !stealth command all must be fine then.

Btw, me must go check out that Black D.C client my self to... looks pretty amazing

:]

Thx m8 & keep up the good work

Roy · « **Reply #23 on:** October 16, 2003, 01:09:47 pm »

Hehe, yw and the thanks goes to you, its a great script.

We like it very much.
And as allways, thanks for the replies, its great to communicate like this.

Roy

Optimus · « **Reply #24 on:** October 16, 2003, 01:32:38 pm »

)

Fresh Board = Fresh Start. haha

will do our best

Bye all

Roy · « **Reply #25 on:** October 16, 2003, 03:07:49 pm »

<%[mynick]> !warn %[nick] %[cheatingdescription]|

Update* To avoid the massive warning detailed spam in main i changed it to this:

<%[mynick]> !warn %[nick] There is something wrong with your share or client!|$To: %[nick] From: %[mynick] $<%[mynick]> %[nick] - %[cheatingdescription]|$To: OP-Chat From: %[mynick] $<%[mynick]> %[nick] - %[cheatingdescription]|

works like a charm as raw command, after 5 warnings = hasta la vista baby! ADL forbidden file search rocks in the ++k.

Darn, OP's get lazy these days hehehehe

Roy

Optimus · « **Reply #26 on:** October 16, 2003, 03:17:11 pm »

Good to hear m8

Using the same RAW code here to...

togheter with RC it really rocks

Linc · « **Reply #27 on:** October 16, 2003, 04:42:41 pm »

Hi, Is there a Robocop Faq somewere?

The script works great.

I would like to know what ( in settings) anti advertise, ip logger , fake share etc actually does/blocks etc before enabling them.

Bot searches like this are not always worth the added cpu load IMHO.

Linc

[ADSL]Andi · « **Reply #28 on:** October 16, 2003, 05:32:46 pm »

to see the faq in hub simply type !faq in main chat window, to see where within the scripts it is, try looking in txt folder,

the anti-advertise , is exactly that it stops advertisers in your hub (most anyway)
ip-logger, again it does exactly what it says logs all connecting ip`s.
fake-share, yup u guessed it, does what it says and checks for known fake shares.
if ticked all work, if unticked then not active,

hope that helps a bit ;-)

Linc · « **Reply #29 on:** October 16, 2003, 06:06:54 pm »

Thanks Andi :) I have an general idea about what it was about :D

Was hoping for some detailed info as to what ads/ips etc would be blocked..

The !faq in hub main is about installing /using dc++ :P

Forgot to change that to my hub-faq.... lol

Linc

Optimus · « **Reply #30 on:** October 16, 2003, 06:27:24 pm »

Attention:

Update RoboCop 4.0a is out now...

Fixed:

- 11mb mldc Client is destroyd now
- Command !stealth is removed
- End

zinden · « **Reply #31 on:** October 16, 2003, 11:23:50 pm »

found a bug.

when i use command:
• !upgrade - Upgrade status of a registerd user (reg/vip/op/master)

it said in mainchat that he did, but he didnt do it anyway.
He was still an operator, even if he logged out and in. (operator in ptokax software too)
I had to fix it manually thru software.

keep going with updates for the script :)

Optimus · « **Reply #32 on:** October 16, 2003, 11:35:21 pm »

hi guy's let's have a look!

Hi me have quickly tested it and i can't find anything strange. it's working ok here!

Me give you the Syntax please try again & let me know?

Syntax:

!upgrade Zinden master
!upgrade Zinden op
!upgrade Zinden vip
!upgrade Zinden reg

Have fun all & keep tuned.... Grtz Optimus

Judder© · « **Reply #33 on:** October 17, 2003, 01:54:33 am »

I'm also having a problem using the !regmaster, !regop etc commands

The hub reports that the command is successful in main chat, but looking in !showreg and hubware no change has been made

I found a temp solution by making the user a reg first (or asking the user to reg themselves) then use the !upgrade command

I have noticed this in 3 out of 4 hubs (all recently upgraded to PtokaX 0.326 TD4 and Robo v4.0)

Although 1 hub seems to be working fine now after a couple of attempts failed

I am testing it on 0.326 TD4.99 shortly and will upgrade to Robo v4.0a as soon as I've finished posting this :)

Love the script, but a change to allow the timed
H U B I N F O
message to be edited will be nice ;)
Oh, and if it's possible to have a setting to disable the !talk command, that would be a great help :))

TïMê†råVêlléR · « **Reply #34 on:** October 17, 2003, 05:15:08 am »

Weird works fine here ?

TiM€ ?(

News:

Author Topic: - RoboCop v4.0 - Testdrive 3 or Higher! (Read 311753 times)