search

Aurorastation / Aurora.3

The code for Aurorastation's new base, forked from Baystation12.
http://aurorastation.org/
GNU Affero General Public License v3.0
149 stars 518 forks source link

[Bug]: All-in-one tcomms weirdness on shuttles #19926

Open hazelrat opened 1 month ago

hazelrat commented 1 month ago

Checks

Location

Third party ship

Describe the issue

Sticking this here for posterity. If you put an all-in-one telecommunications server on a shuttle-based offship (Izharshan Shuttle, Lone Spacer), you will only be able to use your headset if you clear every filtering frequency from the server with a multitool. I assume this is an issue with how tcomms is coded in relation to ship areas.

How to reproduce

  1. Join either the Izharshan or Lone Spacer ghostrole.
  2. Try to use your headset. It won't appear to work.
  3. Take a multitool and delete every filtering frequency from the server.
  4. Use your headset again, and it will work.

Round ID

No response

Staff ckey

No response

FabianK3 commented 1 week ago

Joining the posterity, i think the AIO tcomms are also responsible for the occasional utter breakdown of communications on the Horizon. I experienced a couple of times that suddenly tcomms on the ship completely break without any change to the onboard equipment. The last time i spoke with another player that mentioned they turned on a AIO tcomms on a relic, which fits my own previous experience. Completely reconfiguring/restarting/ahelp the tcomms machines don't fix the issue, i suspect the AIO is responsible as well here. The difference to the mentioned original issue here is, that the standard Horizon frequencies had been added after step 3. 👾