Skip to content

Revert shadekin#1744

Merged
fenndragon merged 7 commits into
masterfrom
revert-Shadekin
May 13, 2026
Merged

Revert shadekin#1744
fenndragon merged 7 commits into
masterfrom
revert-Shadekin

Conversation

@fenndragon
Copy link
Copy Markdown
Collaborator

@fenndragon fenndragon commented May 12, 2026

About the PR

Reverts the abysmal way the shadekin and nullspace got butchered recently and anomalies being implemented so that shadekin, the anomaly role, and the dark can be implemented in a more cohesive and solid state in the future.

Why / Balance

Technical details

How to test

Media

Breaking changes

Changelog

🆑

  • remove: Removed nullphase/shadekin changes
  • remove: temporarily removed the Anomaly job role

Revert "Apply Fixes (#1644)"

This reverts commit a72049b.

Revert "Fix "The Dark" getting cleanup. (#1595)"

This reverts commit 164b46d.

revert
@ShadesMars
Copy link
Copy Markdown
Contributor

Dont rever it to my old previous outated code, just because of some bugs that was fixed.
Talk to me instead in dev channel.

@fenndragon fenndragon merged commit b4ba611 into master May 13, 2026
13 of 14 checks passed
xemeraldwingx-dot added a commit that referenced this pull request May 13, 2026
@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

So had this one actually gotten talked to about like Shades asked? Or what was the consensus to us who weren't in the know case-wise of what happened?

@NotLivyathan
Copy link
Copy Markdown

So had this one actually gotten talked to about like Shades asked? Or what was the consensus to us who weren't in the know case-wise of what happened?

It was never up for discussion.

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

I try to be considerate to all, but it would be definitely nice to have the same given back in equal, or at least get better transparency on actions.

Or at minimum, a tl;dr of what changed because i'm under a decent assumption that this isn't a -small- revert, especially with the author saying that reverting this would take us back to outdated code that was supposedly bugfixed.

@Magniras
Copy link
Copy Markdown
Contributor

Oh, did the shadekin creator see and complain?

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

Oh, did the shadekin creator see and complain?

I feel like 'complain' is definitely the wrong word, given the fact they were actively testing, bugfixing, balancing and doing a lot of hard work to reign in areas that were problematic. They've been willingly open to do what they can to fix things and listen, let alone openly communicate on these things. The author for anomaly/and the shadekin PR implementations from other places asked above to just be -talked- to. That is not unreasonable to do, I just wanted to know if it happened or not.

@Magniras
Copy link
Copy Markdown
Contributor

Not Shades, uh, whats their name. Verysoft. Casey.

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

Not Shades, uh, whats their name. Verysoft. Casey.

Wuh? No??? I specified Shades, the one who authored the anomaly role and all the Shadekin PR fixes here. I don't think I'd know if that person who as far as i'm aware isn't on this server has complained or not. I only asked if there'd been any communication at all on the revert given its size and effort and fact it was being actively fixed, or if we just ignored the authors request to just be -talked- to. You know. Basic common decency at minimum. I HOPE (or at least have optimism) we did that.

@Magniras
Copy link
Copy Markdown
Contributor

Yeah, I wasn't asking you? I was asking in general. Also they're on server.

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

Yeah, I wasn't asking you? I was asking in general. Also they're on server.

Oh apologies. I keep forgetting the way github lays out responses and stuff, sometimes it's hard to know who someone's talking to.

But unless they say something, i'm going to assume not?

@IngvarJackal
Copy link
Copy Markdown
Contributor

Very curious pull request. I will just leave those quotes here for the future reference.

image image

@ShadesMars
Copy link
Copy Markdown
Contributor

I see that instead waiting because im sleeping you go forward with this and revert it all.

Even when the previous PR was going to have the flashers changes you wanted.

@IrkallaEpsilon
Copy link
Copy Markdown
Contributor

IrkallaEpsilon commented May 13, 2026

Shadekin changes cannot be "abysmal" at all. Why you ask? Well its pretty simple you said it yourself.

As you previously stated and heavily enforced: Shadekin CANNOT interact with Abyssals.

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

Shadekin changes cannot be "abysmal" at all. Why you ask? Well its pretty simple you said it yourself.

As you previously stated and heavily enforced: Shadekin CANNOT interact with Abyssals.

They meant "the way this got put in was abysmal (bad)".

They didn't mean anything relevant to interacting with Abyssal entities.

@IrkallaEpsilon
Copy link
Copy Markdown
Contributor

Shadekin changes cannot be "abysmal" at all. Why you ask? Well its pretty simple you said it yourself.
As you previously stated and heavily enforced: Shadekin CANNOT interact with Abyssals.

They meant "the way this got put in was abysmal (bad)".

They didn't mean anything relevant to interacting with Abyssal entities.

Well aware of it.

@Dhizi
Copy link
Copy Markdown

Dhizi commented May 13, 2026

Shadekin changes cannot be "abysmal" at all. Why you ask? Well its pretty simple you said it yourself.
As you previously stated and heavily enforced: Shadekin CANNOT interact with Abyssals.

They meant "the way this got put in was abysmal (bad)".
They didn't mean anything relevant to interacting with Abyssal entities.

Well aware of it.

Then I am utterly confused. Sarcasm??????

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants