Bind zones/ no bind zones

[BatCountry]

I think pre-Velious they had support for regions of zones being unbindable.

This may be faulty recollection, but I remember having to get bound right up against the wall on one corner of OT's city keep because I was KOS there and had screwed up my FV faction hunting those faerie dragon things.

If I recall correctly, I had just about enough time to squat, memorize SoW, cast it on myself, and run like hell before a patrolling guard ganked me after I died.

[ChaosSlayer]

bad bad bad code.
cuase it forcefuly hinders melee classes.
If we must have melee binding restriction - I much rather have an extra collumn like cavedude said
what we realy could use is a confirmation box when person is been bound, so evil casters do not bind melees say in VT
under Aten Ha Ra feet

[cavedude]

Why is it bad? I have it up on TGC right now (though, I did add the db column, I'll diff that and post later) and it's fine for the most part. Melee toons can only be bound in city zones, this code does preciously that.

I don't see a need for a confirmation box, it isn't Live Like, you have to be grouped with the caster to be bound by them, and since they can only be bound in cities, there is no real way to exploit bind affinity... Now, sacrifice and rez on the other hand... those could use confirmation boxes.

[ChaosSlayer]

Originally Posted by cavedude

Why is it bad? I have it up on TGC right now (though, I did add the db column, I'll diff that and post later) and it's fine for the most part. Melee toons can only be bound in city zones, this code does preciously that.

I don't see a need for a confirmation box, it isn't Live Like, you have to be grouped with the caster to be bound by them, and since they can only be bound in cities, there is no real way to exploit bind affinity... Now, sacrifice and rez on the other hand... those could use confirmation boxes.

didn't you read my argument with Angelox?
Melee bind restriction SUCK and unfair.
And hard coding of this into main code is horible cause this kills server admin options of NOT having this stupid live-like feature.

As far as beein a in group - nothing prevents a jerk groupmate to bind you in some legaly bindable place where you kos if he is mad with you

thats why melee bind column and bidn confirmation box is good, and hard coding is BAD.

PS.
and for the GOD SAKE people - the stop treating "LIVE" like a freaken holy bible, where every word is divine and every statement is unquestionable!
Its not!

Originally Posted by ChaosSlayer

didn't you read my argument with Angelox?
Melee bind restriction SUCK and unfair.
And hard coding of this into main code is horible cause this kills server admin options of NOT having this stupid live-like feature.

As far as beein a in group - nothing prevents a jerk groupmate to bind you in some legaly bindable place where you kos if he is mad with you

thats why melee bind column and bidn confirmation box is good, and hard coding is BAD.

PS.
and for the GOD SAKE people - the stop treating "LIVE" like a freaken holy bible, where every word is divine and every statement is unquestionable!
Its not!

The whole point of PEQ is to recreate live, this is in live so it goes in.

The development team has always been good about giving options (rules anyone?) and there is a table option for this for people to edit now, if you dont want this on your server dont do it.

Just because you dont want it dont mean it shouldnt be in, this is an EVERQUEST Emulator and that is what this code does.

[ChaosSlayer]

Originally Posted by mattmeck

The whole point of PEQ is to recreate live, this is in live so it goes in.

The development team has always been good about giving options (rules anyone?) and there is a table option for this for people to edit now, if you dont want this on your server dont do it.

Just because you dont want it dont mean it shouldnt be in, this is an EVERQUEST Emulator and that is what this code does.

note that PEQ- is a DB, not a server code.
The code in question provided by TheLieka (who is a great coder, so this is no way bashing of him) will HARD CODE something which no custom Db can posibly 'fix'. Why hard code anything what can be made into an option by choice?

And as I said- I fully support "extra melee column' approach - server admins who will want to hinder melees, can hinder them. But the code I am bashing does not offer you any options.

Just because EqEmu is EQ emulator- doesnt mean it has to copy down all the shortcoming and weaknesses of the original.

[Angelox]

There's nothing to argue about here, Again, PEQ is the official database for the EqEmu . EqEmu is the Code and the Database, and they are trying to "emulate" live as best they can.
I'm here to support the people working to better the project (PEQ DB + EqEmu + Quests = Project EqEmu), So far they have done nothing but better the code and even keep some "custom" options available, for those who prefer it ( they didn't have to do that).
There's nothing to argue about, so better back off.

Originally Posted by ChaosSlayer

note that PEQ- is a DB, not a server code.
The code in question provided by TheLieka (who is a great coder, so this is no way bashing of him) will HARD CODE something which no custom Db can posibly 'fix'. Why hard code anything what can be made into an option by choice?

And as I said- I fully support "extra melee column' approach - server admins who will want to hinder melees, can hinder them. But the code I am bashing does not offer you any options.

Just because EqEmu is EQ emulator- doesnt mean it has to copy down all the shortcoming and weaknesses of the original.

Did you even read the part where Cavedude added the DB column? and he wants it NOT hard coded?