Editing Talk:Glossary
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The system administrator who locked it offered this explanation: We are currently working on upgrading comp.tf. Edits will be locked for most of March 2025, or until further notice. For questions, please contact staff on the comp.tf Discord. I apologise for the inconvenience.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page is not enabled for semantic in-text annotations due to namespace restrictions. Details about how to enable the namespace can be found on the configuration help page.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | Would it be better to put the words in alphabetical order? | |
| − | + | ||
| − | + | ||
| − | + | Let's go with alphabetical until we have everything, then if it's too intimidating we can split things into groups. -Koobadoobs | |
| − | + | ||
| + | |||
| + | This will be impossible to do alphabetically, I say we split into groups such as combat (Lit, buffed, ubered, etc), map (Mid, generic names like flank and choke, generic naming schemes like at process last), and meta (Advantage, forward spawns, class makeups for teams). If we wait until we have 50+ terms, it will be really hard to sort. - Waldo | ||
