14117
Earlier today I thought it would be interesting to see the average number of OHCs that take place per day, since this number is fortunately going up. But then an idea came into my head, and I almost forgot about it!
My idea is to create something called a "Battle Hype": a number that is displayed under the "Recent Battles" header. This number would be within some range and, after hitting a certain limit, will do something very special... Here's what the number would take into account:
• The amount of OHCs there have been recently. For a timespan I've been thinking of possibly 2 or 3 days. Maybe it could change between the two to make it more random. This is to check for a somewhat firm amount of activity on BotB.
• The frequency of OHCs. The most important determinant for the Battle Hype.
• The number of unique users in each OHC, and especially how many people are recurring in these compos. This will highlight the amount of people who both actively and occasionally participate. Thus, this determines the amount of people likely to join in this "special thing."
• A plethora of numeral statistics from each of said recent OHCs, including the average, peak, and lowest entry count. This is to confirm that there is a non-wavering interest.
• The amount of entries that have been submitted to a major compo (if occurring) in the aforementioned time span (so the position of the Battle Hype might need to be put somewhere else in the side bar...between "Call to Arms" and "Recent Battles"?). This highlights participation in a major battle. And, of course, we get a lot of people in our IRC channel during major battles, which makes including this important!
When the limit is reached, a variably-timed competition can be announced. Yes, a VHC of sorts, or VHB if you prefer!
Now, here's something I'm fishy about including: The site could make sure with the bot that there is still activity in the #botb channel and maybe there could be an implemented AI to evaluate interest in another compo. If the channel was all like "brb," "ugh I gotta sleep," or, "OHC?!" "no" this would prevent the VHC from being offered. This part of the idea could have some problems if we go with it.
If interest has been shown in the channel (if we're going to do that part), then the bot would make an announcement that the limit was reached! The bot would then, within two minutes, randomly pick a person based on his/her activity in recent compos or the channel. Compo hosts could have a higher chance, but this might turn out to be unfair. This person will receive the ability to host one VHC/VHB. He/she would have 8 hours to launch this compo until it escapes from a BotBr's hand and flies out the chimney!
I'd expect the range of a VHC to be from 30 minutes to 2 hours, in 15 minute increments. In fact, while doing pseudo-proofreading, maybe it could be set up so that the more the Battle Hype goes over the limit, a wider range is available. Yeah, that sounds nicer. I'm just too lazy to go back and edit.
This idea is plagued with questions and challenges its own practicability. Does this mean we'll need more IRC/HTTP integration? Will this really turn out to induce further participation from BotBrs as intended? Could this eventually backfire somehow with everyone hating it? Will VHCs be announced at the right time every time? We'll just have to see whether we should do this in the first place or not and see how she goes!
For those who were tl;dr about this post and hated how I went all over the place, heres the idea: OHC/major compo activity + Complex number based on said activity = Variable Hour Competition/Battle!"
I think I might gone crazy with my original idea when writing this but who cares, I'm done now. I've probably been writing this for an hour now. It's 10:25 PM here right now, and the earliest time I can remember checking the time was 9:38 PM. lol mouthful.
Ask me your questions. And please, ask me to clarify whatever you want!
My idea is to create something called a "Battle Hype": a number that is displayed under the "Recent Battles" header. This number would be within some range and, after hitting a certain limit, will do something very special... Here's what the number would take into account:
• The amount of OHCs there have been recently. For a timespan I've been thinking of possibly 2 or 3 days. Maybe it could change between the two to make it more random. This is to check for a somewhat firm amount of activity on BotB.
• The frequency of OHCs. The most important determinant for the Battle Hype.
• The number of unique users in each OHC, and especially how many people are recurring in these compos. This will highlight the amount of people who both actively and occasionally participate. Thus, this determines the amount of people likely to join in this "special thing."
• A plethora of numeral statistics from each of said recent OHCs, including the average, peak, and lowest entry count. This is to confirm that there is a non-wavering interest.
• The amount of entries that have been submitted to a major compo (if occurring) in the aforementioned time span (so the position of the Battle Hype might need to be put somewhere else in the side bar...between "Call to Arms" and "Recent Battles"?). This highlights participation in a major battle. And, of course, we get a lot of people in our IRC channel during major battles, which makes including this important!
When the limit is reached, a variably-timed competition can be announced. Yes, a VHC of sorts, or VHB if you prefer!
Now, here's something I'm fishy about including: The site could make sure with the bot that there is still activity in the #botb channel and maybe there could be an implemented AI to evaluate interest in another compo. If the channel was all like "brb," "ugh I gotta sleep," or, "OHC?!" "no" this would prevent the VHC from being offered. This part of the idea could have some problems if we go with it.
If interest has been shown in the channel (if we're going to do that part), then the bot would make an announcement that the limit was reached! The bot would then, within two minutes, randomly pick a person based on his/her activity in recent compos or the channel. Compo hosts could have a higher chance, but this might turn out to be unfair. This person will receive the ability to host one VHC/VHB. He/she would have 8 hours to launch this compo until it escapes from a BotBr's hand and flies out the chimney!
I'd expect the range of a VHC to be from 30 minutes to 2 hours, in 15 minute increments. In fact, while doing pseudo-proofreading, maybe it could be set up so that the more the Battle Hype goes over the limit, a wider range is available. Yeah, that sounds nicer. I'm just too lazy to go back and edit.
This idea is plagued with questions and challenges its own practicability. Does this mean we'll need more IRC/HTTP integration? Will this really turn out to induce further participation from BotBrs as intended? Could this eventually backfire somehow with everyone hating it? Will VHCs be announced at the right time every time? We'll just have to see whether we should do this in the first place or not and see how she goes!
For those who were tl;dr about this post and hated how I went all over the place, heres the idea: OHC/major compo activity + Complex number based on said activity = Variable Hour Competition/Battle!"
I think I might gone crazy with my original idea when writing this but who cares, I'm done now. I've probably been writing this for an hour now. It's 10:25 PM here right now, and the earliest time I can remember checking the time was 9:38 PM. lol mouthful.
Ask me your questions. And please, ask me to clarify whatever you want!
