How can I adjudicate a character attempting a “shield crush” attack to pin a creature?
$begingroup$
In a recent game at my table, the cleric wanted to use his shield to pin a ghoul against the wall in order to stop it hitting people and make it easier to hit.
The player was thinking of it like a grapple or pin, but those mechanics didn't make sense -- the grapple only stops a creature, but doesn't really inhibit its ability to attack or make it easier to hit; and the pin is only available with a feat the player doesn't have.
But it was a good story beat that I didn't want to refuse, so in the moment I just mechanically called for a shove to knock the ghoul prone, and in the narrative he had the ghoul pinned against the wall with his shield instead of actually prone. It wasn't exactly what we wanted, but it was the closest thing I could come up with.
Is there a better way to mechanically represent crushing your enemy against a surface?
dnd-5e attack grapple shield
$endgroup$
add a comment |
$begingroup$
In a recent game at my table, the cleric wanted to use his shield to pin a ghoul against the wall in order to stop it hitting people and make it easier to hit.
The player was thinking of it like a grapple or pin, but those mechanics didn't make sense -- the grapple only stops a creature, but doesn't really inhibit its ability to attack or make it easier to hit; and the pin is only available with a feat the player doesn't have.
But it was a good story beat that I didn't want to refuse, so in the moment I just mechanically called for a shove to knock the ghoul prone, and in the narrative he had the ghoul pinned against the wall with his shield instead of actually prone. It wasn't exactly what we wanted, but it was the closest thing I could come up with.
Is there a better way to mechanically represent crushing your enemy against a surface?
dnd-5e attack grapple shield
$endgroup$
add a comment |
$begingroup$
In a recent game at my table, the cleric wanted to use his shield to pin a ghoul against the wall in order to stop it hitting people and make it easier to hit.
The player was thinking of it like a grapple or pin, but those mechanics didn't make sense -- the grapple only stops a creature, but doesn't really inhibit its ability to attack or make it easier to hit; and the pin is only available with a feat the player doesn't have.
But it was a good story beat that I didn't want to refuse, so in the moment I just mechanically called for a shove to knock the ghoul prone, and in the narrative he had the ghoul pinned against the wall with his shield instead of actually prone. It wasn't exactly what we wanted, but it was the closest thing I could come up with.
Is there a better way to mechanically represent crushing your enemy against a surface?
dnd-5e attack grapple shield
$endgroup$
In a recent game at my table, the cleric wanted to use his shield to pin a ghoul against the wall in order to stop it hitting people and make it easier to hit.
The player was thinking of it like a grapple or pin, but those mechanics didn't make sense -- the grapple only stops a creature, but doesn't really inhibit its ability to attack or make it easier to hit; and the pin is only available with a feat the player doesn't have.
But it was a good story beat that I didn't want to refuse, so in the moment I just mechanically called for a shove to knock the ghoul prone, and in the narrative he had the ghoul pinned against the wall with his shield instead of actually prone. It wasn't exactly what we wanted, but it was the closest thing I could come up with.
Is there a better way to mechanically represent crushing your enemy against a surface?
dnd-5e attack grapple shield
dnd-5e attack grapple shield
edited 1 hour ago
SevenSidedDie♦
207k31664940
207k31664940
asked 2 hours ago
Darth PseudonymDarth Pseudonym
13.4k33373
13.4k33373
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
$begingroup$
The condition the cleric was trying to describe was a combination between restrained and grappled:
Restrained:
- A restrained creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- Attack rolls against the creature have advantage,
and the creature’s attack rolls have disadvantage.
- The creature has
disadvantage on Dexterity saving throws.
Grappled:
- A grappled creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- The condition ends if the grappler is incapacitated (see the condition).
- The condition also ends if an effect removes the grappled creature from the reach of
the grappler or grappling effect, such as when a creature is hurled away by the
thunderwave spell.
Using official rules, you can take an action to grapple an opponent:
When you want to grab a creature or wrestle with it, you can use the
Attack action to make a special melee attack, a grapple. If you’re
able to make multiple attacks with the Attack action, this attack
replaces one of them. (...) Using at least one free hand, you try to seize the target
by making a grapple check instead of an attack roll: a Strength
(Athletics) check contested by the target’s Strength (Athletics) or
Dexterity (Acrobatics) check
Officially, shoving or grappling is probably what you want to if you are sticking to official rules.
If you were to homebrew something, I would suggest that the character could make a Athletics vs. Athletics/Acrobatics check to try to pin them against the wall, and then grant disadvantage on attack rolls for the ghoul, as it is difficult for it to attack when pinned, and then give attacks targeting it disadvantage, as you are blocking it. Its speed would also become zero.
This is semi-balanced, as it is like the grappled condition, with some advantages and some disadvantages.
$endgroup$
add a comment |
$begingroup$
Prone Was an excellent choice
You said that the cleric wanted "to stop [the ghoul from] hitting people and make it easier to hit." The prone condition has the following two applicable features:
- The creature has disadvantage on attack rolls.
- An attack roll against the creature has advantage
if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
It might seem like the "prone" condition doesn't apply because the ghoul is not splayed out on the ground. But keep in mind that "prone" does not always mean knocked down: it's a spectrum of conditions that make movement awkward and inconvenience a creature at short range (while making it harder to hit at a distance). As an example, consider the following rules on Flying Movement (PHB, p. 191):
If a flying creature is knocked prone, has its speed reduced to 0, or is otherwise deprived of the ability to move, the creature falls unless it has the ability to hover or it is being held aloft by magic, such as by the fly spell.
This text indicates that a flying creature can be "prone," which wouldn't make much sense if "prone" only had its traditional meaning.
Jeremy Crawford has described the various ways that the Shove action can be interpreted as something other than a "shove" (like "a throw, slamming into the other person, and so on.") Similarly, "prone" condition could cover a number of conditions that are analogous without actually requiring the creature to be lying down on the ground.
There are other options
If the Cleric was trying ensure the ghoul was not only inconvenienced but also trapped, he could have tried to both Shove the ghoul prone and Grapple it. For example, if he had the Shield Master Feat, he could use the Attack action to grapple the ghoul, and then a bonus action to Shove the ghoul into the wall with your permission that this would mechanically make it prone. This would stop the ghoul from simply using half its movement remove the prone condition.
But if the cleric didn't have a Feat or special ability that would permit him to render the ghoul restrained via an Action, I'd be hesitant to let him do so. You'd essentially be giving the cleric the ability to do with one attack what other characters can only do with several (or a Feat). If the cleric had only one attack available (as most classes of cleric do), I think that your decision to declare the ghoul to be "prone" was completely appropriate.
$endgroup$
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "122"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f140438%2fhow-can-i-adjudicate-a-character-attempting-a-shield-crush-attack-to-pin-a-cre%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
The condition the cleric was trying to describe was a combination between restrained and grappled:
Restrained:
- A restrained creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- Attack rolls against the creature have advantage,
and the creature’s attack rolls have disadvantage.
- The creature has
disadvantage on Dexterity saving throws.
Grappled:
- A grappled creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- The condition ends if the grappler is incapacitated (see the condition).
- The condition also ends if an effect removes the grappled creature from the reach of
the grappler or grappling effect, such as when a creature is hurled away by the
thunderwave spell.
Using official rules, you can take an action to grapple an opponent:
When you want to grab a creature or wrestle with it, you can use the
Attack action to make a special melee attack, a grapple. If you’re
able to make multiple attacks with the Attack action, this attack
replaces one of them. (...) Using at least one free hand, you try to seize the target
by making a grapple check instead of an attack roll: a Strength
(Athletics) check contested by the target’s Strength (Athletics) or
Dexterity (Acrobatics) check
Officially, shoving or grappling is probably what you want to if you are sticking to official rules.
If you were to homebrew something, I would suggest that the character could make a Athletics vs. Athletics/Acrobatics check to try to pin them against the wall, and then grant disadvantage on attack rolls for the ghoul, as it is difficult for it to attack when pinned, and then give attacks targeting it disadvantage, as you are blocking it. Its speed would also become zero.
This is semi-balanced, as it is like the grappled condition, with some advantages and some disadvantages.
$endgroup$
add a comment |
$begingroup$
The condition the cleric was trying to describe was a combination between restrained and grappled:
Restrained:
- A restrained creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- Attack rolls against the creature have advantage,
and the creature’s attack rolls have disadvantage.
- The creature has
disadvantage on Dexterity saving throws.
Grappled:
- A grappled creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- The condition ends if the grappler is incapacitated (see the condition).
- The condition also ends if an effect removes the grappled creature from the reach of
the grappler or grappling effect, such as when a creature is hurled away by the
thunderwave spell.
Using official rules, you can take an action to grapple an opponent:
When you want to grab a creature or wrestle with it, you can use the
Attack action to make a special melee attack, a grapple. If you’re
able to make multiple attacks with the Attack action, this attack
replaces one of them. (...) Using at least one free hand, you try to seize the target
by making a grapple check instead of an attack roll: a Strength
(Athletics) check contested by the target’s Strength (Athletics) or
Dexterity (Acrobatics) check
Officially, shoving or grappling is probably what you want to if you are sticking to official rules.
If you were to homebrew something, I would suggest that the character could make a Athletics vs. Athletics/Acrobatics check to try to pin them against the wall, and then grant disadvantage on attack rolls for the ghoul, as it is difficult for it to attack when pinned, and then give attacks targeting it disadvantage, as you are blocking it. Its speed would also become zero.
This is semi-balanced, as it is like the grappled condition, with some advantages and some disadvantages.
$endgroup$
add a comment |
$begingroup$
The condition the cleric was trying to describe was a combination between restrained and grappled:
Restrained:
- A restrained creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- Attack rolls against the creature have advantage,
and the creature’s attack rolls have disadvantage.
- The creature has
disadvantage on Dexterity saving throws.
Grappled:
- A grappled creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- The condition ends if the grappler is incapacitated (see the condition).
- The condition also ends if an effect removes the grappled creature from the reach of
the grappler or grappling effect, such as when a creature is hurled away by the
thunderwave spell.
Using official rules, you can take an action to grapple an opponent:
When you want to grab a creature or wrestle with it, you can use the
Attack action to make a special melee attack, a grapple. If you’re
able to make multiple attacks with the Attack action, this attack
replaces one of them. (...) Using at least one free hand, you try to seize the target
by making a grapple check instead of an attack roll: a Strength
(Athletics) check contested by the target’s Strength (Athletics) or
Dexterity (Acrobatics) check
Officially, shoving or grappling is probably what you want to if you are sticking to official rules.
If you were to homebrew something, I would suggest that the character could make a Athletics vs. Athletics/Acrobatics check to try to pin them against the wall, and then grant disadvantage on attack rolls for the ghoul, as it is difficult for it to attack when pinned, and then give attacks targeting it disadvantage, as you are blocking it. Its speed would also become zero.
This is semi-balanced, as it is like the grappled condition, with some advantages and some disadvantages.
$endgroup$
The condition the cleric was trying to describe was a combination between restrained and grappled:
Restrained:
- A restrained creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- Attack rolls against the creature have advantage,
and the creature’s attack rolls have disadvantage.
- The creature has
disadvantage on Dexterity saving throws.
Grappled:
- A grappled creature’s speed becomes 0, and it can’t benefit from any
bonus to its speed.
- The condition ends if the grappler is incapacitated (see the condition).
- The condition also ends if an effect removes the grappled creature from the reach of
the grappler or grappling effect, such as when a creature is hurled away by the
thunderwave spell.
Using official rules, you can take an action to grapple an opponent:
When you want to grab a creature or wrestle with it, you can use the
Attack action to make a special melee attack, a grapple. If you’re
able to make multiple attacks with the Attack action, this attack
replaces one of them. (...) Using at least one free hand, you try to seize the target
by making a grapple check instead of an attack roll: a Strength
(Athletics) check contested by the target’s Strength (Athletics) or
Dexterity (Acrobatics) check
Officially, shoving or grappling is probably what you want to if you are sticking to official rules.
If you were to homebrew something, I would suggest that the character could make a Athletics vs. Athletics/Acrobatics check to try to pin them against the wall, and then grant disadvantage on attack rolls for the ghoul, as it is difficult for it to attack when pinned, and then give attacks targeting it disadvantage, as you are blocking it. Its speed would also become zero.
This is semi-balanced, as it is like the grappled condition, with some advantages and some disadvantages.
edited 59 mins ago
V2Blast
21.8k365139
21.8k365139
answered 1 hour ago
JustinJustin
1,1961422
1,1961422
add a comment |
add a comment |
$begingroup$
Prone Was an excellent choice
You said that the cleric wanted "to stop [the ghoul from] hitting people and make it easier to hit." The prone condition has the following two applicable features:
- The creature has disadvantage on attack rolls.
- An attack roll against the creature has advantage
if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
It might seem like the "prone" condition doesn't apply because the ghoul is not splayed out on the ground. But keep in mind that "prone" does not always mean knocked down: it's a spectrum of conditions that make movement awkward and inconvenience a creature at short range (while making it harder to hit at a distance). As an example, consider the following rules on Flying Movement (PHB, p. 191):
If a flying creature is knocked prone, has its speed reduced to 0, or is otherwise deprived of the ability to move, the creature falls unless it has the ability to hover or it is being held aloft by magic, such as by the fly spell.
This text indicates that a flying creature can be "prone," which wouldn't make much sense if "prone" only had its traditional meaning.
Jeremy Crawford has described the various ways that the Shove action can be interpreted as something other than a "shove" (like "a throw, slamming into the other person, and so on.") Similarly, "prone" condition could cover a number of conditions that are analogous without actually requiring the creature to be lying down on the ground.
There are other options
If the Cleric was trying ensure the ghoul was not only inconvenienced but also trapped, he could have tried to both Shove the ghoul prone and Grapple it. For example, if he had the Shield Master Feat, he could use the Attack action to grapple the ghoul, and then a bonus action to Shove the ghoul into the wall with your permission that this would mechanically make it prone. This would stop the ghoul from simply using half its movement remove the prone condition.
But if the cleric didn't have a Feat or special ability that would permit him to render the ghoul restrained via an Action, I'd be hesitant to let him do so. You'd essentially be giving the cleric the ability to do with one attack what other characters can only do with several (or a Feat). If the cleric had only one attack available (as most classes of cleric do), I think that your decision to declare the ghoul to be "prone" was completely appropriate.
$endgroup$
add a comment |
$begingroup$
Prone Was an excellent choice
You said that the cleric wanted "to stop [the ghoul from] hitting people and make it easier to hit." The prone condition has the following two applicable features:
- The creature has disadvantage on attack rolls.
- An attack roll against the creature has advantage
if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
It might seem like the "prone" condition doesn't apply because the ghoul is not splayed out on the ground. But keep in mind that "prone" does not always mean knocked down: it's a spectrum of conditions that make movement awkward and inconvenience a creature at short range (while making it harder to hit at a distance). As an example, consider the following rules on Flying Movement (PHB, p. 191):
If a flying creature is knocked prone, has its speed reduced to 0, or is otherwise deprived of the ability to move, the creature falls unless it has the ability to hover or it is being held aloft by magic, such as by the fly spell.
This text indicates that a flying creature can be "prone," which wouldn't make much sense if "prone" only had its traditional meaning.
Jeremy Crawford has described the various ways that the Shove action can be interpreted as something other than a "shove" (like "a throw, slamming into the other person, and so on.") Similarly, "prone" condition could cover a number of conditions that are analogous without actually requiring the creature to be lying down on the ground.
There are other options
If the Cleric was trying ensure the ghoul was not only inconvenienced but also trapped, he could have tried to both Shove the ghoul prone and Grapple it. For example, if he had the Shield Master Feat, he could use the Attack action to grapple the ghoul, and then a bonus action to Shove the ghoul into the wall with your permission that this would mechanically make it prone. This would stop the ghoul from simply using half its movement remove the prone condition.
But if the cleric didn't have a Feat or special ability that would permit him to render the ghoul restrained via an Action, I'd be hesitant to let him do so. You'd essentially be giving the cleric the ability to do with one attack what other characters can only do with several (or a Feat). If the cleric had only one attack available (as most classes of cleric do), I think that your decision to declare the ghoul to be "prone" was completely appropriate.
$endgroup$
add a comment |
$begingroup$
Prone Was an excellent choice
You said that the cleric wanted "to stop [the ghoul from] hitting people and make it easier to hit." The prone condition has the following two applicable features:
- The creature has disadvantage on attack rolls.
- An attack roll against the creature has advantage
if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
It might seem like the "prone" condition doesn't apply because the ghoul is not splayed out on the ground. But keep in mind that "prone" does not always mean knocked down: it's a spectrum of conditions that make movement awkward and inconvenience a creature at short range (while making it harder to hit at a distance). As an example, consider the following rules on Flying Movement (PHB, p. 191):
If a flying creature is knocked prone, has its speed reduced to 0, or is otherwise deprived of the ability to move, the creature falls unless it has the ability to hover or it is being held aloft by magic, such as by the fly spell.
This text indicates that a flying creature can be "prone," which wouldn't make much sense if "prone" only had its traditional meaning.
Jeremy Crawford has described the various ways that the Shove action can be interpreted as something other than a "shove" (like "a throw, slamming into the other person, and so on.") Similarly, "prone" condition could cover a number of conditions that are analogous without actually requiring the creature to be lying down on the ground.
There are other options
If the Cleric was trying ensure the ghoul was not only inconvenienced but also trapped, he could have tried to both Shove the ghoul prone and Grapple it. For example, if he had the Shield Master Feat, he could use the Attack action to grapple the ghoul, and then a bonus action to Shove the ghoul into the wall with your permission that this would mechanically make it prone. This would stop the ghoul from simply using half its movement remove the prone condition.
But if the cleric didn't have a Feat or special ability that would permit him to render the ghoul restrained via an Action, I'd be hesitant to let him do so. You'd essentially be giving the cleric the ability to do with one attack what other characters can only do with several (or a Feat). If the cleric had only one attack available (as most classes of cleric do), I think that your decision to declare the ghoul to be "prone" was completely appropriate.
$endgroup$
Prone Was an excellent choice
You said that the cleric wanted "to stop [the ghoul from] hitting people and make it easier to hit." The prone condition has the following two applicable features:
- The creature has disadvantage on attack rolls.
- An attack roll against the creature has advantage
if the attacker is within 5 feet of the creature. Otherwise, the attack roll has disadvantage.
It might seem like the "prone" condition doesn't apply because the ghoul is not splayed out on the ground. But keep in mind that "prone" does not always mean knocked down: it's a spectrum of conditions that make movement awkward and inconvenience a creature at short range (while making it harder to hit at a distance). As an example, consider the following rules on Flying Movement (PHB, p. 191):
If a flying creature is knocked prone, has its speed reduced to 0, or is otherwise deprived of the ability to move, the creature falls unless it has the ability to hover or it is being held aloft by magic, such as by the fly spell.
This text indicates that a flying creature can be "prone," which wouldn't make much sense if "prone" only had its traditional meaning.
Jeremy Crawford has described the various ways that the Shove action can be interpreted as something other than a "shove" (like "a throw, slamming into the other person, and so on.") Similarly, "prone" condition could cover a number of conditions that are analogous without actually requiring the creature to be lying down on the ground.
There are other options
If the Cleric was trying ensure the ghoul was not only inconvenienced but also trapped, he could have tried to both Shove the ghoul prone and Grapple it. For example, if he had the Shield Master Feat, he could use the Attack action to grapple the ghoul, and then a bonus action to Shove the ghoul into the wall with your permission that this would mechanically make it prone. This would stop the ghoul from simply using half its movement remove the prone condition.
But if the cleric didn't have a Feat or special ability that would permit him to render the ghoul restrained via an Action, I'd be hesitant to let him do so. You'd essentially be giving the cleric the ability to do with one attack what other characters can only do with several (or a Feat). If the cleric had only one attack available (as most classes of cleric do), I think that your decision to declare the ghoul to be "prone" was completely appropriate.
edited 16 mins ago
answered 23 mins ago
GandalfmeansmeGandalfmeansme
20.3k376127
20.3k376127
add a comment |
add a comment |
Thanks for contributing an answer to Role-playing Games Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f140438%2fhow-can-i-adjudicate-a-character-attempting-a-shield-crush-attack-to-pin-a-cre%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown