Darkness Player

[Hyun Orth]

Ihave an idea for a character who would often use the Darkness spell in combat - with either a Warlock's Devil's Sight or a Sorcerer's Shadow Magic to remain unaffected. That way the character would get advantage on attack rolls against nearly all enemies (except those that have truesight or blindsight) while the enemies would have disadvantage to hit the character.

My concern is how much this would affect the other players, since most of them won't have the ability to see in magical darkness. Can someone share their practical experience from a campaign where one of the players used this? Was it bad, or did the party make it work?

It depends a lot on how closely your game sticks to RAW. Under RAW, everyone who can't see will attack and defend with disadvantage. If neither the attacker nor the defender can see, the disadvantage for attacking blind and the advantage for attacking someone who can't see you cancel out and the darkness doesn't actually do anything to most attack rolls. Unless a character is using the Hide action, darkness doesn't actually conceal their location, so there is no need to guess where enemies are or attack squares blindly (sometimes DMs will house rule this). So combat will mostly play out as usual despite no one being able to see.

One side effect is that any extra sources of advantage/disadvantage (like ranged attack in melee) get blanked because multiple sources of dis/advantage don't stack. Another effect is that attacks of opportunity no longer happen, because they require vision.

Darkness does have a big impact on spellcasting. A lot of spells require vision to be castable (notably Counterspell). This can be useful for shielding the party from enemy spellcasters (although note Fireball doesn't require vision, and can be devastating to a party huddled inside Darkness). Your party's other spellcasters may want an angle where they can step outside the Darkness to cast their spells, so keep that in mind when you position the Darkness.

Conclusion: RAW, the main impact darkness will have on your party is interfering with spellcasting (which can be tactical, or annoying) and blanking advantage (like Barbarian's Reckless Attack). If your DM is using custom rules for unseen characters, such as automatically Hiding them, then Darkness is much more likely to be an annoyance.

Unlike Dale M, my party doesn't use a magical light source. Rather, they have three of six members with racial darkvision, and they use the Darkvision spell on two of the humans (the third human is the warlock with Devil's Sight).

The principle reason is because it is just too costly. Even at 10th level the warlock still has a meagre two spell slots, and using half of them on a darkness spell is seldom worth it even in the most opportune of conditions.

Early on the warlock was pact of the blade, but quickly realized that he did not want to hang in melee with the party tanks and take as much damage as they were. (The tanks are a wolf totem barbarian who is a damage sponge / advantage generator and a champion fighter with maxed Con, magic plate, and AC20).

Since the warlock switched to pact of the tome, generating advantage for himself in melee is seldom desired, and generating effective disadvantage for others to hit him is easier done by staying at range, using cover, and being prone (none of which cost scarce spell slots).

Even when the warlock was experimenting with being a melee fighter, though, constrained battlefields often meant that his darkness interfered with the others' sights. Since there were more of them than him, and since the dedicated melee characters hit harder than he did, that ended up being a net loss for the party.

The darkness is occasionally useful, but it is situational.

One time the party found themselves in a close range missile ambush, with the enemy behind hidden and fortified positions. In this case the warlock put up darkness, and the other party members entered it to protect themselves until they could formulate a response.

Other times the warlock has used darkness is when he is forced to be solo. He is not the party scout (that is the Stealth-maxed lore bard), but when he finds himself on his own, he can profitably use darkness to both avoid detection and to protect himself if detected.

Sometimes he is charged with holding the flank or rear of the party when they need to restrict access to the battlefield to prevent reinforcements from arriving. Since he will be fighting alone, that is a great time for him to whip out the darkness.

I gave one of my players a wondrous item with the following traits, which I thought were a really neat twist on Darkness (Please excuse some of the weirdness in rules text caused by us playing on Roll20 with specific settings). The player kept the ability secret and used it in a critical moment as a big reveal:

Shadow Magic. While attuned to this item, you know the spell Darkness. It counts as a spell of your class, but doesn't count against the number of spells you know. While wearing this armor, when a creature you can see hits you with an attack, after you see both attack rolls, you can use your reaction to cast Darkness. This may cause the attack to miss.

However, to my surprise, when the player activated this effect and cast Darkness, it caused a lot of havoc on the battlefield and annoyed the other players. One player could no longer see the targets they wanted to see, and had to learn the rules about magical darkness in order to cope with the new obstacle. Another player no longer had intelligence about what the enemies were doing, which was a serious obstacle to deciding on a course of action during their turn. Note that it is totally normal and expected for an adversary to create these kinds of obstacles, but it creates in-group friction when an ally creates them.

So, I would recommend that if a party member plans to use the Darkness spell, the party (in-character, probably) practice some tactics involving it, so that when the spell is used, it doesn't feel like one player is having fun by creating obstacles for the other players. That's the DM's job.

When I first started, I was going out of the AD&D, and there was a passage I'm going to have to dig up to the tune of "if you cast silence and invisible on your whole party, they're going to trip over each other a lot". Your own party can get in your way. The long and short of it, is that both the attacker and the person between the attacker and their target need to coordinate. While 5e lacks a "shooting into combat" caveat that I can find, I would rule that characters who don't know whose way to get into or out of are essentially cover without that coordination. The attacks (for functionally blind characters) are also coming in at a disadvantage, so that +2 for cover can go quite a long way.

COVER:A target with half cover has a +2 bonus to AC and Dexterity Saving Throws. A target has half cover if an obstacle blocks at least half of its body. The obstacle might be a low wall, a large piece of furniture, a narrow tree trunk, or a creature, whether that creature is an enemy or a friend.

One of my first forays into fighting in darkness came because another player had marbles that emanated Darkness. Our plan to siege some fortified enemies involved throwing these marbles in front of the doors and (ground floor) windows and rushing the building under cover. The DM made us to save against spell not to run into a wall, causing a cool 1d6 damage and ending our respective turn on any failures. Once we came through the other side everything was cool again. We apologized to the party members behind us who were forced into the darkness to avoid crossbows from the upper level.

Another time, in 3.5e, I was DMing. I added melee attacks to the "shooting into melee" rule. It got a little complex because I was using Listen checks to tell if anyone was close enough, and not saying friend or foe until they started coordinating. They could attack wildly and I would roll to see who got hit, or they would attack a specific direction and that's who got the attack (friend or foe). Back then we had a very "8bit JPRG" mindset to battle, so being required to think about more than "Does X hit?" was pretty big at the time.

One option is to create a class that extends Light class and create a sphere componenet that allows the player to overlap collide with it. Then you would check for EnterOverlap events, make sure the overlapping actor is the player, then tell the player that he is in the light (however you want do that, make a function in the player class or something of the like). Then on the ExitOverlap event, tell the player he is no longer in the light.

So you can extend the Light class that you want to add a sphere component to it and then add the overlap event handling functions in there. Or, you can do this very simply in Blueprint alone. Seeing as this is a trivial task, the Blueprint overhead would be negligible. Also, you can make one blueprint and just plop a bunch of lights wherever you want and tweak little settings as you see fit.

I want to make it so that when a scene begins, everything is shrouded by darkness. However, there is a small light surrounding the player and the torches so that the player can see something along the way. How do I do that?

Example would be the night mode in Ghost House and Underwater themes in Super Mario Maker 2. The stage is completely dark in this mode, but the player and some other objects like the Starman, fire, fireballs, Boos, and light blocks are either unaffected by the darkness or surrounded by small light.

But turns out in events sheet there is action that changes opacity so you need to set it to 255 (making above step useless so you either change it here or change in above step and delete this action)

image1350148 17.2 KB

When you create a light object, the engine automatically creates another layer called the Lighting layer, which is where all of the light functions work. To make everything dark, you have to go to the Lighting properties in the Lighting layer and set the ambient color to black (0; 0; 0). Afterwards, you can do anything you want. For example, I made it so that when the stage begins, the player character has a little bit of light surrounding them so that the player always knows where their character is.

3a8082e126