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

Vault ghoul ban 2 #687

Merged
merged 24 commits into from
Nov 14, 2024
Merged

Conversation

ReginaeSpence
Copy link
Contributor

Description

Another formatting test against the Linter, my archnemesis.

Description.

Adjusted the parsing on the "-".


CL

# Changelog

🆑
change: adjusted "-"
me: praying 👀

@Peptide90 Peptide90 merged commit 8d59cce into Vault-Overseers:master Nov 14, 2024
8 checks passed
VMSolidus pushed a commit to VMSolidus/nuclear-14 that referenced this pull request Nov 15, 2024
# Description

I have made this originally for N14 as there was a heavy need for junk
items to be list instead of a hash. It created a few issues where you
were unable to put down 2 pieces of steel without making a new defined
entity which spawns a stack of 2.
I thought this was quite annoying so I decided to instead make it into a
`EntitySpawnEntry` from a `string` which would also give it options of
`amount` `prob` `maxAmount` and `orGroup` which would definitely aid in
the scrapping needs there as you could randomize the refined amounts.

I believe this could be useful upstream. As well as cleaning up code
which is more modifiable than before.

The new example of how it can be typed in yaml is also simpler in my
opinion as it is self-explanatory and used in various places like
StorageFill contents for one.
```YAML
  - type: WelderRefinable
    refineResult:
    - id: SheetGlass1
      amount: 1
      maxAmount: 2
      prob: 0.5
      orGroup: Glass
```

---

:cl:
refactor: Refactors WelderRefinableComponent.cs and RefiningSystem.cs
tweak: Tweaked the formatting for WelderRefinable refineResult to use
EntitySpawnEntry format
VMSolidus pushed a commit to VMSolidus/nuclear-14 that referenced this pull request Nov 15, 2024
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.

2 participants