This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

username + ??? (winident1.2 by FireEgl)

Support & discussion of released scripts, and announcements of new releases.
Post Reply
t
topdawg_b
Voice
Posts: 32
Joined: Sun Dec 07, 2008 7:13 pm

username + ??? (winident1.2 by FireEgl)

Post by topdawg_b »

the script is adding 3 random letters to my username .
I know it is probably a simple setting but I have been looking forever.
how do I change it to be just the username?
User avatar
Sir_Fz
Revered One
Posts: 3794
Joined: Sun Apr 27, 2003 3:10 pm
Location: Lebanon
Contact:

Post by Sir_Fz »

What script?
t
topdawg_b
Voice
Posts: 32
Joined: Sun Dec 07, 2008 7:13 pm

Post by topdawg_b »

not in a script that I know of
if I have set username "topegg" the whois will show topegga9u@etc...
or topegg09f@etc... it changes upon each connection and I want it to just be topegg@etc...
User avatar
arfer
Master
Posts: 436
Joined: Fri Nov 26, 2004 8:45 pm
Location: Manchester, UK

Post by arfer »

This has little to do with scripting so possibly in the wrong forum. However, I will provide as much help as I am able.

In the case of an eggdrop bot on an external linux shell the variable username should be set to your shell login name. This will then become the bot's identd on IRC. This is an extract from the .conf file for one of my bots (Colossus) which resides on a linux shell where my login username is terminus :-

# This setting defines the username the bot uses on IRC. This setting has
# no effect if an ident daemon is running on your bot's machine.
set username "terminus"

A network /whois gives the following response :-

Colossus is terminus@server.go.thud.me.uk * Noone shall pass


For a windrop bot, the situation is somewhat different. Generally you would set the variable username to something you want to see as the bot's identd on IRC and ensure that winident1.2.tcl was loaded, as per the following extracts from the .conf file of my windrop bot (osmosis).

# This setting defines the username the bot uses on IRC. This setting has
# no effect if an ident daemon is running on your bot's machine.
set username "osmosis"

# Ident script for Windrop by FireEgl@EFnet <FireEgl@LinuxFan.com>
# uses username value for ident name by default
# read the start of script for more documentation
# uncomment (remove # in front of line) next line to activate
source scripts/winident1.2.tcl

For some reason there is a Tcl statement in winident1.2.tcl which ultimately causes the identd to become the value of username plus 3 random characters. This is the statement :-

set ident(username) "$username***"

I removed the three asterisks (*) in this statement and restarted the windrop bot. This is now the output from a network /whois :-

osmosis is osmosis@cpc2-oldh2-0-0-cust793.manc.cable.ntl.com * osmosis

So, in response, I suspect you are running a windrop bot and that winident1.2.tcl is giving you the three random characters. I have no idea why the author of winident1.2.tcl randomises the identd by default, unless perhaps it is to avoid the appearance of clones in the case of more than one windrop bot from the same ip address.
Last edited by arfer on Tue Jan 27, 2009 6:32 pm, edited 1 time in total.
t
topdawg_b
Voice
Posts: 32
Joined: Sun Dec 07, 2008 7:13 pm

Post by topdawg_b »

you are correct and that was the case .
that did fix it.
what I found odd is I have 3 bots running the exact same scripts nothing is different except the bot name and the channel .
Yet 2 of them did not have the random additions and 1 did.
I then copied the entire folder from the one system that was doing it to a system that wasn't and ran it from there and it dropped the 3 random numbers. I haven't figured that out yet. But none the less it works. TY for the help
n
nml375
Revered One
Posts: 2860
Joined: Fri Aug 04, 2006 2:09 pm

Post by nml375 »

Moderated: Moved to the proper section and updated topic to include scriptname and author.

/NML_375
NML_375
Post Reply