Site Director Drugs Employees Out of Frustration at Low Slop Sales







Site Director Drugs Employees Out of Frustration at Low Slop Sales

By Karen Langtavious Sin Quinqleberm
The Mask News Reporter
| Published December 4th, 2022 |

Site-21 FPZ - After a hard day's work, Site-21 employees intermingled in the hallways of the personnel quarters as the intercoms of the site announced that 'Slop Sunday' had begun in the cafeteria. Slop Sunday is a new nutritional program formed by site administration which has seen little success due to remarkably terrible taste. Staff reported seeing Site Director John Merlin not long after the announcement accost several personnel and ordered them to report to the cafeteria.

"Yeah, I dunno, he was just yelling at them and asking why anyone would even dare pass on a nutritional meal," Immanuel Tygan, Volunteer said. "I personally don't like the stuff, but knowing how passionate he is about it, I don't think anyone is willing to say that to his face."

2022-12-04_15.17.36.png
Picture of the Site Director and Mark Wilson. Source: Purple Guy

Audio recordings recovered from the cafeteria reveal that employees had to resort to pouring cups of coffee and shredding bits of steak to make the taste of the slop tolerable to eat. Further, silent sobbing and prayers were picked up, indicating distress at the mandatory meal.

"It was nasty, even with the caffeine flavoring," Mark Wilson, Construction and Maintenance Intern said. "I think it's got beetroots, or something like that in there? Lord shudders to know what it's made with."

Minutes after the group had finished their impromptu luncheon, the employees began convulsing and vomiting violently, including others who have not consumed the slop. Audio-visual devices reveal that the victims experienced extreme paranoia, levitation, being able to see into other's souls, and hallucinations. Merlin was seemingly unaffected by the maladies.

"You know what? It was totally because he was salty that the slop wasn't bringing in enough profit. I wouldn't be surprised if that were the case," Clover Evans, Security Guard said.

Advertisement
r5kM4ru.png

The Slop Sunday program costs the site $6,752 annually to run, while only bringing in $52 in sales revenue - not withstanding this incident, which is an outlier and has not been considered.

Karen Langtavious Sin Quinqleberm
The Mask News Reporter
  • Karen Langtavious Sin Quinqleberm is a news reporter for The Mask and is excellent at his job.
  • Contact Karen Langtavious Sin Quinqleberm at rat.ksameht|mrebelgniuqnissuoivatgnalnaerak#rat.ksameht|mrebelgniuqnissuoivatgnalnaerak
  • Got a confidental tip? 👉 Submit it here

1 Comments

KittenPixel 42131e182ea29c943bdd79477deee017.webp?size=32

EXCUUUSEEE MEEEE I ET SLOP EVERIDAY !!!!

More articles you may like:

  • Is Site Director Merlin related to the legendary wizard? Merlin's DNA test revealed.
  • Investors in uproar after Site-21 floods market with cheap lab-produced diamonds.
  • Top 10 reasons why you shouldn't check Wilson's office bookshelves: #1 will shock you!
rating: 0+x

What this is

A bunch of miscellaneous CSS 'improvements' that I, CroquemboucheCroquembouche, use on a bunch of pages because I think it makes them easier to deal with.

The changes this component makes are bunch of really trivial modifications to ease the writing experience and to make documenting components/themes a bit easier (which I do a lot). It doesn't change anything about the page visually for the reader — the changes are for the writer.

I wouldn't expect translations of articles that use this component to also use this component, unless the translator likes it and would want to use it anyway.

This component probably won't conflict with other components or themes, and even if it does, it probably won't matter too much.

Usage

On any wiki:

[[include :scp-wiki:component:croqstyle]]

This component is designed to be used on other components. When using on another component, be sure to add this inside the component's [[iftags]] block, so that users of your component are not forced into also using Croqstyle.

Related components

Other personal styling components (which change just a couple things):

Personal styling themes (which are visual overhauls):

CSS changes

Reasonably-sized footnotes

Stops footnotes from being a million miles wide, so that you can actually read them.

.hovertip { max-width: 400px; }

Monospace edit/code

Makes the edit textbox monospace, and also changes all monospace text to Fira Code, the obviously superior monospace font.

@import url('https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;700&display=swap');
 
:root { --mono-font: "Fira Code", Cousine, monospace; }
#edit-page-textarea, .code pre, .code p, .code, tt, .page-source { font-family: var(--mono-font); }
.code pre * { white-space: pre; }
.code *, .pre * { font-feature-settings: unset; }

Teletype backgrounds

Adds a light grey background to <tt> elements ({{text}}), so code snippets stand out more.

tt {
  background-color: var(--swatch-something-bhl-idk-will-fix-later, #f4f4f4);
  font-size: 85%;
  padding: 0.2em 0.4em;
  margin: 0;
  border-radius: 6px;
}

No more bigfaces

Stops big pictures from appearing when you hover over someone's avatar image, because they're stupid and really annoying and you can just click on them if you want to see the big version.

.avatar-hover { display: none !important; }

Breaky breaky

Any text inside a div with class nobreak has line-wrapping happen between every letter.

.nobreak { word-break: break-all; }

Code colours

Add my terminal's code colours as variables. Maybe I'll change this to a more common terminal theme like Monokai or something at some point, but for now it's just my personal theme, which is derived from Tomorrow Night Eighties.

Also, adding the .terminal class to a fake code block as [[div class="code terminal"]] gives it a sort of pseudo-terminal look with a dark background. Doesn't work with [[code]], because Wikidot inserts a bunch of syntax highlighting that you can't change yourself without a bunch of CSS. Use it for non-[[code]] code snippets only.

Quick tool to colourise a 'standard' Wikidot component usage example with the above vars: link

:root {
  --c-bg: #393939;
  --c-syntax: #e0e0e0;
  --c-comment: #999999;
  --c-error: #f2777a;
  --c-value: #f99157;
  --c-symbol: #ffcc66;
  --c-string: #99cc99;
  --c-operator: #66cccc;
  --c-builtin: #70a7df;
  --c-keyword: #cc99cc;
}
 
.terminal, .terminal > .code {
  color: var(--c-syntax);
  background: var(--c-bg);
  border: 0.4rem solid var(--c-comment);
  border-radius: 1rem;
}

Debug mode

Draw lines around anything inside .debug-mode. The colour of the lines is red but defers to CSS variable --debug-colour.

You can also add div.debug-info.over and div.debug-info.under inside an element to annotate the debug boxes — though you'll need to make sure to leave enough vertical space that the annotation doesn't overlap the thing above or below it.

…like this!

.debug-mode, .debug-mode *, .debug-mode *::before, .debug-mode *::after {
  outline: 1px solid var(--debug-colour, red);
  position: relative;
}
.debug-info {
  position: absolute;
  left: 50%;
  transform: translateX(-50%);
  font-family: 'Fira Code', monospace;
  font-size: 1rem;
  white-space: nowrap;
}
.debug-info.over { top: -2.5rem; }
.debug-info.under { bottom: -2.5rem; }
.debug-info p { margin: 0; }
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License