Ticket #32 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

!setspec

Reported by: Left_Eye Assigned to: dugwyler
Priority: low Component: Bots - TWBot
Version: Latest version from repository Severity: minor
Keywords: Cc:

Description

To whoever it may concern:

I recommend that the command /!setspec # would be added to the standard module in the TWBots or such. This command would spec that freq desired as # to be put in spec, but on that freq in which they are currently on. For example, it would be useful in randoming everyone into spec onto two freqs. The players would enter. Hosts would do /!teams 2, then /!setspec 0 and /!setspec 1. Those players would then be ready to play. It's a lot faster than doing /*setfreq 0 and /*setfreq 1 to to everyone in the arena to random.

Attachments

Change History

02/11/07 10:44:50 changed by Maverick

Addition to Left_Eye explanation;
She wants the command to be !setspec <freq nr.> to choose which freq to change to spectator.

03/20/07 05:11:08 changed by dugwyler

  • owner set to dugwyler.
  • priority set to low.
  • status changed from new to assigned.
  • severity changed from major to minor.

Could use input here.

I've implemented this, though changed the name of the cmd to be more intelligible (!specfreq). Also implemented !specallkeepfreqs (which specs everyone but keeps their frequency) and the metacmd !teamsspec, which makes a certain number of teams and then specs everyone while maintaining frequency.

However, I'm thinking: what good is any of this? Even if they're in spec on a particular frequency, they'll generally be set to a random frequency when they enter. This makes the whole process essentially useless —

Unless this is a somewhat more complex project, and Lefty wishes the bot to record each player's ship when they are spec'd with one of these special commands, so that after issuing some sort of cmd like !unspecall (or !unspecfreq for a specific freq), the bot will do a *setship and *setfreq on everyone it has information on, returning teams to pre-spec state?

This wouldn't be hard to do, but then again, this functionality isn't what's requested.

04/09/07 12:09:52 changed by dugwyler

  • status changed from assigned to closed.
  • resolution set to fixed.

This one should be all set. I did end up implementing the restoring feature because it wasn't too much trouble.

Add/Change #32 (!setspec)




Change Properties
Action