brazilofmux
commented
9 years ago Comment #1 originally posted by brazilofmux on 2006-12-29T16:27:05.000Z:
This isn't related to the update from 2.6.0.12 to 2.6.1.19. TinyMUX 2.4 works the same way.
Use '@list guests' and see the current set of guests the server has created. Guests are recycled as needed separately. They are added to the guest channel once. By default, the server keeps one guest (i.e., Guest1) around. Guest2 and higher are destroyed during @dbck. So, if you're testing with Guest1, you would not ever see it added to the Guests channel, but if you're testing with Guest2, you would sometimes see it added (as long as there is an intervening @dbck).
To solve your problem, you can setup an @aconnect that tests for the guest @power and makes a @cemit on the Guests channel.
Original issue 242 created by brazilofmux on 2006-12-29T16:03:22.000Z:
Recently Gamma One was running 2.6.0.12, and I patched up, all at once, to 2.6.1.19, recompiled and @restarted the game. For a long time before the upgrade we had a Guests channel which had been set '@cset/loud Guests'. After the upgrade the connect message is not being displayed for Guests. For other players it works fine.
The channel is 'Guests'. The conf file has 'guests_channel Guests'. Guests should be part of the Guests channel automatically. However, it seems like they're being added too late to trigger the channel connect/loud message.
I've tried doing '@cset/mute Guests' and then '@cset/loud Guests' to 'reset' the settings. I've logged into the guest and delcom'd the guest channel and reconnected. I'm still seeing the same problem.