Baldur's Gate : The Sword Coast Chronicles : NWN2 Persistent World

I think I reported it half a year ago, and the problem is still here.

It is impossible to attack someone's summons if the owner is unknown, invisible, hidden, etc.
I've run into another unattackable blackguard skeleton in east chontair ruins today.

Also, they occasionally persist after the player logs off.

Would be nice to finally have this fixed.

Speaking of which, why was summoning system changed to "posessed" creatures in the first place? New style summons count towards party limit and affect xp. It was not the case with old style creatures.

Have to agree with the OP. This problem should be put as a priority. ran into a person who was afk next to the vampire. such summons are kos except you cannot kos it when you have to find the owner of said summons and toggle them to hostile. I was lucky in that the owner was there visible for my character to toggle hostile in order to kill it. Please fix this ....Pretty please?

This all seems like pretty common sense, but here goes anyway:

First and foremost, you're never supposed to attack someone who is AFK. This protection extends to their summoned creatures. If someone is AFK with a KOS summon then just ignore their presence and RP as if they and the summon are not there until a time when they return from AFK (this is a general rule of thumb for anyone with an AFK tag unless you've been told specifically otherwise by the player).

If the summon is just there as a result of a bug (i.e. persisting when they log out) likewise just RP as if it isn't. If a player is using the mechanics of invisibility or HIPS to have an undead summon present without being attacked just to irritate people then this constitutes griefing and should be reported through appropriate channels.

This is just part of the way summons work, and we're not planning to overhaul the way summons work any time soon.

This seems pretty common sense to me but here it goes.

I agree with the rule to not attack a person who is afk. in fact I am pretty sure if you attack and kill a player who is afk then you in fact die and are fugued. I do not however think summons that is typically a kos should be included. If the player has to go afk and has time to put up an afk tab then they can either dismiss the summon or log until such time that they can be free to face the consequences of harboring the summon. This is a common curtisey I would extend to others so as to not ruin there player experience and any immersion they have. The rule for pvp on summons is this:

Summons can be attacked on sight, but normal PvP rules must be followed for the summoner (the player). The owner of the summons must also follow normal PvP rules in order to attack the killer of his or her summons. (Summons include any creature that can be summoned through a spell or an ability, and that is not a Familiar or an Animal Companion: These include angels, devils, elementals, and undead, among others.)

for my case I never attacked the player. I just eliminated the summon. I never attacked someone who was AFK. I hope any who read this do not take my rebuttal of this discussion as inflammatory. This is not my intent.

No offense taken. It's a fair enough point that the wording of the rule allows for the loophole. We'll make sure to get that updated.

tnx

Endelyon wrote: If the summon is just there as a result of a bug (i.e. persisting when they log out) likewise just RP as if it isn't. If a player is using the mechanics of invisibility or HIPS to have an undead summon present without being attacked just to irritate people then this constitutes griefing and should be reported through appropriate channels.

This is just part of the way summons work, and we're not planning to overhaul the way summons work any time soon.

It is not possible to report someone, when you don't know whose summon that is. It is also not possible to toggle hostile via a summon (I requested it earlier).

I think previous system where you could just rightclick/attack something that is KoS was good enough.

Also, per PvP rules only familiars and animal companions receive special protection from players and are treated as extension of their owner. Normal summons do not receive any protections from any player actions and are killable. That applies to all summon monster spells, planar binding and pretty much anything else.

They only need right-click attack menu added back to them, and that's pretty much it.

PvP aside, if it counts towards a party limit, I think we may want to adjust that. Some builds cannot help a party without using a summon. I do not want hard to level toons to get excluded from parties because they have to pick between them and their summon.

not sure what party limit you are talking about but summons and companions do count against xp gain

Eclypticon wrote:PvP aside, if it counts towards a party limit, I think we may want to adjust that. Some builds cannot help a party without using a summon. I do not want hard to level toons to get excluded from parties because they have to pick between them and their summon.

Having a summon reduces your combat xp. Previously - with previous summon system - having a summon did not reduce xp.

yes it did, idk if its taking more xp than what it use to but summons have always reduced xp

Blackman D wrote:yes it did, idk if its taking more xp than what it use to but summons have always reduced xp

No they didn't. I've played a thaumaturge. Having a summon out had zero effect on your experience.