Post: #11

Just found a bug when summoning Blade Spirit and Vortex, they looks like not pet, but when created, they increase the slots on caster, but they don't decrease when die or whatever.

I made this small fix, hope you can find the way to fix this on source.

Post: #12

confirmed, sometimes the npc is not clearing the owner memory correctly on @Death

I commited this fix some minutes ago, maybe it's working fine now

Post: #13

Finally! Thanks.

Post: #14

Hey Coruja, another bug. It happens when you have .gm

Set for example: serv.chardef.c_horse_gray.followerslots 3
Then create the c_horse_gray and mount. You will gain only 1 follower.
If you shrink, it will consume 1 follower.

I know this only happens with gms but its a bug anyway.

If you create the gray horse and shrink, then unshrink, it will give you the same 1 follower.

I don't know why this is happening because I set the followerslots on serv.chardef.. or its wrong the way to read the follower slots.

If its not clear, I can try explain again

Post: #15

Isn't it based on characters instead of chardefs? Try that using .xfollowerslots 3

Post: #16

Not at all..

I created the horse after using the serv.chardef.c_horse_gray.followerslots 3
So, new horses have the followerslots = 3 BUT, if you mount (gm) you gain only 1 follower.

In other way, if you create the horse and SET followerslots = 3 (even with chardef setting = 3 or 1), it works fine.

Post: #17

strangely sphere cant read global properties (like followerslots) set directly on the chardef, it will always return 0 (and the EF_PetSlots engine will change it to 1 because it's the min value)

but if followerslots is set on npc (under @Create) instead on chardef it works fine

so I think the problem is not really on EF_PetSlots engine, but on this GetDefNum() function that read these properties. I dont know if this function intended to work like this (only return values from npcs instead chardef) so I left it as it is. But I think it must be changed to return chardef properties too

Post: #18

But you have the system working fine, right?

If yes, can you tell us how to fix, or the system will be useless and should be disabled because you 'left it as it is'.

Post: #19

it perfectly works if you set followerslots=3 on npc @Create instead [CHARDEF c_npc]

because followerslots property is read by a sphere internal function GetDefNum() exclusive to read char properties (like all these variables), and this function can read properties from chars (npc already created) but not from chardefs (which are just defs, not really the npc)

Post: #20

I'm gonna have to say, it's probably not the intended behavior and there is a way to make it check the chardef also.
I'll have a look at that right now.