Soul Binders arent working anymore?

[Aramid]

Originally Posted by hayward6

I don't know what to say here except that I am running a 0.7.0-840 server and all my translators that I have tested are working fine, hail and they talk to you and tell them "bind my soul" and they do just that... I don't have to be standing right on top of them like was suggested earlier, I just stand at a normal distance and do it.

Have you maybe screwed up your zone table to make all zones non bindable? I would test it with a caster class to see if you can cast bind affinity on yourself.

My TransLocators work fine too, it is only the SoulBinders that don't work. So I am clear, what my Transloactors do, is you hail them, They respond that they can send you to your starting city, you type in the city you want, you get Translocated and Bound to the Starting City you chose.
Just to be sure I didn't screw things up, I installed from scratch a new server and went one at a time from 0.7.0 to 0.7.0-821. As soon as I installed 0.7.0-821, my SOULBINDERS stopped working. You hail them , they answer as they should. You say bind my soul, and you get the correct response saying Binding your soul etc...
The next line says: You are not allowed to bind here!
The next line says: You feel yourself bind to the area.

TYpe in /char and shows your bound there. Now, zone or log out, do /char again and you will see your still bound in the zone previous to the one you the SoulBinder just bound you to.

Have high enough status to use #castspell, enter #castspell 2049 and you get the same responses.

Do #gm on and now you can bind to your hearts content by either using the SoulBinder or #castspell.

One last way to prove their not working. I made an account on PEQ, The Grand Creation. Their SOULBINDERS do the exact same thing as mine.

By Chance, are you doing this as a GM?

[John Adams]

Ahh, I was GM. And, there may in fact be something wrong with whatever detects your proximity to an object (on my system only, perhaps). Sometimes when I am fighting a mob, it says I am too far away, although I am well within the ring of influence. If I #summon, the mob moves a fraction of an inche and I can hit it again.

This is why I sorted out the NPCs that do not respond to Hail. I started testing that all over my world, and sure enough Hail started working once I summoned or stood atop the NPC. Also note, once the initial Hail worked, subsequent hails did appear to work ok even at a slight distance. It's all mind boggling, and I cannot debug since my logs are not very descriptive anymore (trying to figure that out, too).

I will un-GM and try the binders again sometime.

[hayward6]

Originally Posted by Aramid

My TransLocators work fine too, it is only the SoulBinders that don't work. So I am clear, what my Transloactors do, is you hail them, They respond that they can send you to your starting city, you type in the city you want, you get Translocated and Bound to the Starting City you chose.
Just to be sure I didn't screw things up, I installed from scratch a new server and went one at a time from 0.7.0 to 0.7.0-821. As soon as I installed 0.7.0-821, my SOULBINDERS stopped working. You hail them , they answer as they should. You say bind my soul, and you get the correct response saying Binding your soul etc...
The next line says: You are not allowed to bind here!
The next line says: You feel yourself bind to the area.

TYpe in /char and shows your bound there. Now, zone or log out, do /char again and you will see your still bound in the zone previous to the one you the SoulBinder just bound you to.

Have high enough status to use #castspell, enter #castspell 2049 and you get the same responses.

Do #gm on and now you can bind to your hearts content by either using the SoulBinder or #castspell.

One last way to prove their not working. I made an account on PEQ, The Grand Creation. Their SOULBINDERS do the exact same thing as mine.

By Chance, are you doing this as a GM?

sorry for the misunderstanding, but if you read what I said it's pretty clear I typed translocators by mistake... I was talking about my soulbinders and their ability to bind me. its working fine.

[Aramid]

Well, that is mind boggling if it's working on yours and your NOT a GM. If Grand Creation's doesn't work, I'd presume no ones did.

Also, being that I made NO Changes when reinstalling yesterday and they stopped working at 0.7.0-821.

[Aramid]

Tried a couple of other servers with the same results. After much thought though, it's not the SoulBinders that don't work, it's the Bind Affinity Spell that's not working.

Could it be that the code for determining if the zone was OK to bind in has changed?

[Aramid]

If your compiling 0.7.0-840, here's a fix for Bind Affinity & (SoulBinders).

In zonedb.cpp on line # 91, between maxclip, and time_type, type in walkspeed.

The line should look like this, this being the last 5 entries in that line:

"miniclip,maxclip,walkspeed,time_type,canbind"

recompile zone and Bind Affinity (SoulBinders too) work again. I'm sure the coders will correct it properly in the next release, but here is a fix for now should you choose to try it....

[John Adams]

Maybe I just don't understand the logic enough yet, but in 821, we were told to DROP walkspeed from npc_types. How is adding this to zonedb.cpp fixing a bind affinity problem?

FatherNitwit: Redid walkspeed code to be caclualted from runspeed (EverHood inspired)
.
.
ALTER TABLE `npc_types` DROP walkspeed;

[Aramid]

Yes, walkspeed has been removed from npc_types, but not from zonedb in the database.
While I'm only guessing, I think it put's the variable in a wrong position somewhere. The problem is not with the soulbinders or the bind affinity spell, but whether or not you can acutally bind in the zone you are in determined by the canbind variable.

By adding BACK in walkspeed to the query, it puts canbind back in the correct position. It was there before, but removed in 840.

I'm not a programmer by any means, just tend to get hooked on something and try to figure out how to make it work. This solution is what I found.

It corrected the problem for me in 840. As I said before, the coders will fix it in the proper place but for now, if you want to fix it... this will work.