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

Added a cooldown failure message that makes a nod to the cross-server… #2652

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Pockets-byte
Copy link
Contributor

… comms also being cross-time

basically what it says. there's nothing more to it

Why It's Good For The Game

casual time travel is casual

Changelog

🆑
tweak: added a rejection message to the comms console
/:cl:

@williamcll
Copy link

Remind me again how many years are there between bee and nsv?

Copy link
Contributor

@DeltaFire15 DeltaFire15 left a comment

Choose a reason for hiding this comment

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

Not a big fan of this going for "time travel".

I prefer the implicit relative time adjustment from simple "interstation comms", aka you here pretend the beestation you are talking to is the one of the current year, and beestation pretends the patrol ship they're getting a call from is in their time.

Otherwise the entire "people talk to eachother like they know eachother", which obviously happens, makes zero sense (besides the whole thing about there not being any known means of time travel in the scenario [Temporal Agents are not real]).

code/game/machinery/computer/communications.dm Outdated Show resolved Hide resolved
@Pockets-byte
Copy link
Contributor Author

Pockets-byte commented May 14, 2024

Not a big fan of this going for "time travel".

I prefer the implicit relative time adjustment from simple "interstation comms", aka you here pretend the beestation you are talking to is the one of the current year, and beestation pretends the patrol ship they're getting a call from is in their time.

Otherwise the entire "people talk to eachother like they know eachother", which obviously happens, makes zero sense (besides the whole thing about there not being any known means of time travel in the scenario [Temporal Agents are not real]).

I think it's more in line with the setting to have casual time travel that's used for inane reasons - reminder that chrono legionaries are not the only time effects that can be seen- things like wizards or sepia slime stuff. and I mean- people could go it the long way around- and possibly imply that this can be done elsewhere- it's a plot hole either way, and I personally think this is a better(and funner) way of handling it than not addressing it at all- and in addition- this is time communication, not time travel - on our side, it could also be flavored as a time capsule, as downstream is easier than upstream, but again, in my opinion it's not as fun

Remind me again how many years are there between bee and nsv?

200

@williamcll
Copy link

Not a big fan of this going for "time travel".

I prefer the implicit relative time adjustment from simple "interstation comms", aka you here pretend the beestation you are talking to is the one of the current year, and beestation pretends the patrol ship they're getting a call from is in their time.

Otherwise the entire "people talk to eachother like they know eachother", which obviously happens, makes zero sense (besides the whole thing about there not being any known means of time travel in the scenario [Temporal Agents are not real]).

normally when someone mentions this in-game I say it's "time dilation"

@Pockets-byte
Copy link
Contributor Author

changed it to something a little more vague

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants