Skip to content

Conversation

@snowywinters
Copy link
Contributor

@snowywinters snowywinters commented Dec 24, 2025

About the PR

Adds reinforced cameras and a new sebnet for Ai cameras/routers

Why / Balance

https://discord.com/channels/968983104247185448/1447879561122418731
main reason was because meteors could take out the cameras from over 5 tiles away and the normal camera was too easy to take out by random stuff

For the ai camera subnet is is so the Ai core cameras don't take up space in commands subnet and being its own area it should have its own

Technical details

the reinforced cameras have the following

  1. health 275
    2.explosion resistance 75%
    NOTE: for meteors and any c4 or bombs like it can take out the cameras 1 tile away and can only survive one non direct impact from a meteor and a direct impact will take it out
  2. can be repaired with a welder
  3. has the Electronic damage modifier set which has 30% blunt, 50% slash, 30% Piercing, shock 2, heat 3, and Structural 50%
  4. has the security wire panel so you can add steel/plasteel to the wire panel it only needs one steel/plasteel instead of two
  5. has the full deconstruction route that works and gives mats back
  6. for construction look below in media
  7. command and ai mapping cameras have plasteel the rest have steel in the wire panel
    i don't believe i forgot anything

AI camera subnet

  1. adds a AI subnet
  2. adds a mapping camera for the Ai subnet
  3. adds a camera router for the Ai subnet

Media

Screenshot 2025-12-23 231815 Screenshot 2025-12-23 231927

Requirements

  • I have tested all added content and changes.
  • I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

🆑

  • add: Reinforced cameras can now be built! They have additional HP and are more resistant to explosions and meteors.
  • add: The AI has its own section in the security cameras console.

@snowywinters snowywinters requested a review from a team as a code owner December 24, 2025 08:05
@github-actions github-actions bot added S: Needs Review Awaiting review from a Maintainer size/XL Over 1024 lines Changes: YML Changes any yml files Changes: Localization Changes any ftl files Changes: Sprite Changes any png or json in an rsi S: Merge Conflict Fix your PR! and removed size/XL Over 1024 lines labels Dec 24, 2025
@github-actions
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 24, 2025

RSI Diff Bot; head commit 379d46e merging into 5eaf79d
This PR makes changes to 1 or more RSIs. Here is a summary of all changes:

Resources/Textures/_DV/Structures/Wallmounts/Reinforced_camera.rsi

State Old New Status
reinforced_camera Added
reinforced_camera_assembly Added
reinforced_camera_emp Added
reinforced_camera_in_use Added
reinforced_camera_off Added

Edit: diff updated after 379d46e

@github-actions github-actions bot added size/XL Over 1024 lines and removed S: Merge Conflict Fix your PR! labels Dec 24, 2025
Copy link
Contributor

@ShepardToTheStars ShepardToTheStars left a comment

Choose a reason for hiding this comment

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

Recommend creating a SurveillanceCameraReinforcedBase and putting all of the common attributes on that. It would greatly reduce the amount of duplicated code. Then you could double-parent based off the department. I added it to the first suggestion of the reinforced camera file.

Comment on lines 11 to 59
- type: deviceFrequency
id: ReinforcedSurveillanceCamera
name: device-frequency-prototype-name-surveillance-camera
frequency: 1926

- type: deviceFrequency
id: ReinforcedSurveillanceCameraEngineering
name: device-frequency-prototype-name-surveillance-camera-engineering
frequency: 1931

- type: deviceFrequency
id: ReinforcedSurveillanceCameraSecurity
name: device-frequency-prototype-name-surveillance-camera-security
frequency: 1932

- type: deviceFrequency
id: ReinforcedSurveillanceCameraScience
name: device-frequency-prototype-name-surveillance-camera-science
frequency: 1933

- type: deviceFrequency
id: ReinforcedSurveillanceCameraSupply
name: device-frequency-prototype-name-surveillance-camera-supply
frequency: 1934

- type: deviceFrequency
id: ReinforcedSurveillanceCameraCommand
name: device-frequency-prototype-name-surveillance-camera-command
frequency: 1935

- type: deviceFrequency
id: ReinforcedSurveillanceCameraService
name: device-frequency-prototype-name-surveillance-camera-service
frequency: 1936

- type: deviceFrequency
id: ReinforcedSurveillanceCameraMedical
name: device-frequency-prototype-name-surveillance-camera-medical
frequency: 1937

- type: deviceFrequency
id: ReinforcedSurveillanceCameraGeneral
name: device-frequency-prototype-name-surveillance-camera-general
frequency: 1938

- type: deviceFrequency
id: ReinforcedSurveillanceCameraEntertainment
name: device-frequency-prototype-name-surveillance-camera-entertainment
frequency: 1939
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these needed? Can't we just use the previous frequencies as as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

they are the default camera frequencies for the camera subnet they where just added since each mapping camera has to have its own variant so mappers can map then in different departments faster like the normal cameras but they do use the base camera frequency since that frequency is that cameras subnet

@ShepardToTheStars ShepardToTheStars added S: Awaiting Changes Do not merge due to requested changes and removed S: Needs Review Awaiting review from a Maintainer labels Dec 24, 2025
snowywinters and others added 3 commits December 24, 2025 20:44
Recommend by ShepardToTheStars thanks a lot for the recommendation and code start
@github-actions github-actions bot added S: Needs Review Awaiting review from a Maintainer and removed S: Awaiting Changes Do not merge due to requested changes labels Dec 25, 2025
@Cepelinas1 Cepelinas1 added the Waiting on Direction This pull request is waiting on a decision from the Direction team. label Dec 30, 2025
@Cepelinas1
Copy link
Contributor

approved

@Cepelinas1 Cepelinas1 added S: Direction Approved This PR has been approved by a member of Direction and removed Waiting on Direction This pull request is waiting on a decision from the Direction team. labels Dec 31, 2025
@snowywinters
Copy link
Contributor Author

@ShepardToTheStars will this be looked at to merge Or was it sadly forgotten with the massive amounts of work flow?

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

Labels

Changes: Localization Changes any ftl files Changes: Sprite Changes any png or json in an rsi Changes: YML Changes any yml files S: Direction Approved This PR has been approved by a member of Direction S: Needs Review Awaiting review from a Maintainer size/XL Over 1024 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants