Vincula issue ... HELP NEEDED !! asap pweeeez

Good day guys

ok .. here's the thing ...

the vincula i use has two probles

1) It doesn't show me getting -q'd ...

2) it says i'm banned when someone -q's me which triggers the auto-hop and i keep hopping for the amount of times it says i'm banned

for example ((takin from a room just now))

==================================

( 10:07p ) Mode : sazzle -q Fahad

( 10:07p ) Mode : sazzle -q lee

( 10:07p ) Mode : sazzle -q lee_x

( 10:07p ) * Hitman: you're not channel operator

( 10:07p ) Non-Subscriber.

( 10:07p ) Mode : sazzle +v sazzle

( 10:07p ) * Hitman: you're not channel operator

( 10:07p ) Non-Subscriber.

( 10:07p ) * Hitman: you're not channel operator

( 10:07p ) %#sazzle • Access was denied to %#sazzle

( 10:07p ) • %#sazzle Access Denied.

MODE +h Not enough parameters

No permissions to perform command

( 10:07p ) %#sazzle • Access was denied to %#sazzle

( 10:07p ) • %#sazzle Access Denied.

( 10:07p ) %#sazzle • Access was denied to %#sazzle

=================================

Notice it never showed me being deownered...and then the you're not channel operator ((which is fine because i try to owner up)) but then i get the "non-subscriber" and the "access was denied" messages..

how can i fix this .. i know the denied raw is "913" but i don't see how that would interfer with me being deownered ...

P.S. please don't ask me to download anther connection because i'm a vincula fanatic and to me no other connection is as good as vincula .. so i'd just like help fixing this "glitch"

looks like you are trying to kick the person who has -q you and you need to +q first then kick or you get the error you said

OZZY .. i changed it to trying to "-q" the user but the error remains

except i now see the "-q" on my nick

=============================

Prop : OWNERKEY : ei ( By Fahad )

( 11:31p ) Mode : Fahad -q Hitman

( 11:31p ) Non-Subscriber.

( 11:31p ) * Hitman: you're not channel operator

( 11:31p ) Non-Subscriber.

No permissions to perform command

( 11:31p ) %#Hitman • Access was denied to %#Hitman

( 11:31p ) • %#Hitman Access Denied.

=============================

this is going to drive me nuts coz i keep hopping when it says i'm banned

what script is it

turn the deowner protection off

I don't think raw 913 is just for bans. I think some other things might trigger it as well. However, Vincula uses that raw numeric to show bans, but that doesn't mean you are really banned, or you wouldn't be able to join the room again.

As for the "No permission to perform command" that only means you aren't ownered, and therefore cannot perform those commands until you are ownered. In many instances the script tries to perform the commands before you are able to join the room, and therefore you'd get that message which is why, though it is a slower process, you'd need to perform a check to see that you are actually in the room, and an owner first before making your script perfom the commands. Here is an example of what NOT to do...

on *:DEOWNER:#: {
  if ($opnick == $me) {
    hop
    access # add deny $ial($nick).addr 0
    kick $chan $nick [Don't ever deop me again]
  }
}

Here is a better way to do it...

alias getnicklist
  var %gn = 1
  :next
  if ($me isowner $chan) {
    if (%kicknick. [ $+ [ $ial($nick($chan,%gn)).addr ] ]) {
      access $chan add deny %kicknick. [ $+ [ $ial($nick($chan,%gn)).addr ] ] 0
      kick $chan $nick($chan,%gn) [Don't ever deop me again]
      unset  %kicknick. [ $+ [ $ial($nick($chan,%gn)).addr ] ]  
    }
    inc %gn
    if (%gn <= $nick($chan,0)) goto next
  }
}

on *:DEOWNER:#: {
  if ($opnick == $me) { set %kicknick. [ $+ [ $ial($nick).addr ] ] $ial($nick).addr | hop }
}
on *:JOIN:#: if ($nick == $me) getnicklist

This code maybe a bit slower, but at least it will check to see if you are actually in the room, and owner before it tries to execute the command. Also, it will kick others out who have that variable as well.

Ozzy10

its a script i made my self, except for the connection ((vincula)) ... and i have the anti-owner inbidded into the connection it self and i need it on 24/7 as G/N uses are "room taking" fans so removing it isn't an option i have ...

===

Warrior24 ... the thing is .. i do not leave the room to get that banned message .. it echos it in the room when i get deownered so its not about being in room or not ;(

===

and i asked a friend earlier and he said he was having same problems

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

Hitman says:

k did u get any "denied" messages

friend says:

(17:56:47) %#Hitman • Access was denied to %#Hitman

(17:56:47) • %#Hitman Access Denied.

(17:56:47) %#Hitman • Access was denied to %#Hitman

(17:56:47) • %#Hitman Access Denied.

(17:56:47) • Access Denied.

-

* /sockopen: 'urole' socket in use (line 3941, vincula.mrc)

-

%#Hitman No access

MODE +h Not enough parameters

(17:56:47) %#Hitman • Access was denied to %#Hitman

(17:56:47) • %#Hitman Access

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

so it must be some sort of error with vincula it self

==

anyway .. thanks for your quick replies ... appriciat it (Y)

sockwrite -n

Fusion i've tried changined the "Sockwrite -n" to "sockwrite -tn" but i still got the error of being banned ...

this is the deowner prot i have in the vincula connection

    if ($pos($4-5,-q $me)) && (%-qflood != on) && ($me !isin $1) {
      sockwrite -tn $sock($sockname,1) mode $scid($cid).me +h $msn.ownerkey($gettok(%read,3,32)) $+ $lf $+ kick $3 $right($gettok(%read,1,33),-1) $+ $lf $+ prop $3 ownerkey $rand(0,9999) $+ $me $+ $lf $+ access $3 clear owner
      set -u1 %-qflood on
    }

i don't know what's wrong with it but i went through the whole vincula and couldn't find a reason behind the deny posting every time i get deownered

Well, in many scripts when someone deowners someone else they also have a code to set the ownerkey property to something else. So, in that case you wouldn't be able to use the stored ownerkey you previously had.

best bet, MOVE ON WITH THE TIMES Vincula is dying .. get a new connection .. get out of the stone age..

althought i know there are alot of connections out there that are better than vincula in so many ways ... i find vincula the easiest to code stuff for ... or maybe its just because i started coding stuff to work well with vincula for so long it seems the only way i can get things to work .. i tried using other connections and all the codes i did went dead .. so i went back to using vincula again ...

BTW .. does anyone know if eXonyte is ever going to finish V.5 ? .. or has he givin up the project ?

Well if u find it easy to code for vincula why cant you use Nuclear-Msn it has the same coding style as vincula .I think Dogcollar is also an easy connection there is nothing called as so complicated with dogcollar .Anyway its your choice so go ahead with vincula .

Well your right xfusion but my point is nuclear is same as vincula (i.e Nuclear has vincula compaitabilty) .Even the dialog setup too, for example: if you want to open vincula control panel we type /msn.setup it goes the same with Nuclear .And even the socks are same .

eXonyte was in tulips room not too long ago, and expressed how he didn't have the time to make another Vincula. So, I think it will be at least a long time before he ever works on one again.

yah Warrior .. i spoke to Sky earlier today and he told me how he and eXonyte decided it wasn't worth their time to work on such big projects "Rewt3, Vincula5" and they had a life to live..

but hope he (exonyte) one day decides to finish it .. i know he was half way through it when he stopped .. and i hear their isn't that much left..

so either he finishes it or releases the code so others can finish what ever's left in it