Improving The Impromptu or How To Make Gamedays Great Again
There's been a lot of discussion about how tests are done in the steam chat, and there are disagreements on whether Impromptu tests should be run the current way or the "old-school" way.
With that in mind I would like to list all the methods of testing available and suggest how I think things could work, as well as inviting discussion on the issue.
Methods of Testing
Current "Bot" Impromptus
People submit their maps to the bot, the maps are played in first-come-first-serve order, ensuring anyone can get testing.
Downsides:
- The queue builds up faster than it can be played, queuing a map when you are available could see the map being played days later while you're busy
- Without the mapper there, discussion about the map quickly goes off course
Old-style Impromptus
The maps of those present are played, ensuring there can be actual discussion about the maps.
Downsides:
- Some people need testing but aren't available during tests
- Can sometimes be hard to source maps to host one
Gameday
Formerly the more "open" form of test to people who could not be around to imp, this method is now somewhat obselete in the face of the easy-access bot, but is still filled first-come-first-served the same way.
Downsides:
- Hard to get a map in if you aren't around when the thread goes up
- The more focused testing doesn't necessarily go to the maps that could use it
The Proposal
So here's the suggestion that's been floating around in the chat but being buried line-by-line in the discussion, up where everyone can read and criticise it:
Step 1. Split Impromptus into Old- and New- style Impromptus (and probably rename one)
Each style serves a specific purpose, and eliminating one in the face of the other was arguably unnecessary and isn't ideal for some people but, likewise, the new style definitely makes testing more accessible and is a necessity in the current era of mapping.
I propose alternating impromptus based on demand between working the list and playing the maps of people who are available. This way, people who can wait can wait, people who can't don't have to.
Step 2. Rework Gamedays
The purpose of a gameday in the past was to allow testing for people who were unable to attend imps. As feedback in gamedays improved compared to impromptus, and as the bot replaced gamedays as the accessible test, the gameday's primary purpose has become the scheduled, "event" nature, and the more focused testing. With the first-come-first-served system the maps that could make best use of the testing don't necessarily make it in.
I propose letting gameday hosts pick the submitted maps based on which maps they think could make the best use of the testing, whether it be because the map has potential or because the mapper is attending. This wouldn't come at the cost of accessibility as the bot is always available, and instead would make Gamedays more of an event and something for mappers to aim for.
As stated above, the purpose of this thread is to provide a full explanation of the issue and its proposed resolutions, and to allow discussion and criticism that wouldn't be possible through me just trying to explain it in steam chat.
There's been a lot of discussion about how tests are done in the steam chat, and there are disagreements on whether Impromptu tests should be run the current way or the "old-school" way.
With that in mind I would like to list all the methods of testing available and suggest how I think things could work, as well as inviting discussion on the issue.
Methods of Testing
Current "Bot" Impromptus
People submit their maps to the bot, the maps are played in first-come-first-serve order, ensuring anyone can get testing.
Downsides:
- The queue builds up faster than it can be played, queuing a map when you are available could see the map being played days later while you're busy
- Without the mapper there, discussion about the map quickly goes off course
Old-style Impromptus
The maps of those present are played, ensuring there can be actual discussion about the maps.
Downsides:
- Some people need testing but aren't available during tests
- Can sometimes be hard to source maps to host one
Gameday
Formerly the more "open" form of test to people who could not be around to imp, this method is now somewhat obselete in the face of the easy-access bot, but is still filled first-come-first-served the same way.
Downsides:
- Hard to get a map in if you aren't around when the thread goes up
- The more focused testing doesn't necessarily go to the maps that could use it
The Proposal
So here's the suggestion that's been floating around in the chat but being buried line-by-line in the discussion, up where everyone can read and criticise it:
Step 1. Split Impromptus into Old- and New- style Impromptus (and probably rename one)
Each style serves a specific purpose, and eliminating one in the face of the other was arguably unnecessary and isn't ideal for some people but, likewise, the new style definitely makes testing more accessible and is a necessity in the current era of mapping.
I propose alternating impromptus based on demand between working the list and playing the maps of people who are available. This way, people who can wait can wait, people who can't don't have to.
Step 2. Rework Gamedays
The purpose of a gameday in the past was to allow testing for people who were unable to attend imps. As feedback in gamedays improved compared to impromptus, and as the bot replaced gamedays as the accessible test, the gameday's primary purpose has become the scheduled, "event" nature, and the more focused testing. With the first-come-first-served system the maps that could make best use of the testing don't necessarily make it in.
I propose letting gameday hosts pick the submitted maps based on which maps they think could make the best use of the testing, whether it be because the map has potential or because the mapper is attending. This wouldn't come at the cost of accessibility as the bot is always available, and instead would make Gamedays more of an event and something for mappers to aim for.
As stated above, the purpose of this thread is to provide a full explanation of the issue and its proposed resolutions, and to allow discussion and criticism that wouldn't be possible through me just trying to explain it in steam chat.
Last edited: