NuClearMSN - Bug File

i have noticed a bug where if the script gets disconnected it will update the passport but fail to rejoin sometimes.

After that has happend it will not join any rooms, it requires the entire script to be restarted to get it going again

i have noticed a bug where if the script gets disconnected it will update the passport but fail to rejoin sometimes.

After that has happend it will not join any rooms, it requires the entire script to be restarted to get it going again

i have noticed the same thing. and i belive when u get kicked sometimes it doesnt rejoin even if u have it set to rejoin. the restart can be a pain if u have like and mp3 player running or games and u have to shut it all down and start it up again...

i'll work on a fix. unfortunately i haven't had this problem. i just submitted an updated version (6.0.2) for release which should be available soon enough.

for now, a work around would be to wait until the passports have finished updating, then use this alias

alias msn.reset { sockclose msn.* | msn.lookcon }

then close the status windows for your rooms and rejoin them manually.

Hey, when I join rooms, sometimes i get this message in status. It does it a lot more than Im posting, but you get the drift.

* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1293, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1293, nuclear.mrc)
-
* /cline: insufficient parameters (line 1293, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)
-
* /cline: insufficient parameters (line 1294, nuclear.mrc)

Here is line's 1293 & 1294

         if (G* iswm $9) cline $color(gray) $msn.scn($4) $wnick($msn.scn($4),$msn.decode($8),1).num

          else cline $color(listbox text) $msn.scn($4) $wnick($msn.scn($4),$msn.decode($8),1).num

I still get in the room fine.

i cant really comment on the connection as, i use my own.. lol but for that bug.. make sure u .who the channel and /names one and a while (the connection should do it when an event happens) or just hash gates lol

WOW i just noticed what was posted "line 1294" wtf are u doing to the connection lol ohh another vincula lolll

That was a total waste of space. This is a post for Nuclear, if you don;t know about Nuclear then there is no point in posting. I do hope that these 3 posts will be deleted as they are extremely pointless. Please do not post unless your answer actually correlates with the question. Thank You.

Hey Vex, you know why I'm getting these error messages?

yeah no kiddin, his connection is prolly half vincula and the other half is nuclear lol

travis .. i get that error too. it's because the script executes before mirc knows you're in the room. if you turn of 'show away users' in nuclear command, it won't happen anymore. of course, it won't show away users anymore either... but that only applies to mirc's built-in nicklist anyway. ill work on a permanent fix tho.

lmfao, dont be a smart ass (and by the way steph, if ur talking about my con being half vincula.. lmfao ur funny, my cons only about 10.0kb's so.. thx) lol

and vex, i dint say nothing was wrong with ur connection

Travis : i was refuring to his connection and the problem u people were discussing sheesh hold ur balls

13 Dec 2005

Happy Birthday Vex'

13 Dec 2005

 

Happy Birthday Vex'

Happy birthday vexation wish ya happy returns of da day

Not really a bug, but erm, in the access list, there isn't a "clear deny's" option? or am i totally missing it? If there isn't maybe you could tell me how to add a feature like this, it wouldn't have to be in the dialog, just a command like /access # clear deny

Not really a bug, but erm, in the access list, there isn't a "clear deny's" option? or am i totally missing it? If there isn't maybe you could tell me how to add a feature like this, it wouldn't have to be in the dialog, just a command like /access # clear deny

I figured it out:

alias cleardeny { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear deny }

alias clearhost { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear host }

alias clearowner { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear owner }

alias clearvoice { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear voice }

alias cleargrant { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear grant }

alias clearaccess { .sockwrite -tn msn.server. $+ $cid access $msn.get($cid,fullroom) clear }

Right click in the access list. A whole slew of options are there, one of them is to clear all entries.

Hey get ready for the NEW NUCLEAR!!!!!! Check out the site http://www.immortal999.com