archangel979

Snapping a neck just like that takes practice and knowhow. Anyone having that, also can easily make someone unconscious by knocking them on the head of taking away their oxygen. And it is not precise science, and our characters are heroes. The point of my comment was that if you can snap a neck with 100% success with that NPC not being able to get away she will not get away from being knocked out.

That was enough, lock with spells and unFPS cover system made the game a bad shooter. It was something in the middle and it was bad version of both worlds

I think he just means the game does not have cinematic storytelling like Mass Effect or Skyrim (at least the start of Skyrim). The story and way it is presented is not much different than Fallout 1 and 2 and I don't care about it not being cinematic. I prefer it done this way. Old school style.

That is just another reason to not let her go back in this condition alone. Your characters might be confident that they can deal with both and come out on top as victors. It has nothing to do with being ruthless. And you put safety of everyone in front, lord and girl, by doing it this way. It does not mean you put Lord before the girl, you are saving the girl as much here by not letting her leave. What if she murders him and remembers it, she will be mentally damaged for life. What she gone through in Animancer experiments is already bad. A good person will not let the victim come close to her abuser, especially after a group of crazies did magical experiments on her. A Chaotic good would just take her away and a lawful good would look to bring down the lord through laws. None would look to murder the Lord unless in self defense or to defend life of other innocents. Other outcomes are class locked, while the ones available to all are lacking.

Another solution would be to copy how D&D 4e did it with some classes being able to mark enemies. Then those enemies could choose to ignore that mark but would suffer serious penalties when doing so like attack penalty or damage over time. Movement would still be free and a choice of players (and AI) to deal with the one doing marking or move around because of needing to do other stuff.

I didn't say it is the best 3PS, I said it has the best game mechanics of any 3PS. I'll make it easy for you - name a 3PS where you have as many (vastly different) abilities to chose from as in ME3. Hint: When you start reaching the 80 mark, you're getting close. And if you can manage that, we can start talking about character stats, unique enemy types, weapons, weapon mods 1, weapon mods 2, ammo types, armor mods, gear, combos, sync kills...you get the idea. And of course you don't have to like all this stuff but it is there and it objectively makes ME3 one of the most versatile 3P combat games around. The thing is, it is not even a shooter. Because the game basically does everything for you. You lock targets and fire something that goes into direction of enemy. That is not a shooter, that some something else. And cover system is standard of games like Assassin Creed, not real shooters. ME2 and ME3 plays more like real time Xcom (new one) then any shooter. Or that Xcom "shooter" that got terrible reviews by having almost same system like Mass Effect.

I presented my solutions. It keeps a penalty for those disengaging forcefully but also lets everyone leave if they use more careful options.

You don't know that at the moment. You know what they said, but you don't know how they will do it, when exactly and what they programmed the girl to do in case their and her plans are discovered. As far as you know you just sent her to stick a knife in his throat immediately upon arrival. Getting killed by his niece is already a much bigger thing than just being killed by a random person. You are still using here your knowledge of the whole quest to present your point. As for knocking her out in front of them causing them to fight you, that is the point. Just like killing her causes them to fight you, but you also try to save her life. And you are right that it is risky as she might die during spellcasting battles. And as a result I change my suggestion into: If you knock her out at end of battle you find her dead with a description similar to what you said. It is good that quests have options where player plans don't always end up as expected. But, add another conversation option for high enough Stealth skill where you let the girl go but send one party member unnoticed after her to knock her out. Then if you decide to fight these guys you got one guy less for the fight (maybe the door closes behind you and that person is on the other side of the door). And also keep the current option of just letting her go as normal for the people that want to roleplay those that want the girl to finish her mission or those don't want her but are less wise about the risks. As for what good people would do here, that is a conversation for another topic/post.

Huh? You mean in PoE? Enemy's movement speed doesn't prevent them from re-engaging you now.And who's allies, enemies or yours? yes in poe. If you are faster once you exit they cannot engage until you stop if they keep following. Just like in my example.And of course I mean your allies. You disengage and move to back lines and your allies engage those that follow just like in my example based on dnd AoO. both systems work same once you disengage, difference is that my suggestion lets you disengage without special class abilities in exchange for only being able to move and not attack right after which prevents ranged characters from abusing this to kite.

It may not be needed to beat the game with a single or multi class PC and single or multi class companions but if you choose to dual class instead especially if you have multiple dual class characters in your party it can be very problematic to simply play through normally vs using something like the pirate cave to "quick level" your new class to get your old skills back ( also depending on a lot of outside factors like size and makeup of group, general alignment of group, companion availability, and what point in the game you are at when it comes time to dual class.) The same thing can occur in BG2 as well altho since you start at level 8ish it is less problematic as you have a much sturdier PC or companion to keep alive while getting their old skills back. Why use golem cave when you can easily go kill basilisks for lots of XP. Even with no magical protections, you can use that Ghoul to mostly kill them for you. Is that also grinding?

Soo what stops the enemy from just re-engaging you when you are recovering? What prevents them now? Movespeed and allies. If you are alone and fighting enemies you don't get anything from retreating anyways unless you are much, much faster.

Player character know is that point of conversation that Lord has abused the girl and lied about who girl is and that he is quite disgusting person overall, so I would question more why player character would care if she immediately will kill/poison/whatever the Lord, especially when player still knows that they have time to collect reward from the lord? Some player will not care, others will want to roleplay a good guy that does not allow murder. And players at that point don't know what happens if you let the girl go. You know because you played that part already. I came into this topic as a person that didn't know what happens later and the person I watched on Youtube didn't as well. We both assumed letting the girl go would kill the Lord or something else terrible will happen. The Youtuber decided to kill the girl to prevent that. I noticed that if players can automatically succeed killing the girl they should automatically succeed in knocking her out as that is what a good person would do to avoid OR RISK any more unneeded deaths.

I care more about single player then MP as I find 1v1 games too stressful and XvX in Starcraft is not balanced.

In DnD 3.5e if you wanted to move away from enemy without suffering AoO but didn't have any special way (spells, feats, tumble or some magical ability) there were two options: 1. just move without doing anything. This worked against one enemy, but additional ones that surrounded you would still get their AoO. - this can be implemented in PoE by turning on a universal ability for all classes that lets you move away from one engagement but your recovery turns on for few seconds. You will be able to break engagement from one enemy but you will not be able to do much for the duration of the recovery. 2. go into full defense mode and move out of area. This would cause everyone around to get AoO but their chance of actually hitting you would be reduced considerably (about 20%). - this can be implemented in PoE similar to #1 but it gives a noticeable Deflection boost while also putting your character into recovery for few seconds. You can more safely move from as many engagements as you want but you will also not be able to do much for the duration of recovery. This option would also reduce your move speed while recovery is in effect.

What you quoted sounds just like I said, like you need to stop her from getting to him. Maybe it is because English is not my first language or because games so far have taught us that letting the girl go would result in death before we can stop it. Why would a player's character risk it even? You don't even know exactly what are her plans, as far as we know she will poison him immediately with slow acting poison. The game presents you will two options, it is normal to assume that the one that does not kill her will let her accomplish her task. Put yourself in the shoes of your character there. That is how I did it, as a GM of countless groups for about 17 years I just imagined what many of my players would do or did in similar situations with their characters and they sure as hell would not let her go unless they wanted her to kill the Lord. And then the game presents you with automatic death of girl without a chance of failure. If my character can do that, he can also automatically knock her out as that is a logical course of action if you don't want to kill her or let her go to do who knows what before you get back there.

Although in my mind I agree with you, I love Starcraft universe and characters so much so I still play and buy Starcraft 2 content. I even took Star Wars Saga Edition PnP rules and converted them so I can play Starcraft PnP :D

I agree with Sensuki. I wanted to play an RPG and I got a badly done shooter with way too much boring combat. Only thing good was production values and decent full voice overs with your companions. But gameplay itself was so bad, and I play games for gameplay first. This was a problem with Fallout 3 and FNV, trying to be more FPS but not enough and ending up a bad FPS and a bad RPG. I would rather they go full Counter Strike or Crysis and just add some rpg elements and conversations. Actually later Crysis almost had as much character customization as ME2 and ME3 had, it just lacked a bigger story, companions and RPG story and more freedom. If you are actually going to do a shooter RPG, make sure the shooter part is as good as it can be.

I was just about to ask this lol

WL2 is also 21+ GB. I guess Unity games are big.

Also it says it has full voice over for all languages :D

Actually I would prefer nwn2 system over what we have now. In nwn2 it could miss like any attack, it wasn't instant critical, any class could use tumble and there were feats that gave you bonus AC vs these attacks.

In that case there is three option, let girl go back (and when you go back to lord you will find him alive and well and girl next to him and you can decide do you tell about ritual to lord or not and so on) nap girl's neck and kill cultist. Option three is not directly shown to player, but if you kill cultists without killing girl it is possible to reverse ritual (all options to this path aren't open in beta). Knocking girl down and letting her go to lord are effectively same as cultist are already cast their spell on her and she don't kill lord before you get to tell him/not tell him about ritual. Although letting player knock her down and carry her to lord would add flavor option for those players who want be bit more brutal in how they handle situations, but consequence wise there would be next to nothing difference to current options. No, you misunderstand. The way the conversation goes the player is led to believe if you let the girl go she will get there and kill the Lord. You don't know if you can get back in time to do anything about it. At that point in time, knocking her out is only normal response that does not involve making a hard choice (let girl kill lord or kill girl).As I was watching that conversation with the Let's Play person we both got the same impression. The youtuber chose to kill the girl to prevent her from killing the Lord. The options are presented in a bad way to players, that it why I am asking for the knock out option to be able to resolve this situation without killing the girl or the lord.

It can be beaten with a single lvl something character just by abusing some features of the last map :D

The was it is presented is #1 Kill the girl by automatically snapping her neck or #2 Let her go back and as far as you know she will probably kill the lord by the time you get there (actually that would be the expected outcome of letting her go in case you want her to kill him). #3 option for all classes is sorely lacking here. If players can automatically snap her neck, they can also automatically knock her out and then taking her back to Lord could be counted as if you talked to Lord about it after letting her go (like you described).

I just said I don't have beta access. Unless you want me to pirate the beta (not sure if it is even possible) I cannot do that. And I don't plan to watch all lets plays and read all conversations to check all quests. It is easy to check out combat or mechanics through streams or lets plays but for quests I would need to be able to play the game and try all options to find strange options (or lack of those).