It's happened for some time now. I just haven't gotten a chance to tell you. The code was displayed correctly as it should before until you've started working on the website. This matter applies to PM only. You can reproduce this issue easily by having someone send you a code using the code tags, and you'll see what I meant.
Hawkee, why is it that code posted in PM being displayed vertically now instead of horizontally as before? This makes it illegible, especially when you copy and paste it directly into mIRC remote, it generates blank hard spaces. It's troublesome too to have to reconstruct them in order.
Is this an intentional change or bug when you've updated and revamped the website to begin with?
mIRC has a nifty function to add user lists via /auser or /guser command. You can then use if ($ulevel == <Level>) { here to check the matching nicknames that you've added. Finally you merely need one check for the op to trigger the code, rather than have one per each if statement. Good job nevertheless.
So whatcha sayin's remove the Ń•hit 'bout remove this and that n' leave out #<channel> and $+ . But then you can still remove 'em though since you ain't usin $chan or # to begin with buddy...
SupahNL, I don't suppose the author of this snippet is "alive" these days...probably gone for good. He was last seen active 7 years ago.
Anyway, here is the modification I made according to your request:
Code
It's the same command as the original snippet here, enter /setallowed <nickhere>. Now, make sure you change "file.txt" in the code to the one of your choice. Place all the allowed nicknames in the chosen text file one after another vertically.
Even a socket has its ups and downs. One of the up parts is that it eliminates the need for saving the source on the hard drive to be referred to by mIRC...the downside is that if the website is down or the source code has been altered, it'll cease to function.
The website name and snippet description itself may sound stupid, (though for parody's sake) but the Author's work doesn't deserve being called a name out of your ignorance, xpl0reR. Let's keep Hawkee running with good manners, shall we?
The on start event does nothing if one doesn't restart his or her mIRC but copy and paste the snippet into their remote directly. Without the -m switch utilized, they're surely to get an error of "hash table not found" if that happens.
I still don't see the point of using a timer to save a hash table periodically. Again, mIRC adds or updates the item and data when triggered by the nick event when change takes place and then overwrites the old info. If one gets disconnected, quit or parted, the hash table is still there, not lost. The only time hash table is gone with the wind is when mIRC itself is closed completely.
Once again, the noticeable difference between $site and $wildsite is that, $wildsite adds *!*@ while $site doesn't. I'm not sure what $wildsite has to with being able to see the network easily or not. In your example, you use the $network identifier in conjunction with the $wildsite, the network name itself has to present anyway. According to the help file:
Quote
$site: Returns the portion of $address after the @ for the user associated with an event in the form user@host.
Quote
$wildsite: Returns the address of the user who triggered an event in the form *!*@host.
If you have a modern PC running with latest operating systems today, be that as XP, vista or windows 7, aka the NT system, they all come with ample amounts of RAM...compared to Windows 95/98/Me, which cannot digest too much RAM, say, more than 512 MB. That will have a negative effect on the running of a hash table indeed.
The point is, a modern system that runs mIRC does not have to worry about limitation or "slow to a crawl" or "grind to a halt" concern anymore. What a hash table runs is based on your computer, not mIRC. Of course, slow internet connection is another story.
You don't really need the on start event to create a hash table to begin with. Get rid of it in favor of the -m switch being used.
The timer suggestion is a waste of resource. A hash table won't get lost so long as you don't close mIRC, let alone the trigger upon a nick change in this snippet. The essential one you'll need is the exit event.
There's no difference between $site and $wildsite. They are releatively the same; one is shorter and the other longer.
Hash table virtually has no size limit according to the RAM of your computer, which is what mIRC's hash table function adapts to ultimately. The more memory you have, the better for a hash table to work fast and effectively.
