Skip to content
NuClearMSN Connection

NuClearMSN - Bug File

A TG007 community discussion started by vexation.

Discussion 35 posts
Pinned topic
Pinned Open
Topic #2931 · 35 published posts · 5,648 views

Known Issues in NüClearMSN >>>

 

1. Some UK users have minor issues with room lister.

... room lister shows HTML where the number of users in a room should go. again, i can't reproduce this error so i can't fix it. hopefully someone will find a fix :P

 

------ - - - - - - - - - - - - - - - - -

progress on these issues will be posted in this thread.

------ - - - - - - - - - - - - - - - - -

 

If you find a bug, please post it in THIS thread.

Edited Dec 12, 2005 11:32 PM by Ozzy10

bfush.PNG

Spec Kicker doesnt kick specs. Cheers. I havent looked at the code, but could it have something to do with the whole ctcp reply thing and this connection?

Edited Mar 4, 2005 9:09 AM by Travis

On Windows 98se, using mIRC..

 

uhm, it won't list colors, and refuses to list all the fonts.

 

So I had to force it to 'Teal' and Lucida Sans Unicode.

 

Lack of cloaking sucks too btw.

 

 

The spec kicker doesnt use ctcp reply, it uses O, which means unsubcriber. I know previous version the spec kick worked , I dont think he would change it and yes it works, make sure its turned on in options.

Edited Mar 4, 2005 2:34 PM by Molsonâ„¢

Custom Computer

AMD Athlon 64 x2 Dual Core 5200+

Asus M2N-SLI MOB

2GB DDR2 @ 800mhz

160GB Hard Drive

NVidia GeForce 8400GS 256

there is no stealth mode and won't be, sorry, but it gets abused too much. as for 98se i dont have a machine to test it on that platform so i dunno.

 

the spec kicker does work, just try what molson said.

bfush.PNG

Ok, see, I'm used to just clicking that button in the status bar twice which turns on the script kicker and chooses ban. Now Ive done that AND gone into the control panel and turned it on. And yes it works now. Thanks Sorry about that message you had to delete. Hope you enjoyed the link. Im outta here for a few months, be interesting to see hwere evrything is at when I get back. Adios Muchachos. Thanks for the great support Vex.

Edited Mar 4, 2005 4:42 PM by Travis

Ive noticed every now and then nuclear stops seeing gates, seems to be mainly when another script -o +q 's it.

Im not sure if thats the exact cause but it stops seeing any gates, even its own.

to fix it i have to unload and reload nuclear.

what are you using to retrieve the gates?

bfush.PNG

in the nick list i use

.Copy User GK:/clipboard | /clipboard -a $$address($$1,1)

 

but i only use that test, the main time i notice its stopped seeing gates is when people enter and when my script trys to add access

 

I know im being pretty vauge, but im not 100% sure what causes the problem. ill have to do a few more experiments and get back to you.

try using $ial($$1).addr instead

bfush.PNG

the Spec KIcker Works it kicks them but when ban is turn on it dont ban them they dont show up on the access list and they come back other than that exelent work on the spec kicker

Edited Mar 18, 2005 7:44 AM by LATIN
try using $ial($$1).addr instead

Nah that didnt work either, i dont think it has anything to do with that, the script stops seeing gates anywhere.

 

even in nuclears access popup, if i right click and hit "add self" it just returns an error

"NuClear Access Bad command"

 

it just happend again when i hopped, there is another script in the room that has my script on auto owner but my scripts account is only a host.

So it joins with brown, then the other script owners it up.

I have a code to automaticly add access when golded but like i said, when the script stops seeing gates it wont work.

It just adds OWNER 0!*@*$* instead

The same thing happens when i tick the the auto access switch in nuclear command

yea, i've noticed this problem in my connection as well and i think it has something to do with the decoding of nicknames cause Vincula virtually never has that problem. I think the only way around this little issue is if a database is kept with the user's nickname and gate so that you can just use an alias to retreive the user's address. I can't think of another way around it.

yeah im having the same prob when i try and ban someone threw the access...it wont take at all

Rumbaar wrote a great code for logging gatekeepers in their own window. It works great! I see no reason to keep tryin to reinvent the wheel unless you truly revolutionize it.

./sockwrite: 'msn.mirc.1' queue would exceed 16384 bytes (line 36, nuclear.mrc)

 

 

bug???

I dont understand why noone else is having trouble connecting to msn's servers with Nuclear 6.0.1 I get on fine with version 6.0.0 btu I have never been able to connect to msn with 6.0.1. I have only had it loaded on a fresh new mIRC. Whats up??

 

Whats the difference as well? What am I missing?

Edited Mar 25, 2005 6:14 AM by Travis

o.O

 

nothing in the connection part changed from 6.0.0 to 6.0.1. try downloading again? i dunno.

 

does it simply not try to connect? or does it try and fail?

 

open the debug window using the command /msn.debug s and try to connect. post the contents of the debug window here.

bfush.PNG

IM tryin to make a remote command to load the access list. I have tried many different thinsg and finally decided on just tryign to use the alias msn.access.load thinkin that may be possible. The problem I am finding is the filename. Getting it to load the actual file.

 

Here is the code,

alias msn.access.load {
 :access.load.check
 var %f = $shortfn($$sfile($scriptdir,Load Access List,Load))
 if ($exists(%f) == $true) && (*.acc iswm %f) {

 

Lets just say the file is called Access.acc and is in a folder called Nuclear ( /Nuclear/access.acc ) Any Ideas??

 

You worked your voodoo or something. I swear I tried that 6.0.1 about 7 or 8 times, and every time all it would say was "Opening lookup server connections" and tghen just scroll that. And then, of course, I go to load it in a new mIRC, like always, to try what you said and it worked. I dont get it. Wuteva, THANKS! you better nto have a voodoo doll of my computer or something!!