Grow Battles - What Do We Need to Fix or Change?

[bakEQuatorial]

Here's what i find confusing: If our first round fails, rules on second round inclusion for participation never have been clear. Am I nixed from competing in another grow battle in general or from that vendor for having had failed my first round, or can I at least keep participating with the seeds remaining (or if i had germinated all seeds buy my own seeds eligible for that competition and continue as a non-competing participant in the other legs to maintain my gladiator badge).
How should I handle extra seeds sent for competition, should I grow them, or hold them until such a time as the next round comes along so I can participate in the next competition?
Would Vendors, staff and fellow gladiators allow those whose attempts did not pass the finish line and need to start a new plant asap due to legitimate reasons to do so using the competition seeds as long as they are documented properly here on AFN and then be allowed to be included in equal consideration for next years growing rounds/growoffs/etcs and retain their gladiator badge?

The deadlines on some of the legs of the grow battles are a bit tight if you're running a super long strain like some that are ultra long flower strains (a la auto ultimate and my one dreamberry).

I have seen it where who enters one battle, enters multiple battles and wins multiple battles using the same picture. I never understood why there was no rule requiring different pictures to be entered into different battles. Like if you are in a grow off and a lighting battle, you shouldnt be able to use the same pictures.

Like if you're going the KISS route, i understand multiple pictures, but is it possible to allow a forum user to only win one battle and not multiple, like if they win a light battle and a grow battle, they have to choose and then 2-4 move to 1-3 on the battle they conceded in. I think that allows more inclusion of people as it will allow more newbies to enter grow battles because it will feel less scary.

Plus, the name grow "Battle" Is scary to a lot. I know I hate being compared, and I always know I'll lose. Last time I voted in the battles it was a bit iffy feeling for me, but i think things can change... HOWEVER, here is a scary issue... It is currently possible to make zombie accounts which appear as live people and vote anyone you want to win (if you wish I can show you). There has to be some way to fight this through a verification method of voting rights with those who vote required to have a certain posting count or a ranking weight with less than 100 posts based upon their content strength value. Such a plugin could be developed to simply take the user, evaluate the overall data of the user's posts, then add weight based upon who quotes them, who they are replying to, what words are and are not said, in what sentence structure etc. Such a structured system could be achieved with a simple and quick auth script.
So basically i believe voting itself should require multi factor authentication.

To properly manage battles you will need to write a custom module that basically does the following: It will allow each admin to create a battle group. it will then allow the admin to fill in the battle sponsor, the battle subgroup(s), the battle subgroup leader, then the battle subgroup members. The forum also has basic details such as the Strain info provided by the company and their rules for the grow, start date, end date, and the code used for the run and when the grow battle will be announced.. After the leaders are selected in the admin module, a new topic announcing the grow battle is automatically generated by the system giving all details that were entered into the forum and then put either directly online, or into a queue to be published at a later date when the grow battle is to be announced. If the users are not announced at the time of the grow battle, the admin (or the subgroup leader) can go into the battle management section and then either add members, remove them, or message all of them, or one at once as the list is available. They can also see the last few posts by each of their group members in their individual battle threads. Once this list is completed the battle leader can lock the list. Once the list is locked, a time can be set for another auto generated set of topics to be generated and published by the system under the names of each user who is part of that grow battle allowing them all to have the exact same format for their topic. Since the system generated and published the growers grow battle topics, the system has access to all the information needed to fill in the grow battle leader's management field. The management module can then alert the grow battle leader on x number of updates to the grow battle so there are less updates to scroll through on the home page. The system can also pick up on images that are published, so when an image is published by the user, the grow battle leader can simply click to reveal the latest post with the photo and then go over to the account update window and check off that the update for grower x is complete for that day. When the grow battle leader checks off this box, an auto generated post is added to the first post announcing the grow battle's start date and information

I've always thought that 1 plant for 1 battle? You mean I could've joined 6 battles with one plant, instead of the 6? That don't sound right. But then, I've only had 2 legs worth of experience so I might not know any better.

 

[Son of Hobbes]

How about breaking battles into groups, then under each group do a common thread?

Could you clarify breaking them into groups? Right now the communal/common thread is the current norm, no?

 

[St. Tom]

Hi mate, I'm not a big fan of the 6 month battle time, it makes some sense for photo battles, but as we are mostly Autoflower growers it makes more sense to me, to go back to the old way of 3 battles a year, 2 first legs and a final. That way we can pretty much go straight from one grow (battle) to the next without having to wait a few months for the next one

I agree with you on this but some people take longer than 12 weeks on a single grow thread i think it was changed to give people more time but i much prefered the older setup

 

[St. Tom]

I've always thought that 1 plant for 1 battle? You mean I could've joined 6 battles with one plant, instead of the 6? That don't sound right. But then, I've only had 2 legs worth of experience so I might not know any better.

Thats correct mate one battle one plant but the light or led battle i think you could use the same plant long as its posted in weekly updates as thats why i used to run 4 differant strains at a time like you

 

[pop22]

I agree with the concept of a minimum post rule. However, weighting is just over complicating things. With the minimum post rule, it would be easy enough for us the take a quick look at a voters profile and see if their posts were fluff or not, and if they were, report them. Could also flag votes if there were multiple votes from members with only a certain number of posts.

We're not judging these "battles" nor the voters for the content or the ranking of members. We're providing free publicity for the seed companies. We get free seeds, the companies get to evaluate their genetics in the hands of a broad range of growers and skills, across a wide physical area and in multiple environments and styles. I enter these as an opportunity to grow new strains and to input any useful information I can provide. I could care less if I "win" or not. My jars of bud are my prize. If this were truly a competition then there should/would have prizes at the end of each round!

Here's what i find confusing: If our first round fails, rules on second round inclusion for participation never have been clear. Am I nixed from competing in another grow battle in general or from that vendor for having had failed my first round, or can I at least keep participating with the seeds remaining (or if i had germinated all seeds buy my own seeds eligible for that competition and continue as a non-competing participant in the other legs to maintain my gladiator badge).
How should I handle extra seeds sent for competition, should I grow them, or hold them until such a time as the next round comes along so I can participate in the next competition?
Would Vendors, staff and fellow gladiators allow those whose attempts did not pass the finish line and need to start a new plant asap due to legitimate reasons to do so using the competition seeds as long as they are documented properly here on AFN and then be allowed to be included in equal consideration for next years growing rounds/growoffs/etcs and retain their gladiator badge?

The deadlines on some of the legs of the grow battles are a bit tight if you're running a super long strain like some that are ultra long flower strains (a la auto ultimate and my one dreamberry).

I have seen it where who enters one battle, enters multiple battles and wins multiple battles using the same picture. I never understood why there was no rule requiring different pictures to be entered into different battles. Like if you are in a grow off and a lighting battle, you shouldnt be able to use the same pictures.

Like if you're going the KISS route, i understand multiple pictures, but is it possible to allow a forum user to only win one battle and not multiple, like if they win a light battle and a grow battle, they have to choose and then 2-4 move to 1-3 on the battle they conceded in. I think that allows more inclusion of people as it will allow more newbies to enter grow battles because it will feel less scary.

Plus, the name grow "Battle" Is scary to a lot. I know I hate being compared, and I always know I'll lose. Last time I voted in the battles it was a bit iffy feeling for me, but i think things can change... HOWEVER, here is a scary issue... It is currently possible to make zombie accounts which appear as live people and vote anyone you want to win (if you wish I can show you). There has to be some way to fight this through a verification method of voting rights with those who vote required to have a certain posting count or a ranking weight with less than 100 posts based upon their content strength value. Such a plugin could be developed to simply take the user, evaluate the overall data of the user's posts, then add weight based upon who quotes them, who they are replying to, what words are and are not said, in what sentence structure etc. Such a structured system could be achieved with a simple and quick auth script.
So basically i believe voting itself should require multi factor authentication.

To properly manage battles you will need to write a custom module that basically does the following: It will allow each admin to create a battle group. it will then allow the admin to fill in the battle sponsor, the battle subgroup(s), the battle subgroup leader, then the battle subgroup members. The forum also has basic details such as the Strain info provided by the company and their rules for the grow, start date, end date, and the code used for the run and when the grow battle will be announced.. After the leaders are selected in the admin module, a new topic announcing the grow battle is automatically generated by the system giving all details that were entered into the forum and then put either directly online, or into a queue to be published at a later date when the grow battle is to be announced. If the users are not announced at the time of the grow battle, the admin (or the subgroup leader) can go into the battle management section and then either add members, remove them, or message all of them, or one at once as the list is available. They can also see the last few posts by each of their group members in their individual battle threads. Once this list is completed the battle leader can lock the list. Once the list is locked, a time can be set for another auto generated set of topics to be generated and published by the system under the names of each user who is part of that grow battle allowing them all to have the exact same format for their topic. Since the system generated and published the growers grow battle topics, the system has access to all the information needed to fill in the grow battle leader's management field. The management module can then alert the grow battle leader on x number of updates to the grow battle so there are less updates to scroll through on the home page. The system can also pick up on images that are published, so when an image is published by the user, the grow battle leader can simply click to reveal the latest post with the photo and then go over to the account update window and check off that the update for grower x is complete for that day. When the grow battle leader checks off this box, an auto generated post is added to the first post announcing the grow battle's start date and information

 

[St. Tom]

Here's what i find confusing: If our first round fails, rules on second round inclusion for participation never have been clear. Am I nixed from competing in another grow battle in general or from that vendor for having had failed my first round, or can I at least keep participating with the seeds remaining (or if i had germinated all seeds buy my own seeds eligible for that competition and continue as a non-competing participant in the other legs to maintain my gladiator badge).
How should I handle extra seeds sent for competition, should I grow them, or hold them until such a time as the next round comes along so I can participate in the next competition?
Would Vendors, staff and fellow gladiators allow those whose attempts did not pass the finish line and need to start a new plant asap due to legitimate reasons to do so using the competition seeds as long as they are documented properly here on AFN and then be allowed to be included in equal consideration for next years growing rounds/growoffs/etcs and retain their gladiator badge?

The deadlines on some of the legs of the grow battles are a bit tight if you're running a super long strain like some that are ultra long flower strains (a la auto ultimate and my one dreamberry).

I have seen it where who enters one battle, enters multiple battles and wins multiple battles using the same picture. I never understood why there was no rule requiring different pictures to be entered into different battles. Like if you are in a grow off and a lighting battle, you shouldnt be able to use the same pictures.

Like if you're going the KISS route, i understand multiple pictures, but is it possible to allow a forum user to only win one battle and not multiple, like if they win a light battle and a grow battle, they have to choose and then 2-4 move to 1-3 on the battle they conceded in. I think that allows more inclusion of people as it will allow more newbies to enter grow battles because it will feel less scary.

Plus, the name grow "Battle" Is scary to a lot. I know I hate being compared, and I always know I'll lose. Last time I voted in the battles it was a bit iffy feeling for me, but i think things can change... HOWEVER, here is a scary issue... It is currently possible to make zombie accounts which appear as live people and vote anyone you want to win (if you wish I can show you). There has to be some way to fight this through a verification method of voting rights with those who vote required to have a certain posting count or a ranking weight with less than 100 posts based upon their content strength value. Such a plugin could be developed to simply take the user, evaluate the overall data of the user's posts, then add weight based upon who quotes them, who they are replying to, what words are and are not said, in what sentence structure etc. Such a structured system could be achieved with a simple and quick auth script.
So basically i believe voting itself should require multi factor authentication.

To properly manage battles you will need to write a custom module that basically does the following: It will allow each admin to create a battle group. it will then allow the admin to fill in the battle sponsor, the battle subgroup(s), the battle subgroup leader, then the battle subgroup members. The forum also has basic details such as the Strain info provided by the company and their rules for the grow, start date, end date, and the code used for the run and when the grow battle will be announced.. After the leaders are selected in the admin module, a new topic announcing the grow battle is automatically generated by the system giving all details that were entered into the forum and then put either directly online, or into a queue to be published at a later date when the grow battle is to be announced. If the users are not announced at the time of the grow battle, the admin (or the subgroup leader) can go into the battle management section and then either add members, remove them, or message all of them, or one at once as the list is available. They can also see the last few posts by each of their group members in their individual battle threads. Once this list is completed the battle leader can lock the list. Once the list is locked, a time can be set for another auto generated set of topics to be generated and published by the system under the names of each user who is part of that grow battle allowing them all to have the exact same format for their topic. Since the system generated and published the growers grow battle topics, the system has access to all the information needed to fill in the grow battle leader's management field. The management module can then alert the grow battle leader on x number of updates to the grow battle so there are less updates to scroll through on the home page. The system can also pick up on images that are published, so when an image is published by the user, the grow battle leader can simply click to reveal the latest post with the photo and then go over to the account update window and check off that the update for grower x is complete for that day. When the grow battle leader checks off this box, an auto generated post is added to the first post announcing the grow battle's start date and information
[EDIT]You could also have such a system so that each individual grower submits their pics through such a module and then their pics are also automatically submitted via the system to the main thread and then the grow battle leader gets an actual time of arrival for the photograph and its instantly uploaded for them to check out without wading through pages of threads[/EDIT/]

1 battle one plant and we have ip software so people cant do multiple votes with new accounts they would be banned but we rely on peoples honesty

 

[Son of Hobbes]

To properly manage battles you will need to write a custom module that basically does the following: It will allow each admin to create a battle group. it will then allow the admin to fill in the battle sponsor, the battle subgroup(s), the battle subgroup leader, then the battle subgroup members.

The forum also has basic details such as the Strain info provided by the company and their rules for the grow, start date, end date, and the code used for the run and when the grow battle will be announced.. After the leaders are selected in the admin module, a new topic announcing the grow battle is automatically generated by the system giving all details that were entered into the forum and then put either directly online, or into a queue to be published at a later date when the grow battle is to be announced.

If the users are not announced at the time of the grow battle, the admin (or the subgroup leader) can go into the battle management section and then either add members, remove them, or message all of them, or one at once as the list is available. They can also see the last few posts by each of their group members in their individual battle threads.

Once this list is completed the battle leader can lock the list. Once the list is locked, a time can be set for another auto generated set of topics to be generated and published by the system under the names of each user who is part of that grow battle allowing them all to have the exact same format for their topic. Since the system generated and published the growers grow battle topics, the system has access to all the information needed to fill in the grow battle leader's management field.

The management module can then alert the grow battle leader on x number of updates to the grow battle so there are less updates to scroll through on the home page. The system can also pick up on images that are published, so when an image is published by the user, the grow battle leader can simply click to reveal the latest post with the photo and then go over to the account update window and check off that the update for grower x is complete for that day. When the grow battle leader checks off this box, an auto generated post is added to the first post announcing the grow battle's start date and information

Both the initial cost of such development or the means to support it (especially bug fixes, etc) would likely be our biggest obstacle with this. We just don't have the money some people think we do (I run AFN from my kitchen table if that helps put this into perspective lol...)

We've explored a few different options, including a 'tournament' software:

It just didn't really pick up any steam though.

It had some convenient options in it though:

The problem though is that it still creates a thread (like we've always done,) which still creates the jumbled thread.

We have a Threadmarks add-on that allows posts to be "marked", then those threadmarks can be built into an index. You can also view JUST threadmarks in a thread, so if all updates were properly marked, technically you could still have all comments (from both particpant and non,) but if you JUST wanted to read the updates? Click, click, done.

Another option we kicked around was the use of Forms, which would require participants to click a link to an update form (that would look just like this text box,) that would automatically post the update in a thread of our choosing.

Few options are particularly "sleek and sexy" though in terms of presentation.

 

[pop22]

That would be fine if the actual battle thread remained there instead of the main battle thread. It's that all in one thread that's the core of the problem here. Then break growers down into groups of 4 say. so Under the main title od, say, Female Seeds Grow Battle 2020 Leg One, you could have a sign up thread, then, threads for Group!, Group2, etc

Could you clarify breaking them into groups? Right now the communal/common thread is the current norm, no?

View attachment 1196657

 

[The Dalai Farmer]

I agree with you on this but some people take longer than 12 weeks on a single grow thread i think it was changed to give people more time but i much prefered the older setup

I hear what you saying, but it's very rare for an auto to take 4 months and if someone does pick a long finishing one then it's there own fault and sod em

 

[St. Tom]

Both the initial cost of such development or the means to support it (especially bug fixes, etc) would likely be our biggest obstacle with this. We just don't have the money some people think we do (I run AFN from my kitchen table if that helps put this into perspective lol...)

We've explored a few different options, including a 'tournament' software:

View attachment 1196666

View attachment 1196668

View attachment 1196669
View attachment 1196670

It just didn't really pick up any steam though.

View attachment 1196671

It had some convenient options in it though:
View attachment 1196672

The problem though is that it still creates a thread (like we've always done,) which still creates the jumbled thread.

We have a Threadmarks add-on that allows posts to be "marked", then those threadmarks can be built into an index. You can also view JUST threadmarks in a thread, so if all updates were properly marked, technically you could still have all comments (from both particpant and non,) but if you JUST wanted to read the updates? Click, click, done.

Another option we kicked around was the use of Forms, which would require participants to click a link to an update form (that would look just like this text box,) that would automatically post the update in a thread of our choosing.

Few options are particularly "sleek and sexy" though in terms of presentation.

Also this time around we lost way more than half of are battle staff and the holes still havent been filled sadly . and the state we are in now threadmarks are the only way to keep the relevant post or updates marked for going back to