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

Engineering, janitor, and medical holosign projectors are much faster, and have a max capacity of 12. Their integrity have been reduced. #5

Merged
merged 2 commits into from
May 19, 2023

Conversation

Pickle-Coding
Copy link
Owner

@Pickle-Coding Pickle-Coding commented May 19, 2023

Reduces janitor, engineering, and medical holosign creation time to 6 seconds. Increases max sign count of engineering and medical holobarriers to 12.

About The Pull Request

Sets the holosign creation time for the engineering, janitor, and medical holosign projectors to 0.6 seconds. Increases engineering and medical holosign projector max capacity to 12. Engineering, janitorial, and medical holosign integrity have been reduced to 1.

Why It's Good For The Game

Holosign projectors, especially the engineering ones (as the situation that warrents them is an emergency that does not have a lot of time to waste), are not used often. Their time to project was too long to be practical for an emergency, and a capacity of 6 is somewhat restrictive for what can warrent their usage.

Their integrity got reduced so hopefully they can't be used to Fortnite.

Changelog

🆑
balance: Engineering, janitorial and medical holosign projector projection time reduced to 0.6 seconds.
balance: Engineering and medical holosign projector max capacity increased to 12.
balance: Engineering, janitorial and medical holobarrier integrity reduced to 1.
/:cl:

Reduces janitor, engineering, and medical holosign creation time to 6 seconds. Increases max sign count of engineering and medical holobarriers to 12.
Reduces the integrity of the engineering, janitor, and medical holosigns to 1. I wish they just let the barrier subclass be an abstract base class instead of being used gor security.
@Pickle-Coding Pickle-Coding merged commit b275b6c into master May 19, 2023
6 checks passed
github-actions bot added a commit that referenced this pull request May 19, 2023
@Pickle-Coding
Copy link
Owner Author

Why does proposing changes on github mobile directly push to master?

Pickle-Coding added a commit that referenced this pull request May 19, 2023
…h faster, and have a max capacity of 12. Their integrity have been reduced. (#5)"

This reverts commit b275b6c.
Pickle-Coding added a commit that referenced this pull request May 19, 2023
…h faster, and have a max capacity of 12. Their integrity have been reduced. (#5)" (#6)

This reverts commit b275b6c.
Pickle-Coding pushed a commit that referenced this pull request Sep 6, 2023
…nent (tgstation#77539)

## About The Pull Request

Hey there,

I've personally fallen for this stupid thing twice (in tgstation#77503 and tgstation#75627
(d357516)), so I decided to spend a few
hours to crack out a unit test to ensure that I (and no one else) falls
for this stupid thing again.

Let me know if there's a smarter way to code something like this, but I
couldn't figure out a better way to accomodate the current framework and
be as agnostic to certain oddities as possible.
## Why It's Good For The Game
Catches stuff like this:

```txt
[2023-08-11 21:10:04.019]     FAILURE #1: The mob Garden Gnome does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE #2: The mob the morph does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE #3: The mob the guard spiderling (946) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE #4: The mob the ambush spiderling (255) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE #5: The mob the scout spiderling (375) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE #6: The mob the flesh spiderling (337) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#7: The mob the hunter spiderling (869) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#8: The mob the nurse spiderling (629) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#9: The mob the tangle spiderling (19) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#10: The mob the broodmother spiderling (855) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#11: The mob the viper spiderling (519) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#12: The mob the tarantula spiderling (963) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
 -     FAILURE tgstation#13: The mob the spiderling (100) does not have ANY instances of TRAIT_SUBTREE_REQUIRED_ELEMENT, but has a planning subtree (/datum/ai_planning_subtree/target_retaliate/to_flee) that requires it! at code/modules/unit_tests/ensure_subtree_element.dm:45
```

(ignore the part about gnomes and morphs, this was an earlier version of
the unit test. everything else was relevant and is fixed)
## Changelog
:cl:
fix: Growing spiders will now retaliate against you like they were
always meant to.
/:cl:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant