Bind zones/ no bind zones

[cavedude]

Using one column works for me. On PEQ, I split this off into its own column, canbindothers. Using 1 column would certainly save a bit of space in the db. The one thing I didn't do yet is change the above code so you cannot bind anybody else in zones that are self only. The way that code is written, it only disallows melee guys from being bound. While this functionality essentionally is the same, it does bring up the point that you can bind other casters in these zones which we don't want in cases where they don't yet have bind affinity.

[Scorpious2k]

Originally Posted by cavedude

Using one column works for me. On PEQ, I split this off into its own column, canbindothers. Using 1 column would certainly save a bit of space in the db. The one thing I didn't do yet is change the above code so you cannot bind anybody else in zones that are self only. The way that code is written, it only disallows melee guys from being bound. While this functionality essentionally is the same, it does bring up the point that you can bind other casters in these zones which we don't want in cases where they don't yet have bind affinity.

So we need an additional test to make sure they are only casting on themselves (target=self)?

[Angelox]

There's another thing; some places have designated areas for binding non casters- Rathe Mountains is a good example - I remember there's a specific area there where a mellee could get a bind. I also remeber a rare item that came from there (Rathe Mountains) , allowed any one one bind anywhere in any zone (forgot what the item was called)

[cavedude]

Yeah, those zones are supposed to be self cast only. The class check in this case isn't needed. This would also allow us to override with soul binders or as Angelox mentioned items that cast bind affinity, while still preventing any class that doesn't have bind affinity from being bound in these zones.

The areas where you can bind will be a bit more tricky, I think. The gypsy camp in NK is like that as well. I was thinking just to make one of the gypsies a soul binder. Ghetto, but functional at least.

[Scorpious2k]

OK, I have this in with the variation I mentioned (canbind = 0,1,2).

It will be in 1112. Let me know if I broke anything.

[Scorpious2k]

1112 is in.

==06/17/2008
Scorpious2k (TheLieka): Ban by IP
Scorpious2k (cavedude/TheLieka): Ability to limit melee guys from being bound in certain zones. This changes the canbind
            column of the zone table. Value 0 means noone can bind, value 1 means only casters can bind, value 2 means
            anyone can bind in the zone (ie cities).

Required SQL:
CREATE TABLE `Banned_IPs` (
  `ip_address` VARCHAR(32) NOT NULL,
  PRIMARY KEY (`ip_address`)
)
ENGINE = InnoDB;

Optional SQL:
Insert into rule_values values (0, 'World:UseBannedIPsTable', 0);
Update zone set canbind = 2 where zoneidnumber in (1,2,3,8,9,10,19,23,24,29,40,41,42,45,49,52,54,55,60,61,62,67,75,82,83,106,155);