Any thoughts on adding a justice.cfg and region.cfg entry called "NoCombat" with a 0/1 flag? This would be used to block combat attempts via the Attack Request by client and also (If doable), check to block "HARMFULL" labeled targetting cursors (see the .em flags for targeting cursors).
Considered adding this when doing the attack request stuff before, but had forgotten all about it. Let me know what you think.
NoCombat Justice Regions
Checks would have to be made for client requesting attack (for the target's position), same with the harmful targetting.
Now, for your question. Let's say Char A is outside the region, Char B is inside the region. Char A is in combat with Char B already. Char A runs into the region that is NoCombat marked. Utilizing the Enter Region Code, we check for opponent data, etc. We then remove oppnents from who enters, and from who their opponent was (if a player). Update clients for warmode, and send them on their merry way.
In theory so far, hehe.
Now, for your question. Let's say Char A is outside the region, Char B is inside the region. Char A is in combat with Char B already. Char A runs into the region that is NoCombat marked. Utilizing the Enter Region Code, we check for opponent data, etc. We then remove oppnents from who enters, and from who their opponent was (if a player). Update clients for warmode, and send them on their merry way.
In theory so far, hehe.
Aye, it is being based off client checks (and npcs do not have clients). So that is the desired path I am taking. So many have asked, attempted, etc, for this feature in POL. I've been doing the combat/attack reworks for a while now, and knew this is one that should be handled also.
I am still undecided on have it handle the Target() stuff though, because that is EASILY done via the scripts (just check region of course). I have been working on this in peices for a while as I had time, the implementation of reading it, accessing it during attack request, is done. Just have to finish the resetting stuff and all (it kicks players out of warmode and removes the Opponent from the aggressor when entering the region already in combat.)
I am still undecided on have it handle the Target() stuff though, because that is EASILY done via the scripts (just check region of course). I have been working on this in peices for a while as I had time, the implementation of reading it, accessing it during attack request, is done. Just have to finish the resetting stuff and all (it kicks players out of warmode and removes the Opponent from the aggressor when entering the region already in combat.)
You don't want to put a check for that into Target()?
Is the opponent moved via Enter Region Script being started and the script makes the move?
I hope so.. IMO if you kick both or 1 player from warmode and they're not able to attack one another then there's really no reason to boot the person out of that region. Or if not.. and the core moves the player, add an option for enabling or disabling booting out of the region. And possible(again if not called by script) an option XYZ to move the opponent to.
(New to 096 sorry.)
Is the opponent moved via Enter Region Script being started and the script makes the move?
I hope so.. IMO if you kick both or 1 player from warmode and they're not able to attack one another then there's really no reason to boot the person out of that region. Or if not.. and the core moves the player, add an option for enabling or disabling booting out of the region. And possible(again if not called by script) an option XYZ to move the opponent to.
(New to 096 sorry.)
