Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Halloween: Cauldron to replace deep fryers #2240

Merged
merged 4 commits into from
Oct 17, 2024

Conversation

arimah
Copy link
Contributor

@arimah arimah commented Oct 15, 2024

About the PR

  • Adds a new entity, the cauldron, which is functionally identical to a deep fryer
  • Adds a new HalloweenSystem that effectively migrates all deep fryers to cauldrons, replacing them on map creation

Why / Balance

Spooky witch stuff! Brew things, or something.

The many identical-looking fill levels for the cauldron were added for compatibility with the deep fryer. I could set it to having only a single fill level, but then you can't even see if there's anything in the cauldron until it's full, which isn't ideal. This solution also isn't ideal, but it's for a single day only, so.

The cauldron can be deconstructed and reconstructed to make a normal deep fryer. This is intentional: (1) it gives players a way to "opt out" of the funny meme, (2) I'm too lazy to go and define a unique board for this once-a-year playfulness.

How to test

  1. Either set your computer's clock to 31st of October or modify the Halloween holiday to be active on whatever day you're testing this.
  2. Spawn on the dev map. The deep fryer should now be a cauldron.
  3. Warp to Tinnia's. The deep fryer should now be a cauldron.
  4. Warp to Bahama Mama's. The deep fryer should now be a cauldron.
  5. Buy a food ship. Its deep fryer should now be a cauldron.
  6. Use the cauldron like a normal deep fryer.
  7. Deconstruct and reconstruct the cauldron to get a deep fryer.
  8. Ensure that the cauldrons on POIs block tool use.
  9. Try doing deep dark magic with the cauldron. You know, for science.

Media

2024-10-15.18-14-59.mp4

Requirements

Breaking changes

No.

Changelog
N/A, let people discover as they play the game.

Copy link
Contributor

github-actions bot commented Oct 15, 2024

RSI Diff Bot; head commit 63cc41f merging into cc5c54d
This PR makes changes to 1 or more RSIs. Here is a summary of all changes:

Resources/Textures/_NF/Structures/Machines/cauldron.rsi

State Old New Status
off-0 Added
off-1 Added
off-2 Added
off-3 Added
off-4 Added
off-5 Added
off-6 Added
off-7 Added
off-8 Added
on-1 Added
on-2 Added
on-3 Added
on-4 Added
on-5 Added
on-6 Added
on-7 Added
on-8 Added

Edit: diff updated after 63cc41f

@arimah
Copy link
Contributor Author

arimah commented Oct 15, 2024

The beautiful sprites were made by Bing Guss and very slightly modified by me.

@whatston3
Copy link
Contributor

Want a spooky shader for ghostly food?

@arimah
Copy link
Contributor Author

arimah commented Oct 15, 2024

Want a spooky shader for ghostly food?

I love you. Yes.

@dvir001
Copy link
Contributor

dvir001 commented Oct 15, 2024

This feels like the system can be a more general holiday system but its fine as it is.

@Ansome101
Copy link
Contributor

Might I suggest extending the period that the cauldrons (and any future Halloween items) are available by a few more days? Something to the tune of October 27th-31st would work well, otherwise you'll only see these cauldrons for at best four shifts on Maunder and likely only one on Hypatia. I ask because SS13 servers traditionally have their Halloween mode last a few days to ensure a fair number of players can experience the seasonal content.

@whatston3
Copy link
Contributor

whatston3 commented Oct 15, 2024

Had to fight with the shared DeepFriedComponent definition, it really doesn't like replicating its own state onto the client when changed on the server. Did get something working though. Also, brings back the "deep-fried" state, and the possibility to describe more through a prototype.

Results are up here: whatston3:halloween-cauldron-spooky-frying

Shader could probably use some work, maybe the brighter something is, the closer it turns to a purplish colour.

image

Also added a spooky cat (no recipe) to match crispy. Dumb idea, probable trash, but shown for completeness of "this is a deep fryer shader alternative".

image

@GreaseMonk
Copy link
Contributor

GreaseMonk commented Oct 16, 2024

optionally add green glow for extra spook

@GreaseMonk
Copy link
Contributor

PS i will help fix this pr if need be

Copy link
Contributor

@GreaseMonk GreaseMonk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In light of new information the conclusion is my comments on this pr are invalidated and there is just no other way . the code spooked me

Copy link
Contributor Author

@arimah arimah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay so, right, okay, so, despite the conversation basically resulting in "the hardcoded entity prototype IDs are okay for now", I had a few minutes to think and came up with a more general solution that would let us trivially add future entity replacements, including more Halloween ones: arimah#1

If you think that's more reasonable (I think it is), I'll update this branch.

@GreaseMonk
Copy link
Contributor

this is awesome 👍🏼 arimah#1 insta merge

@Cheackraze
Copy link
Member

yea generecizing it asap would actually probably be good. Like most holiday themed fun PRs, these often get rushed, forced into code, and then swiftly forgotten until the next holiday and we do it again. And, we are heading into holiday season where we will likely have even more use for such a system.

@GreaseMonk GreaseMonk merged commit 79626e3 into new-frontiers-14:master Oct 17, 2024
16 checks passed
@Ansome101 Ansome101 mentioned this pull request Oct 19, 2024
2 tasks
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.

6 participants