Descendants of Darkness Wiki - User contributions [en]

In-World Devices

2026-06-12T20:22:48Z

Ninja: /* Quick Reference */

=Resting Nexus=
[[File:RestingNexus400x400.png|thumb|Resting Nexus|border|left]]
The Resting Nexus offers protection from blood loss for a specified duration, currently set at 14 days. You have the choice to age during this period or remain unchanged. Opting for 14 days without aging incurs a fee of 250 Lindens, while choosing aging costs 500 Lindens. Aging occurs gradually, with one night passing for every two days, ensuring a balanced progression. This duration was chosen to maintain fairness, preventing abuse by creating alternate accounts solely for aging. The Resting Nexus provides security during periods of absence from the computer, yet players remain vulnerable to attacks.

=Blood Well=
[[File:Blood Well 2026-01-13.png|left|thumb|Blood Well]]
The Blood Well has multiple uses. You can deposit blood, withdraw blood, or transfer blood to another player. To use the Blood Well, it costs 5 Lindens to deposit, withdraw, or transfer.

If you deposit blood, it will add the amount of blood you deposited to the total amount you have deposited. It will also deduct that amount of blood from you in-world.

When you withdraw blood, the amount you withdraw will be added to your total blood in-world.

For transferring blood to another player, you will need to enter the key of the other player. Once you've clicked on the device to pay, the other player can access the blood by withdrawing it from the Blood Well.

=Species Change=
[[File:SpeciesChange400x400.png|left|thumb|Species Change Device]]

The Species Change Device allows you to change your species. If you're a vampire, you can switch to a lycan or witch, and vice versa. The cost to use the device is 2,500 Lindens. This price is set to discourage people from abusing the device and constantly changing species.

=Reawakening Shrine=
[[File:ReawakeningShrine400x400.png|left|thumb|Reawakening Shrine]]
The Reawakening Shrine is an animated device that revives a player. To operate the Reawakening Shrine, two players are required. The player who needs to be revived sits on the device first, followed by the player who will perform the revival. Two essences will be taken from the reviving player. The revived player will be restored with 1.000 liters of blood.

= Elixirs =

<gallery>
File:RevivalElixir400x400.png|Revival Elixir (Red)
File:BreathOfVitality400x400.png|Breath of Vitality Elixir (Teal)
</gallery>

Elixirs are consumable items used to restore or revive your avatar in ''Descendants of Darkness''. These interact with the '''human feeding system''', not other players.

== Types of Elixirs ==

; Revival Elixir (Red)
: Used to fully revive your avatar after death.

; Breath of Vitality Elixir (Teal)
: Used to restore humans that have been drained by feeding (when their blood has been taken).

== Cost ==

Each elixir costs '''250 Linden Dollars (L$)'''.

They can be purchased at the '''Descendants of Darkness main land'''.

== How to Use ==

# Purchase the elixir:
#* Right-click the elixir vendor
#* Select '''Pay''' and enter '''L$250'''
# Take the item:
#* Right-click the elixir
#* Select '''Take''' to move it into your inventory
# Use the elixir:
#* Attach it to your avatar
#* Click the elixir in your hand
#* Select '''Open Bottle'''
#* Confirm by selecting '''Yes'''

Once consumed, your avatar will be restored to '''full health'''.

== Using Elixirs on Humans ==

Elixirs can also be used on humans.

* Once purchased, you can send the elixir to a human
* The human must attach the item
* They then use it the same way by opening and drinking the elixir

This allows you to restore humans that have been killed by feeding.

=Essence Chest=
[[File:EssenceChest400x400.png|left|thumb]]
The Essence Chest serves as a secure repository for your essence. Upon your demise, your essence would otherwise be lost, making it advisable to store it within the chest to prevent any loss. With the Essence Chest, you have the capability to deposit and withdraw essence at will. Moreover, you retain control over who can access your stored essence, with options to limit access to yourself, a select group, or open it to everyone. Additionally, you can track all transactions made with your essence through the transaction history feature. This provides transparency regarding who has withdrawn essence from your Chest. Finally, you have the ability to customize the appearance of your Essence Chest by selecting from various texture colors, including Gold, Blue, and Black.

=Overseer=
[[File:Oversee.png|left|thumb]]

= The Overseer Guide =
The '''Overseer''' is a monitoring device that allows you to track yourself or another player. It can alert you when the monitored player is attacked, nearing starvation, or needs help while offline.

If the tracked player is attacked, the Overseer will send a notification in '''Nearby Chat''' and, if configured, to '''Discord''' through a webhook.
----

----
== How Alerts Work ==
The server checks for attacks every '''15 minutes on the hour'''. If an attack has occurred, the Overseer will send an alert within that 15-minute window.

Alerts may include:

* Attack notifications
* Near starvation warnings
* Discord webhook notifications, if added

----

== What the Overseer Can Do ==
With the Overseer, you can:

* Monitor yourself or another player
* Receive attack alerts
* View attack logs for up to '''3 days'''
* View death logs
* View kill logs
* Remotely donate blood to an offline player
* Add Discord webhook alerts
* Remove the tracked player and add a new one

----

== How to Use the Overseer ==

# Rez the Overseer.
# Touch the Overseer to open the menu.
# Add yourself, or have the player you want to monitor touch it.
# Both players must be alive when adding a player.
# The tracked player may be resting, but they cannot be dead.

The Overseer hover text will change color depending on the tracked player’s health:
{| class="wikitable"
!Hover Text Color
!Meaning
|-
|Green
|Healthy
|-
|Yellow
|Warning
|-
|Red
|Danger
|}
<blockquote>'''Note:''' If the tracked player is dead, the menu options will not be available. The only available option will be to remove the player.</blockquote>
----

= Overseer Menu Options =

# Donate Blood
# View Attack Logs
# View Kill Logs
# View Death Logs
# Turn Off Attack Alert
# Turn Off Near Starvation Alert
# Set Starvation Alert
# Remove Player from Overseer
# Add Discord Webhook

----

== 1. Donate Blood ==
The '''Donate Blood''' option allows you to remotely feed the tracked player.

To donate blood:

* The tracked player must have been offline for at least '''4 hours'''.
* You must accept the debit permissions popup.
* The cost is '''L$50 per 0.500 liters'''.
* Donations increase in '''0.500 liter increments'''.

This is useful when a player cannot log in to feed themselves.<blockquote>'''Important:''' Debit permissions allow the Overseer to charge your account for the blood donation.</blockquote>
----

== 2. View Attack Logs ==
The '''View Attack Logs''' option lets you review attacks against the tracked player.

You can view logs for:

* Today
* Yesterday
* The day before yesterday

=== Example Attack Log ===
<code>╔═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰
║ Date: Jun 11, 2026 10:56:35 AM
║ Attacker: Oreo Cream Rуσʂհℹη (oreocream.baby)
║ Victim: Eva Rуσʂհℹη (evakora)
║ Damage done: 0.000
║ Victim's Health: 4.700
║ Location: Uphill
║ Teleport to Uphill (128,128,25)
║ Page 2 of 2 of attack logs.
╚═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰</code>
----

== Log Paging System ==
Attack logs, kill logs, and death logs all use a paging system.

Each page can display up to '''4 logs'''. The Overseer can print up to '''4 pages''' at a time. Once those pages are printed, you may be asked if you want to view more.

If you click '''More''', the Overseer will print older pages.

Think of the logs like a book:

* The newest logs are on the highest page numbers.
* When the logs print in Nearby Chat, the newest entries appear at the top.
* Older entries continue below as more pages are printed.

----

== 3. View Kill Logs ==
The '''View Kill Logs''' option shows every recorded time the tracked player has killed another player.

Kill logs may include:

* Date and time
* Victim name
* Killer name
* Location
* Teleport location
* Total kill count

=== Example Kill Log ===
<code>╔═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰
║ Date: Apr 21, 2026 08:12:35 PM
║ Victim: Ninjie
║ Killed by Eva Rуσʂհℹη (evakora)
║ Location: Social Island 10
║ Teleport to Social Island 10 (128,128,25)
║ Page 1 of 2 of kill logs.
╚═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⊰</code>

=== Example Total Kills Message ===
<code>╔═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰
║ Eva Rуσʂհℹη (evakora) has a total of 5 kills.
╚═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰</code>
----

== 4. View Death Logs ==
The '''View Death Logs''' option shows recorded deaths for the tracked player.

Death logs may include:

* Date and time
* Victim name
* Killer or cause of death
* Location
* Teleport location
* Total death count

=== Example Death Log ===
<code>╔═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰
║ Date: Apr 1, 2025 12:59:31 AM
║ Victim: Eva Rуσʂհℹη (evakora)
║ Killed by Kou Ayashi
║ Location: Kealani
║ Teleport to Kealani (128,128,25)
║ Page 3 of 4 of death logs.
╚═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰</code>

=== Example Total Deaths Message ===
<code>╔═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰
║ Eva Rуσʂհℹη (evakora) has died 13 times.
╚═⊱⋅•∙•⋅⋅•⋅⋅•⋅⊱⋅⋅•⋅⋅•∙⋅∘☽★☾∘⋅∙•⋅⋅•⋅⋅⊰⋅•⋅⋅•⋅⋅•⋅⋅∙•⋅⊰</code>
----

== 5. Turn Off Attack Alert ==
This option turns off attack alerts for the tracked player.

When attack alerts are turned off:

* You will no longer receive Nearby Chat attack messages.
* Discord webhook attack alerts will also stop.

----

== 6. Turn Off Near Starvation Alert ==
This option turns off near starvation alerts.

When this is turned off, you will not receive a Nearby Chat message when the tracked player is close to dying from lack of feeding.
----

== 7. Set Starvation Alert ==
The '''Set Starvation Alert''' option allows you to choose when you want to be warned before the tracked player dies from lack of feeding.

You can choose to be alerted:

* 1 day before death
* 2 days before death
* 3 days before death

For example, if you select '''1 day''', you will receive a notification in Nearby Chat and Discord when the player is within one day of dying from starvation.

If the alert is set to '''1 day''' and you receive the warning, the player will die at '''midnight''' if they are not fed.
----

== 8. Remove Player from Overseer ==
This option removes the currently tracked player from the Overseer.

After removing a player:

* You will no longer receive notifications about them.
* You may add a new player to the Overseer.

----

== 9. Add Discord Webhook ==
This option allows you to add a Discord Webhook URL to the Overseer.

Once added, the Overseer can send alerts to your chosen Discord channel when:

* The tracked player is attacked
* The tracked player is near death from starvation

<blockquote>'''Warning:''' Keep your Discord Webhook URL private. Anyone with the URL may be able to send messages to that Discord channel.</blockquote>
----

= How to Add a Discord Webhook to the Overseer =

== Step 1: Create a Discord Webhook ==

# Open Discord.
# Go to the server where you want Overseer alerts to appear.
# Click the server name in the top left.
# Select '''Server Settings'''.
# Click '''Integrations''' in the sidebar.
# Under '''Webhooks''', click '''Create Webhook'''.
# Choose the channel where alerts should be sent.
# Customize the webhook name and avatar if desired.
# Click '''Copy Webhook URL'''.

----

== Step 2: Add the Webhook URL to the Overseer ==

# Touch the Overseer to open the menu.
# Select '''Add Discord Webhook'''.
# Paste the Discord Webhook URL.
# Confirm the change to save it.

----

== Step 3: Test the Webhook ==
After adding the webhook, test it to make sure alerts are working.

You can test by:

* Simulating an attack on the tracked player
* Checking the selected Discord channel for the alert message

If the alert appears in Discord, the webhook is working correctly.
----

= Quick Reference =
{| class="wikitable"
!Option
!What It Does
|-
|Donate Blood
|Feeds an offline player using paid blood donation
|-
|View Attack Logs
|Shows recent attacks against the tracked player
|-
|View Kill Logs
|Shows kills made by the tracked player
|-
|View Death Logs
|Shows deaths and causes of death
|-
|Turn Off Attack Alert
|Stops attack alerts in Nearby Chat and Discord
|-
|Turn Off Near Starvation Alert
|Stops starvation warning alerts
|-
|Set Starvation Alert
|Sets a warning for 1, 2, or 3 days before starvation death
|-
|Remove Player from Overseer
|Removes the tracked player
|-
|Add Discord Webhook
|Sends Overseer alerts to Discord
|}

=Trial of Shadows=
{{:Trial of Shadows}}

In-World Devices

2026-06-12T20:21:38Z

Ninja: /* The Overseer Guide */

Ninja: /* Arch */

__TOC__
= Player =
When someone becomes a player, they are not affiliated with any family. They are considered a solitary player. The person who converted the player may choose to bring them into a family. If they do not, the player remains solitary. Solitary players are only bound by the system rules. If they are not a solitary player, they may be bound to the family rules. Moving from the concept of solitary players and their rules, let's delve into the structure of Houses/Packs/Circles.

= Houses/Packs/Covens =

A house consists exclusively of vampires, a pack exclusively of lycans, and a circle exclusively of witches. These formations cannot contain various species as it would contradict the roleplay. To create a house/pack/coven a player must have 10 or more followers and also pay the fee of 1000 Lindens. Currently, in the beta phase, the follower count is set to five followers.

= Clans =

A clan can include two or more houses, packs, or covens, either individually or in any combination. The clan is owned by the clan leader, known as the sovereign. Occasionally, there are two owners, with the second being the co-sovereign. After the sovereigns in leadership come the Ambassador, and finally, the Proxy. To start your own clan, you must meet the requirements below.

Requirements:

Approximately 25 active members within your house (not including alts or inactive accounts).
Payment of the clan creation fee (20,000 Lindens).
Completion and submission of the [https://docs.google.com/forms/d/e/1FAIpQLSf49QRpPqZKhS6ve9X4_rH7ie-agoDd5xR2iV9BqBARSXHb8A/viewform Clan Application Form] here.
Must include two or more houses.
Can pledge loyalty to an arch and encompass houses, packs, and covens.

= Bloodlines =
In the Realm of Darkness, a bloodline refers to a lineage or lineage-based group of individuals who share a common ancestry, heritage, or set of characteristics. These traits could include specific physical traits, a shared history, or even a common destiny. Bloodlines often hold significance within the world's lore, with members typically inheriting their status or abilities from their ancestors. They may form organized societies or factions within the world, each with its hierarchy, traditions, and goals. Bloodlines can play a central role in shaping the narrative, providing a framework for character development, conflict, and world-building within The Realm of Darkness.

= Arch =
An arch represents the highest position a player can hold within the hierarchy of a bloodline. Serving as the progenitor of the bloodline, the arch holds a revered and influential role, in guiding and inspiring their fellow players while upholding the values of fairness, integrity, and collaboration. As the ultimate authority, the arch initiates the creation of new bloodlines and oversees the community's growth and development. To ascend to the esteemed position of Arch within Descendants of Darkness, one must not only have 125 total members, but they must also embody the ideals of leadership, community, and progress. Below are the guidelines outlining what it takes to become an Arch, ensuring that those who hold this position are dedicated to the betterment of their bloodline and the system at large.

'''Community Engagement''': Archs must actively engage with the community, fostering a positive and inclusive environment within the bloodline. They should participate in discussions, events, and help resolve conflicts among members impartially.

'''Leadership Skills''': Archs should demonstrate strong leadership qualities, such as effective communication, decision-making, and problem-solving skills. They should be able to inspire and motivate others, leading by example and guiding members toward common goals. Commitment to Improvement: Archs must show a commitment to continuously improving the bloodline and the community as a whole. They should be open to feedback, willing to listen to suggestions from other members, and actively seek ways to enhance the experience.

'''Fairness and Impartiality''': Archs should be fair and impartial in their dealings with other members, avoiding favoritism or bias. They must uphold the rules and standards of the community, ensuring that all members are treated equally and respectfully.

'''Collaborative Spirit''': Archs should encourage collaboration and teamwork among members, promoting cooperation and mutual support. They should be able to delegate tasks effectively and recognize the contributions of others to the bloodline's success.

'''Vision for the Bloodline''': Archs should have a clear vision for the bloodline's future, with goals that align with the interests and aspirations of its members. They should be able to articulate this vision and inspire others to work towards it.

'''Diplomacy and Conflict Resolution''': Archs must possess diplomatic skills, able to navigate conflicts and disagreements peacefully and constructively. They should strive to maintain harmony within the bloodline and mediate disputes when necessary.

'''Adherence to Ethical Standards''': Archs should adhere to ethical standards, acting with integrity and honesty in all their interactions. They should prioritize the well-being of the community and avoid actions that could harm or disadvantage other members.

'''Knowledge and Experience''': Archs should have a good understanding of the lore and dynamics of the bloodline. They should also have experience in leadership roles or relevant areas that contribute to their effectiveness as an Arch.

'''Continuous Learning and Adaptability''': Archs should be willing to learn and adapt to new challenges and changes within the community. They should stay informed about updates, trends, and best practices to keep the bloodline vibrant and competitive.

MediaWiki:Common.css

2025-11-14T06:38:44Z

Ninja:

MediaWiki:Common.css

2025-11-14T06:37:47Z

Ninja:

/* Descendants of Darkness – bigger logo in left nav */
.mw-wiki-navigation-logo {
width: 250px !important; /* overall logo area width */
height: 250px !important; /* overall logo area height */
}

.mw-wiki-navigation-logo .mw-wiki-logo,
a.mw-wiki-logo {
display: block !important;
width: 100% !important; /* fill the container width */
height: 100% !important; /* fill the container height */
background-size: contain !important;
background-repeat: no-repeat !important;
background-position: left center !important;
}

/* If the menu looks squashed vertically, give the whole nav a bit more height */
#site-navigation {
min-height: 90px !important;
}

/* ============================================================
DESCENDANTS OF DARKNESS — GOTHIC DARK THEME (MEDIK)
============================================================ */

/* 0. Global reset: stop any skin element from forcing a white background */
.skin-medik *,
.skin-medik *::before,
.skin-medik *::after {
background-color: transparent !important;
}

/* 1. Base page background & text */
.skin-medik html,
.skin-medik body {
background-color: #050509 !important; /* almost black */
color: #dddddd !important;
}

/* 2. Main content area */
.skin-medik .mw-body,
.skin-medik #content,
.skin-medik .mw-content-container {
background-color: #09090f !important; /* slightly lighter panel */
color: #dddddd !important;
border: none !important;
}

/* Headings */
.skin-medik .mw-body h1,
.skin-medik .mw-body h2,
.skin-medik .mw-body h3,
.skin-medik .mw-body h4,
.skin-medik .mw-body h5 {
color: #f0f0f0 !important;
}

/* 3. Top bar / navbar – solid black */
.skin-medik .navbar,
.skin-medik .navbar-default,
.skin-medik #mw-head {
background-color: #000000 !important;
border-bottom: 1px solid #222 !important;
}

/* Top-left wiki name in the bar (white, not red) */
.skin-medik .navbar-brand,
.skin-medik .navbar-brand a {
color: #f5f5f5 !important;
text-shadow: none !important;
}

/* 4. Sidebar – dark, no white behind it */
.skin-medik #mw-panel {
background-color: #050509 !important;
color: #dddddd !important;
border: none !important;
}

/* Sidebar headings (Introduction, HUD Guide, etc.) */
.skin-medik #mw-panel .portal h3 {
color: #d64040 !important; /* red section titles */
}

/* Sidebar links */
.skin-medik #mw-panel a {
color: #f0f0f0 !important;
}

.skin-medik #mw-panel a:hover {
color: #ff5b5b !important;
}

/* 5. Article links (the ones in page content) */
.skin-medik .mw-body a,
.skin-medik .mw-body a:visited {
color: #d64040 !important;
}

.skin-medik .mw-body a:hover {
color: #ff5b5b !important;
}

/* 6. TOC, infoboxes, tables */
.skin-medik .toc,
.skin-medik .infobox,
.skin-medik .wikitable,
.skin-medik table {
background-color: #101018 !important;
border-color: #2a2a3a !important;
color: #dddddd !important;
}

/* 7. Kill any remaining white strips/wrappers explicitly */
.skin-medik #mw-head-base,
.skin-medik #mw-page-base,
.skin-medik #mw-wrapper,
.skin-medik .mw-page-container,
.skin-medik .mw-page-container-inner {
background-color: #050509 !important;
border: none !important;
}

/* 8. Logo – keep its original colours */
.skin-medik .mw-wiki-logo,
.skin-medik #p-logo a,
.skin-medik .mw-logo-icon img {
filter: none !important;
background-color: transparent !important;
}

/* ==== NAV BAR & DROPDOWN FIXES (MEDIK) ==== */

/* Top nav links (Main Page / Discussion / Actions / Tools etc.) */
.skin-medik .navbar-nav > li > a {
color: #f0f0f0 !important; /* light text on black bar */
}

/* Active/open nav item */
.skin-medik .navbar-nav > .open > a,
.skin-medik .navbar-nav > .open > a:focus,
.skin-medik .navbar-nav > .open > a:hover {
background-color: #151520 !important;
color: #ff5b5b !important;
}

/* Dropdown menu panel (for Actions, Tools, etc.) */
.skin-medik .dropdown-menu {
background-color: #101018 !important; /* dark panel, not invisible */
border: 1px solid #2a2a3a !important;
}

/* Links inside dropdown */
.skin-medik .dropdown-menu > li > a,
.skin-medik .dropdown-menu > li > a:link,
.skin-medik .dropdown-menu > li > a:visited {
color: #f0f0f0 !important;
}

/* Hover on dropdown items */
.skin-medik .dropdown-menu > li > a:hover,
.skin-medik .dropdown-menu > li > a:focus {
background-color: #191926 !important;
color: #ff5b5b !important;
}

MediaWiki:Common.css

2025-11-14T06:31:34Z

Ninja:

MediaWiki:Common.css

2025-11-14T06:24:25Z

Ninja:

/* Descendants of Darkness – bigger logo in left nav */
.mw-wiki-navigation-logo {
width: 250px !important; /* overall logo area width */
height: 250px !important; /* overall logo area height */
}

.mw-wiki-navigation-logo .mw-wiki-logo,
a.mw-wiki-logo {
display: block !important;
width: 100% !important; /* fill the container width */
height: 100% !important; /* fill the container height */
background-size: contain !important;
background-repeat: no-repeat !important;
background-position: left center !important;
}

/* If the menu looks squashed vertically, give the whole nav a bit more height */
#site-navigation {
min-height: 90px !important;
}

/* ============================================================
DESCENDANTS OF DARKNESS — GLOBAL DARK THEME (MEDIK)
============================================================ */

/* Base page background & text */
html, body {
background: #050509 !important; /* almost-black */
color: #dddddd !important;
}

/* Main content area */
.mw-body,
.mw-content-container,
#content {
background: #09090f !important;
color: #dddddd !important;
border: none !important;
}

/* Headings */
.mw-body h1,
.mw-body h2,
.mw-body h3,
.mw-body h4,
.mw-body h5 {
color: #f0f0f0 !important;
}

/* Top bar / navbar – keep it solid black */
.navbar,
.navbar-default,
#mw-head {
background: #000000 !important;
border-bottom: 1px solid #222 !important;
}

/* Top-left wiki name in the bar (white, not red) */
.navbar-brand,
.navbar-brand a {
color: #f5f5f5 !important;
text-shadow: none !important;
}

/* Left sidebar (kill the white behind it) */
#mw-panel,
#mw-panel .portal,
#mw-panel .body {
background: #050509 !important;
color: #dddddd !important;
border: none !important;
}

/* Sidebar section headings (Introduction, HUD Guide, etc.) */
#mw-panel .portal h3 {
color: #d64040 !important; /* red headings */
}

/* Sidebar links */
#mw-panel a {
color: #f0f0f0 !important;
}

#mw-panel a:hover {
color: #ff5b5b !important;
}

/* Article links (the ones in your content) */
.mw-body a,
.mw-body a:visited {
color: #d64040 !important;
}

.mw-body a:hover {
color: #ff5b5b !important;
}

/* TOC, infoboxes, tables */
.toc,
.infobox,
.wikitable,
table {
background: #101018 !important;
border-color: #2a2a3a !important;
color: #dddddd !important;
}

/* Logo – don’t mess with its colours */
.mw-wiki-logo,
#p-logo a,
.mw-logo-icon img {
filter: none !important;
background-color: transparent !important;
}
/* --- Fix remaining white behind sidebar & under top bar --- */
#mw-head-base,
#mw-page-base,
#mw-panel,
#mw-panel .portal,
#mw-panel .body,
#p-logo {
background-color: #050509 !important; /* same near-black as page */
border: none !important;
}

/* Just to be sure the overall screen never shows white */
body {
background-color: #050509 !important;
}
/* ==== FINAL WHITE-KILLER FOR MEDIK ==== */

.skin-medik html,
.skin-medik body,
.skin-medik #mw-wrapper,
.skin-medik .mw-page-container,
.skin-medik .mw-page-container-inner,
.skin-medik #mw-head-base,
.skin-medik #mw-page-base,
.skin-medik #content,
.skin-medik #p-logo,
.skin-medik #mw-panel,
.skin-medik #mw-panel .portal,
.skin-medik #mw-panel .body {
background-color: #050509 !important; /* same near-black as rest */
border: none !important;
}