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

[MIRROR] Makes attempting to refresh the logs not just throw a runtime error #2751

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

Steals-The-PRs
Copy link
Collaborator

Mirrored on Nova: NovaSector/NovaSector#1814
Original PR: tgstation/tgstation#82432

About The Pull Request

Really all this seems to be is a mismatch between the tgui and dm side of the menu.
https://github.com/tgstation/tgstation/blob/3c71b14df0957749f31fb2e678130daf4cfb3250/tgui/packages/tgui/interfaces/LogViewer.tsx#L71
https://github.com/tgstation/tgstation/blob/3c71b14df0957749f31fb2e678130daf4cfb3250/code/modules/logging/log_holder.dm#L110-L113
Making these line up by renaming re-render to refresh seems to make it work just fine, and not just throw an error.

Why It's Good For The Game

Life tends to be better when refreshing to see new runtimes doesn't just add its own lovely little runtimes.
image
image
And then not show them til you re-open the window cause it doesn't refresh.

Changelog

🆑 00-Steven
admin: Refresh button on the View Round Logs menu actually works, instead of just adding a runtime to the logs (and not updating them).
/:cl:

…e error (#1814)

* Makes attempting to refresh the logs not just throw a runtime error (#82432)

## About The Pull Request

Really all this seems to be is a mismatch between the tgui and dm side
of the menu.

https://github.com/tgstation/tgstation/blob/3c71b14df0957749f31fb2e678130daf4cfb3250/tgui/packages/tgui/interfaces/LogViewer.tsx#L71

https://github.com/tgstation/tgstation/blob/3c71b14df0957749f31fb2e678130daf4cfb3250/code/modules/logging/log_holder.dm#L110-L113
Making these line up by renaming `re-render` to `refresh` seems to make
it work just fine, and not just throw an error.
## Why It's Good For The Game

Life tends to be better when refreshing to see new runtimes doesn't just
add its own lovely little runtimes.

![image](https://github.com/tgstation/tgstation/assets/42909981/79bee3db-5c28-409b-9ff5-3a315fb4ed1c)

![image](https://github.com/tgstation/tgstation/assets/42909981/82a25038-ba7a-430a-bb79-f59d5f4b262b)
And then not show them til you re-open the window cause it doesn't
refresh.
## Changelog
:cl:
admin: Refresh button on the View Round Logs menu actually works,
instead of just adding a runtime to the logs (and not updating them).
/:cl:

* Makes attempting to refresh the logs not just throw a runtime error

---------

Co-authored-by: _0Steven <[email protected]>
@Iajret Iajret merged commit cef3dd1 into master Apr 5, 2024
26 checks passed
@Iajret Iajret deleted the upstream-mirror-1814 branch April 5, 2024 13:32
AnywayFarus added a commit that referenced this pull request Apr 5, 2024
Iajret pushed a commit that referenced this pull request May 30, 2024
…when the drone is seperated from the node (#2751)

* Increases move resistance on NODE Drones, adds handling for when the drone is seperated from the node (#83309)

## About The Pull Request

NODE Drones now have higher move resistance
(MOVE_FORCE_EXTREMELY_STRONG), preventing them from being bumped off the
node, pulled away, or lifted away by a fulton extraction kit.

As an extra layer of assurance, the NODE Drone will depart from the site
if it is moved off of its vent.

## Why It's Good For The Game

Closes #83164.

I'm pretty sure these things shouldn't really be ever moving off of
their vents.
## Changelog
:cl: Rhials
fix: You can no longer force NODE Drones off of ore vents. That includes
using fulton packs!
fix: When a NODE Drone is forcibly separated from its vent, it will fly
away.
/:cl:

* Increases move resistance on NODE Drones, adds handling for when the drone is seperated from the node

---------

Co-authored-by: Rhials <[email protected]>
Co-authored-by: NovaBot13 <[email protected]>
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.

3 participants