Warrior124

This addon is for dialogs using an mdx style list. The reason for this addon is because the /didtok protocol won't work for lists using mdx.dll. Here is the code... ;How to use: /mdidtok dialogname did Character text ;Example1: /mdidtok Testlister 1 44 Test1,Test2,Test3,Test4 ;Example2: /mdidtok Testlister 1 32 Test1 Test2 Test3 Test4 alias mdidtok { var %mdialog = $1 , %mdid = $2 , %mchar = $chr($3) , %mdidtok = $4- write mdidtok.txt $replace($4-,$chr($3),$crlf) if ($dialog(%mdialog)) loadbuf -ro %mdialog %mdid mdidtok.txt .remove mdidtok.txt }

You'll have to upload your image to somewhere like ImageShack. They'll give you a link to your image.

Buzzen isn't bad at all. When I was there the day I saw msn chat was going to close in October I thought it was a very good place to go, and chat. However, like err0r said, I am concerned about what will happen to buzzen after msn chat closes, because of the ocx issue. I don't have anything against buzzen at all, and I would like to make scripts/addons for them, but I don't want to make them if buzzen won't be around much longer. That would be work down the drain. I now regret making scripts and addons for msn chat that I have made recently, because that was work for nothing.

I think buzzen is a pretty good chat service myself. I've been there once, and I liked it. However, my only concern about it is when msn shuts down what would that mean for buzzen since they use a clone of the msn chats ocx? If I can get this question answered, and if buzzen will keep going then I would start making some scripts, and addons for buzzen as well. Right now, I'm concentrating on VSIXc at the moment, because they have their own ocx, and won't be affected by msn's shutdown of chat service.

ty, Josh. Still alot more work needing to be done, though.

ty, everyone. x-fusion, I'll be there shortly.

I just now clicked on them, and they displayed to me. However, I edited them to show, instead. I was trying to save some space, lol.

Here are a couple more screen shots.

lol, ty Kronic.

Here is a connection addon I'm working on at the moment for VSIXc...

ty X-Fusion. lol, sorry Ozzy. I was sleepy when I put this screen shot up, and thought I hit the ircx button.

Here is a screen shot of WebchatZ_VSIXc2...

Here is a screen shot of "MAME Project". For those unfamiliar with MAME, it is an emulator that emulates arcade games. MAME is one of the most dificult emulators to understand. So, I made MAME Project for irc to better be able to use MAME better. When using MAME always make sure your games are legal copies.

lol, that's what I thought before too, webagent. However, there is a dll out there called nicklust believe it or not, lol.

Hey Kronic. Sorry for the late reply, mate. I've came up with this code. I tested it out, and it works. If you need any more help please let me know. alias ff { if (!%ff. [ $+ [ $1- ] ]) || (!$exists(%ff. [ $+ [ $1- ] ])) set %ff. [ $+ [ $1- ] ] $shortfn($findfile($mircdir,$1-,1)) return %ff. [ $+ [ $1- ] ] } on *:JOIN:#:{ if ($nick == $me) { dll $ff(nicklust3.dll) Mark $window($chan).hwnd lust_callback nodefgroup hottrack staticedge hideempty underlinehot rowselect dll $ff(nicklust3.dll) SetGroupText $chan 1 > UnVoiced dll $ff(nicklust3.dll) AddGroup $chan 2 . 2 > Owners dll $ff(nicklust3.dll) AddGroup $chan 3 & 3 > Admins dll $ff(nicklust3.dll) AddGroup $chan 4 @ 4 > Ops dll $ff(nicklust3.dll) AddGroup $chan 5 % 5 > HalfOps dll $ff(nicklust3.dll) AddGroup $chan 6 + 6 > Voiced dll $ff(nicklust3.dll) SetGroupPos $chan 1 end 1 } P.S.: I added the ff alias so that wherever you put the nicklust3.dll your script will be able to find it for you automatically. Best wishes, mate.

Hey Kronic. I'll try to find out what is happening with nicklust. However, here is where you can get the hammers. Gold Hammer Brown Hammer MSN Butterfly

Well, the main reason why people should never hard code their work is because not everyone has the same dlls, and such in the same places that are required in hard coding. This can lead to people not wanting anything else that you work so hard on, and all that work will be for nothing. So, here are some simple things you can do to achieve the same results without having to hard code. Here is one of the simplest codes you can use to achieve the same results, but works better than hard coding... alias findfile2 { if (!%findfile2. [ $+ [ $1- ] ]) || (!$exists(%findfile2. [ $+ [ $1- ] ])) set %findfile2. [ $+ [ $1- ] ] $shortfn($findfile($mircdir,$1-,1)) return %findfile2. [ $+ [ $1- ] ] } Now you have a code that works just as well as hard coding, but can find the needed file for your work without having to manually look for it. Once the variable is stored it will work just like hard coding. Here is an example on how to use it... alias mdx return $findfile2(mdx.dll) alias dialogmdx return $findfile2(dialog.mdx) on *:dialog:mp3:init: .dll $mdx SetMircVersion $version .dll $mdx MarkDialog $dname .dll $mdx SetControlMDX 10 Positioner size maxbox minbox > $dialogmdx } This is just a sample code, but it gives you an idea on how to use it. Remember that hard coding works, but only if the right files are in the right place. This code works better. So, I'd better never see another hard coded script again. Just kidding, lol, but please, PLEASE use this code instead. Beleive me when I say you'd do the world a huge favor, lol.

The reason for that is because many people hard code their mp3 players (meaning they put a direct link to a file ($mircdirdlls\mdx.dll) like that). However, they seem to forget that not everyone has the same dll in the same location. That is why you are seeing numbers, and funny letters instead of icons. The best thing to do is just post the mp3 player code here, and one of us will try to fix it for you to work better.

This will check to see what operating system you are running, and if any of those systems are found will execute whatever commands you wish. The else statement will only activate if said operating systems aren't found, and will execute whatever commands you put in... on *:START: { if ($os == 95) || ($os == 98) || ($os == NT) || ($os == ME) || ($os == 2K) || ($os == XP) || ($os == NET) { <commands here> } else { <commands here> } }

I apologize hixxy, and yes you are right. It is the fault of the user if they do that. However, I like for my scripts\addons to work reguardless of what the user does, lol. When I first started scripting I would hard code, myself because I knew it was faster. However, I'd get complaints about how my scripts/addons wouldn't work, because it wasn't finding some files\dlls. That is why I started using $shortfn($findfile. Yes, it does slow things down some, but at least I know it will work even for people who does move things around. I agree with you. Hard coding is alot better, and I suggest people don't move files around, or whatever.

Well, ask yourself this. Would you wnat an addon that doesn't work, because you didn't know you had a dll in the wrong folder, or would you want something that works? Like I said. There are better ways to code. However, what I gave was just an example. If you don't like it you don't have to use it. If you know how to make your own script then it is always best to do so. that way whoever does has a script they can suit to their needs, and wants. P.S.: By the way, this post isn't about who can make the better script. It was about getting help for a problem. Which by the way no one seemingly was able to help me out with, and I found the solution on my own. So, please keep the remarks to yourself. Also, unless the script one uses is like one of the biggest scripts in the world with so many files in there it is like counting stars, $findfile doesn't slow the script down enough to be that much of a trouble. Crytons code is terrific, and I suggest anyone to use it. However, don't knock someone elses coding. Especially if one has found a way when no one else was seemingly able to, and decides to share what he/she has found to help others. If you have a better way to code, then do like Cryton did, and volunteer it if you wish, but don't knock others for finding solutions when you didn't.

lol, so we're going to get into who has the best coding? I suppose there are better ways to code, and such, and I never claimed that the code I provided was the "only" way to code it. I was just providing an example, and yes. Hardcoding is always better, and much faster. However, lets face it. People don't keep the same files in the same directories. That is why a huge percentage of addons don't work, and that is why I provided the code in my coding to search for the dlls, and again. It was just an example coding. Not something you neccessarily have to do.

Not true. $mircdir refers to the main directory. However, $findfile($mircdir finds the file being searched for in both the main directory, and also the sub-directories as well. Otherwise $findfile is a useless command.

Exactly, lol.

Actually, it means that if $2 is either $null, or doesn't exist, or above 100 it will ban permanently. Otherwise if $2 is from 0-100 it will ban for that amount of time times 60.