2 suggestions

[mvazquez99]

Devs are doing an awesome job, but I think these are 2 easy coding changes that will help playability a lot:

1) Eliminate the "in combat" feature entirely. I understand the reason for not being able to join a scenario when you are really "in combat," but that is really for a more polished game and has little or no benefit in this Alpha. But the downside is big: My friends and I have to exit game all the time to join a scenario because we are falsely labeled as "in combat." We really don't need this restraint, and playing in scenarios will be much easier without it.

2) Eliminate cooldown on Book of Binding. Again, that cooldown makes sense for a polished game, but in this Alpha, we don't need it, and removing it would solve problems. We often get respawned in some "void" or back in Norsca, and cannot relocate because our Book of Binding is still cooling down. Let us Book of Bind as often as we want, and we can play this Alpha more freely with fewer frustrations.

Hope these suggestions are helpful (Gephank, Sazzlen, etc.)

[Tiggo]

devs cant change the client code (yet) and combat requirement is checked in the client max already said that.

[Azarael]

Is the stuck in combat issue still occurring as of today?

[mvazquez99]

yes, it is. Sometimes it flashes off, sometimes it never goes away and the only way to actually get into the scenario you were called for is to exit game, restart, and re-queue

[satekh]

I've had it today on my Choppa.

[Lindisfarne]

happens quite frequently, its frustrating. It seems to happen when u get certain buffs/debuffs stuck on your character.

[Morf]

i dont think it is smart to allow scens to be taken in combat or to remove the cooldown on book of binding reason being even as an alpha state there are many ppl who would use this as a way to avoid death, ive alrdy had ppl in the past book out during combat .

[Ley]

I don't agree with removing the in combat option ... more "options" to have people abusing it. What you and your friends have is a bug coming from buffs which i'm sure will get fixed.
With the second suggestion , i agree completely.

[Razid1987]

I don't understand how people can have such a big problem with the combat bug. Whenever I get it, I just start running in a random direction, and I get out of combat after about 5 seconds.

And again, I said this in another thread, and I was apparently labelled as "a troll" for saying so. I think it will be abused heavily, if you allow people to join SCs while in combat. Just imaging people getting ganked in ORvR. With a click of your mouse, you'll be all safe. Just join a SC and laugh at the people who just tried to kill you.

If something can be abused, it WILL be abused. Sad, but true...

[Azarael]

I'm not currently sure what causes the combat bug.

I know that multiple "in combats" sent to the client stack, for some infernal reason, so if the client ever receives two "in combat" packets, two "out of combat" packets will need to be sent to remove them.

However, this was already happening. A fix I tried a couple of days ago was to ensure the client is always taken out of combat when teleporting (as happens when you change zones), in case the combat state is linked to the map you're currently in. It seems that didn't work either.

Can try editing WSCT to explicitly message when going in combat and out of combat, with the map ID, to see if something's going wrong there.