I tried the suggestion that Derision made, but that didn't work. In fact, it stopped the limiting from happening at all as far as I could tell.
I am sure we can still come up with something. If I could only find the code that keeps you from logging in the same character more than once, I think it could be applied to this code to make a good solution.
I don't know if anything changed with the situation with aza77 (didn't know them), but here are a few excerpts from the changelog that seem to show that aza77 doesn't mind sharing code:
Quote:
==10/28/2006
aza77: Fixed SendAppearancePacket
aza77: Fixed a PvP bug that caused the zone to crash on death
==07/16/2006
aza77: Fixed the lift issue + keyitems at doors
aza77: Fixed + modified traps and added a new type of trap
==07/13/2006
aza77: Added in game guild creation variables.GuildCreation + commands #guildcreate #guildapprove #guildlist
==07/12/2006
aza77: Added triggered only doors.
==07/05/2006
aza77: Added variables.Rules + commands #rules #acceptrules
==06/28/2006
aza77: Changed hp_regen + mana_regen such that negative values indicate no regen
==06/27/2006
aza77: Added quest::setnextinchpevent + $inchpevent
aza77: Added quest::sethp
==06/25/2006
aza77: Fixed PVP appearance issues
==06/15/2006
aza: Added MySQL5 support (FOR CUSTOM COMPILE ONLY)
==05/31/2006
FatherNitwit: (aza) Added quest::unscribespells
==05/06/2006
FatherNitwit: (aza) Enabled newer froglok classes.
FatherNitwit: (aza) Enabled several berserker combat skills.
==04/13/2006
FatherNitwit: Adding the incstats canges from aza on the forums.
|
And, here is the last post I see from aza77, and it just happens to show more sharing:
http://eqemulator.net/forums/showthread.php?t=21609
So, I would be pretty surprised if they were upset about their code being posted. From what I can tell, they would have wanted it shared. I do believe that the author reserves all rights to decide to share or not. Since you are unable to reach them, it is up to you whether to share or not. My guess is that the code wasn't meant to be secret, but was just something that they never got around to sharing. If they were a secretive person, then I would definitely say not to share.
Either way, we will get the account limiting issue resolved in the best way possible. It isn't a big deal. If the code that aza77 wrote just blocks them from logging in another character on the same account, then that is what the current code here already does, so it wouldn't be needed anyway. The only thing we need is a way to make it boot the in game character on the same account instead of blocking the one logging in. If it doesn't do that, there is no use for the code anyway.
Threaded Mode
