|
Post by Rajiv on Feb 10, 2013 19:00:19 GMT 8
Done. Excluding the "Stand-Alone Polls" sub-board and the "General Information" thread, there are a total of 26 threads on the Discussion board covering all matters relating to our games. Although there is some degree of overlap between threads, wherever this is the case, the threads cover different aspects of an issue. I do not envisage the need for anymore threads. Threads on the "Stand-Alone Poll" sub-board should relate to our games, and include a poll on an issue. The most recent polls relate to the use of Sports Planet @ East Coast. Threads on the "Chat" board can be about anything. There are separate report boards under the categories of GIFFA-Defined Games and OPSAGE.
|
|
|
Post by Rajiv on Mar 24, 2013 9:26:52 GMT 8
|
|
|
Post by Rajiv on May 27, 2013 10:22:01 GMT 8
I've been keeping a record of the number of games each week on roughly a monthly basis on the "Scheduling & game per week/month" thread since November 2012, dating back to the end of September 2012. Previously, I did so on the "Days, time & locations" thread, dating back to 20 February 2012, and starting with just weeknight games. However, summarizing the weekly situation at the end of the month means having to trawl through the month's games at the end of each month. To make it easier for myself, I've started a weekly round up thread on the "Chat" board, for May 2013, starting with the week from 4 to 9 May 2013. Having a separate thread allows me to break down the work into weekly bits, and also allows me to add a bit more detail. The summary at the end of each month will still be on the the "Scheduling & game per week/month" thread.
|
|
|
Post by Rajiv on Jul 4, 2013 21:34:02 GMT 8
Each week, there is one post. I don't actually need a monthly thread. I will have a half-yearly thread from now on, so approximately 26 weeks. .... The summary at the end of each month will still be on the the "Scheduling & game per week/month" thread. Since early October 2011, I have been locking the schedule thread once the report thread is up. From now on, when I do the weekly round-up post, I will lock the report threads for the previous week's games.
|
|
|
Post by Rajiv on Oct 25, 2013 9:26:26 GMT 8
|
|
|
Post by Rajiv on Jan 25, 2014 16:09:48 GMT 8
From above: Each week, there is one post. I don't actually need a monthly thread. I will have a half-yearly thread from now on, so approximately 26 weeks. .... The summary at the end of each month will still be on the the "Scheduling & game per week/month" thread. Since early October 2011, I have been locking the schedule thread once the report thread is up. From now on, when I do the weekly round-up post, I will lock the report threads for the previous week's games. The weekly round ups for the second half of 2013 have been completed. I will lock the thread at the end of the month. As I've been busy, the weekly round up has often been posted a few weeks later, with the unintended consequence that players have had more time to add comments on the report thread. From now on, to allow players more time to comment on individual games, I will wait at least two weeks before I lock the report thread, even if I do the round up sooner. I will put up the thread for the first half of 2014 on the "Weekly Round Up & Team Selectors Table" board in a short while.
|
|
|
Post by Rajiv on Feb 19, 2014 20:07:41 GMT 8
From "The Message board & modes of communication" thread: .... .... Announcements and discussions will be dealt with generally under this thread, or under the specific subject matter thread on this board. Stand-alone polls and chat will continue to be dealt with generally under the "Reports, discussion, chat & polls" thread, which will be renamed as "Reports, polls & chat". Specific polls will be dealt with under the particular subject matter thread. Apart from OPSAGE, reports, polls and chat are the features of this message board where players can be more involved. .... This thread has been renamed accordingly. Also from the same post on "The message board & modes of communication" thread: .... I used to create new threads to discuss various broad issues that arose in our games. Over time, these threads were modified and merged until they were consolidated into the current 26 subject matters by March 2012. Since then, there have only been minor modifications of the scope of particular threads, such as that described above. The changes over time are captured by posts within the thread. However, given the way each thread was started and modified, the first post of each deals with some aspect of our game which may be only partially related to the current subject matter of the thread. I will therefore replace the first post of each thread with the following: Polls were added to some of the threads. Some of the polls have been lost through thread mergers. There were four remaining polls. Although the polls appear at the top of the thread, they relate to a limited and/or obsolete issue within the thread. Under ProBoards v5, polls can be deleted. I have archived three of the four polls as screen images below, and deleted the polls. The remaining poll was one created by Rai, and which led to the change of our team colours from white and black to white and red (which previously was only used for the weekend games at The Grandstand). The thread had been continued by me to cover standardization of equipment generally. Rather than delete the poll, I wanted to move it to the "Stand-Alone Polls" board, but I could only do that by moving the entire thread, so I did that, moved the post relating to standardization of equipment generally to a new thread on the "Overview, Announcements & Discussions" board, with the subject matter "Standardizing equipment" as before, and renaming the moved thread on the "Stand-Along Polls" board as "Change of colour for Kit @ Sports Planet" to match the poll question. Only thing is that the "Views" of 973 for the thread belong to the moved and renamed thread, which is a very high number for what is now a relatively short thread.
|
|
|
Post by Rajiv on Mar 22, 2014 11:49:04 GMT 8
From the "Weekly schedule & number of games" thread: .... Commencing with July 2013, I have been referring to the weekly round up for the number of games per week. As we haven't had a regular Friday game up to now, the GIFFA week runs from Saturday to Thursday, as shown in each weekly and monthly summary. Up to 2009, under the old FIOFAFI blog, the weeknight games were dealt with separately from the weekend games. .... Although I went back to listing the games from Saturday to Thursday by October 2012, the listing was not included in the GIFFA System thread until much later, sometime in 2013. Even if we do finally get round to having a regular Friday game, I will add it at the end of the week, rather than switching back to a Monday to Sunday week. As weeks don't usually fall squarely within a month, when I do the monthly round up based on the weekly round up, there is usually an overrun or truncation at the the beginning or end of the period covered. Rather than continue with doing a monthly round up on this thread, from this month onwards, I will just provide a summary of each week in the weekly round up post in the weekly round up thread for each half year on the "Weekly Round Up & Team Selectors Table" board. It will also save me some amount of work at the beginning of each month. .... And from the "Keeping score & the competitive edge" thread, relating to the team selector table: .... For the first season, all the included results, the table, and all explanation, were in a single post. I had a single post for the second season as well, but by mid February, the post had become unwieldy as more results were added and the table grew bigger, so I split it into three posts - one with the table and the explanation, the second with the included results from October to December 2013, and the third with the included results from January to March 2014. Soon after, it occurred to me that by combining the listing of included results with the weekly round up, I could save myself a fair bit of work. I will do so from the next season onwards, starting from April 2014. .... Therefore, from April 2014 onwards, I will create a new thread every 6 months, one in April and one in October. The first post will contain the table and explanation. Each week, I will add a round up post below, in the following table format: As the weekly round ups will now be in sync with each season (April to September and October to March), the current weekly round up thread will be truncated from the first half of 2014 to the first quarter of 2014. I have renamed the thread accordingly. On a separate note, from "The forum & modes of communication" thread: .... I have changed the settings for the "Post-Game Reports & Comments" board so that threads remain listed by the date they were created rather than the date of the last post. This should make the report thread for any particular game easier to find. .... As report threads remain listed in the order in which they were created, and later posts won't distort the order, I will no longer be locking the report threads after two weeks.
|
|
|
Post by Rajiv on Apr 1, 2014 21:17:04 GMT 8
From the "Social dimension, and fun" thread: .... Back in November 2011, Foo Cheong and Rainer proposed a pre-game poll to allow players to indicate whether the line ups for a particular game were balanced or not. I followed up with a "Prediction Poll" sub-board, where any could vote on the possible outcome of the game, limited to the following options: - Close game.
- Comfortable win for Whites
- Comfortable win for Reds
Rainer was keen on getting it started, but there was no interest after it was started: From the earlier discussion, it was apparent that the use of a poll created difficulties. For a couple of weeks now, I have been thinking of encouraging users to predict the final score instead. This could be done as individual posts, either on the schedule thread after the line ups go up, or on the report thread, with it going up earlier, as soon as possible after the line ups go up. We could even have a prediction table to complement the team selector/captain table. I have considered awarding points as follows: - 4 points for correctly predicting the result and the exact scoreline.
- 3 points for correctly predicting the margin or being one goal off from the correct scoreline.
- 2 points for correctly predicting the result, but the wrong scoreline.
- 1 point for participating.
If a user's prediction falls into more than one category, it will be awarded points from the highest category only. Only one prediction will be allowed per user per game. Like the team selector/captain table, it will be weighted to take into account that users will have predicted different number of games. I am prepared to give credits as a prize to the top predictor at the end of each 6 month period. To avoid a situation where a player in the game tries to influence the game towards his prediction, predictions by players in the game will be excluded from the table. Therefore, the prediction table will be for users who aren't playing in that game. It can extend to users who are not in the GIFFA Player group even. However, as non-GIFFA Players cannot post on the schedule thread, it will mean the report thread will have to go up earlier, as soon as possible after the line ups are posted. It will allow for the following: - Those who are out of our games long term, either through injury, being away from Singapore, or other commitments, can continue to be involved.
- Players who are not regulars in a particular game can become more familiar with the players in that game.
- Users who are interested in watching and discussing football, but not necessarily interested in playing, can participate.
And its all for fun anyway. .... To allow registered users who are not in the GIFFA Player group to participate, I will put up the report thread earlier on the day of the game, any time before, or when, the team selector/captain poll closes (usually 4.5 hours before the game). Once the line ups are settled, any registered user can predict the result. Those who are in GIFFA Player group can do so either on the schedule thread or the report thread. Those who are not in the GIFFA Player group can do so on the report thread. Only make one prediction, any time up to the start of the game. You can change it anytime before the game starts by editing the post. If you change it after the the game starts, the prediction is not valid. If you make more than one prediction, the later or the last will be the only valid prediction. Report threads will from on be referred to as "predictions & report threads", "predictions threads" or "report threads", depending on the context, and the name of the board will be changed from "Post-Game Reports & Comments" to "Pre-Game Predictions & Post-Game Reports/Comments". From the "Weekly schedule & number of games" thread: From above: .... I have also added colour-coded labels to the subject for each schedule thread from yesterday's game onwards. The label appears at the start of the subject, and the colours are:
- The Grandstand - Red
- Balestier Road - Green
- East Coast - Blue
- Kallang - Purple
If you click on a label on the listing of threads on the schedule board, only games at that venue will be listed. .... From the schedule thread for the game on 1 April 2014 (Tuesday at Kallang) onwards, I have added the following labels: - WD-N / WE-E / WE-N / PH-E - Part of the week/day, as follows: Weekday ("WD", Monday to Friday), weekend ("WE", Saturday or Sunday) or public holiday ("PE"), and evening ("-E", 4 to 8 pm) or night ("-N", 8 to midnight). So far, we've only had games between 4 to 7 pm (currently only 5 to 6 pm) and 8 and 10 pm (currently only 9 to 10 pm). The label for evening games are in red. Anyway, I see Sunday night in the same way as I do weekday night games. If a regular night game is scheduled on a weekday that is also a public holiday, I will use "WD-N", not "PH-E". If we ever get round to having morning games, I will create new labels.
- Saturday / Sunday / Monday / Tuesday / Wednesday / Thursday / Friday - Day of the week. Saturday and Sunday are in red. So far, we haven't had a game on Friday other than a public holiday.
As I am now using red for evening games and for Saturday and Sunday, I have changed the colour for The Grandstand to brown. To shorten the labels, I have dropped "The" before "Grandstand", as well as "Road" after "Balestier". As the labels appear in alphabetical order, I have added (a) for labels for part of the week/day, (b) for days of the week, and (c) for area/location, so that they appear in that order. By clicking on a label, the threads on the schedule board can be listed by that value. Unfortunately, I am informed that you can't see the labels of your device's browser is on "mobile view". You need to have it on "desktop view" to see the labels. Also from the post above: .... I have changed the subject format to "[Day of week], [Date], [Session start time], [Venue] @ [Area]". Previously, the last part was [Area] ([Venue]). The day of week is the first 3 letters of the day. The date is in D Mmm YYYY format. The session start time includes the 10 minutes before the start of the game. As ProBoards v5 allows more letters in a subject, I have, since the move to v5 in January 2014, expanded the abbreviated venue names. Our regular venue names are now as follows: - Prem Pitch (C) - Premier Pitch's covered pitch at The Grandstand.
- Premier Pitch - Premier Pitch at Balestier Road.
- Sports Planet - At East Coast.
- The Cage - In Kallang.
.... So as not to duplicate information in the subject, the subject for each schedule thread will be [Date], [Session start time], [Venue]. As area/location is no longer included, to avoid confusion between the Premier Pitch at Balestier Road and the Premier Pitch at The Grandstand, I will use the following names: - Premier Pitch (Khalsa) - Premier Pitch @ Balestier Road (on the premises of Singapore Khalsa Association).
- Premier Pitch (C) (GS) - The covered pitch at the Premier Pitch @ The Grandstand
....
I will use the same labels for the report threads. The format for the subject of each thread will be changed to [Date] - [Venue] ([Game in payment cycle]) From the "Filling places & choices" thread: The report thread is an indication of the degree of involvement of the players, especially the regulars, in that game. The Tuesday game at Kallang ( which only needs 8 players to go on) is suffering both from a small pool of players, and the lack of involvement reflected in the absence of reports - two games cancelled in three weeks (on 18 March 2014 and today).
|
|
|
Post by Rajiv on Apr 10, 2014 9:51:24 GMT 8
Further to the first part of the post above, from "The social dimension, and fun" thread: .... If, from April to September 2014, there are at least 10 players validly predicting at least 5 games each, there will be a prize for the highest placed user who has validly predicted at least 5 games. Although strictly speaking, the predictions and the prediction table are not part of the "GIFFA System", and more "OPSAGE", I will maintain the prediction table on the "Weekly Round Ups & Team Selector Table" board. For now, the thread for discussing predictions and the prediction table will be this "The social dimension, and fun" thread. .... Earlier, from the "Keeping score & the competitive edge" thread: .... .... I will rename the "Weekly Round Up & Team Selectors Table" board .... .... I have created the "Overview" post on that board. Also from the "Keeping score & the competitive edge" thread: .... .... I will add an appendix to the Overview thread to keep a record of the following (starting from this month onwards): - Lowest-scoring and highest-scoring games for each venue.
- Comebacks.
- Grossly one-sided results.
Earlier records will remain only on this thread. And from "The forum & modes of communication" thread: .... The board has been re-named "Weekly Round Ups, Tables & Game Records". .... I have changed the description of the board to: I have also re-named the report board as "Pre-Game Predictions & Post-Game Reports/Comments" and changed the description to: For the first week of this month, I was trying to put up each predictions & report thread immediately after the poll closed, or where I suggested line ups, after the line ups were finalised, quoting extensively from "The social dimension, and fun" and this thread, and adding a quote from the schedule thread as to the team selectors/captains or line ups where I suggested them, and ending with: I also added a link in the schedule thread to the predictions & report thread, explaining that with the new style, it was up early. It was unwieldy and not consistently applied. From now on, the predictions & report thread will be put up when the poll closes, or, when I suggest line ups, when the line ups are finalised, stating as follows: This was put into effect for the game last night (Wednesday night at Balestier Road). The post will be quoted back on the schedule thread, so that users can follow the link.
|
|
|
Post by Rajiv on Jul 5, 2014 10:36:07 GMT 8
From the "Weekly schedule & number of games" thread: ..., the amount of space taken by labels in the title to each thread on the schedule board is large, so if a player inadvertently clicks on one of the labels instead of the thread subject, he will get to a listing of threads by that label, instead of into the thread itself. The player can click on the thread subject he wants in the listing of threads by the label to get into the thread, but that is an extra step, and it might take him a while to figure out what happened. If he keeps clicking on a label, he will keep getting a listing by the label. To reduce the risk of players accidentally clicking on a label when they actually want to get into a thread, I will reduce the length of the labels. Days of the week will be by the first three letters (that is "Sat", "Sun", "Mon", "Tue", "Wed" and Thu") and the venue/location will be reduced to two letters, as follows: - GS: The Grandstand
- BR: Balestier Road
- EC: East Coast
- KG: Kallang
.... The labels for the predictions & report board have similarly been shortened. For browsers on mobile devices, labels remain only viewable on desktop view, not mobile view. After the changes to the subject format for the thread listing on the report board on 1 April 2014 (see the preceding post), the appearance of the thread listing on the report board is currently very similar to that of threads on the schedule board. It can cause confusion. I will change the format back to [Day], [Date] - [Venue/Location] ([Number in payment cycle]). I will backdate this to 1 July 2014. Continuing from the post above, on the "OPSAGE, women's & all-comers' game" thread: .... Apart from a player trying to predict the result of games in which he was playing ..., so far, there have only been a couple of attempts by non-players to predict the result .... It is currently more work than it is worth. I will abandon the prediction table for the rest of this GIFFA season (up to 30 September 2014). I will remove the references to the pre-game predictions and the prediction table. Players can continue to try to predict results, either on the schedule thread or the report thread (wherever the line ups appear), but that would be just for fun. The system by which I switch from the schedule thread to the report thread for a game is still not applied consistently. It is complicated by the recent trend for team selectors to post the line ups on the WhatsApp group chat only, as almost all the players are on the group chat. I only remind team selectors to post the line ups on the schedule thread if there are players who are not on WhatsApp or who have left the group chat. Where the line ups are not posted on the schedule thread, they only appear on the report thread. I will look to making the system more consistent by the start of the next season (1 October 2014). A reminder from the "Equipment" thread: The ball credit was introduced in March 2014. From the "Equipment" section of the GIFFA System thread: .... Balls are provided at the venue. However, the quality of the ball provided may vary greatly, players are encouraged to bring their own balls. Our preference is for a reduced bounce size-4 or size-5 ball, but an ordinary size-5 ball will do. If there is more than one ball available, team selectors/captains should discuss and agree on the choice of ball. If a ball brought by a player is used up to the end of a game, and it is reported on the report thread to the game, the player will receive $1 credit for the first 35 times that ball is used. .... The ball credit has only been claimed twice so far: Kelvin Au reported the use of ball both times, once brought by him, and once brought by Rai. .... ... note: - ....
- The use of the ball must be posted on the report thread to claim the $1 credit.
I'll make more of an effort to promote this.
|
|
|
Post by Rajiv on Oct 4, 2015 10:53:23 GMT 8
From earlier in ths thread: A regular who is current injured turned up to watch the game yesterday, and was the first to provide a report of the game on the message board. I have no objections in principle to giving the $2 credit for a first report to someone who isn't playing but comes down to watch the game. However, the credit is stated to be for the first player, which implies someone who plays in that game. If anyone thinks spectators should also be entitled to the $2 credit for the first report, add your views below. Unless and until there is a change in the position, spectators can still provide reports or comments, whether they are the first to do so or not, because they enjoy doing so, or just because want to. Hi Rajiv, I think it is only fair that a spectactor would get $2 credit for the first report. We are already glad that a spectactor would take the effort to show up and often they have the most insightful, balanced and often funniest reports... Well, the counter argument is that spectators get to watch good football for free, and they're so inspired by what they see they rush back to write a report.  As a spectator writes because he enjoys it, does he really need a further reward in the form of a $2 credit? The credit is ultimately a form of "rebate". As spectators don't pay, it's hard to justify a "rebate". I'll put it up as a poll on the Stand-Alone Polls sub-board anyway, to see what the majority think. .... I put up a poll on the Stand-Alone Polls board, asking if spectators should be entitled to the first report credit. As there was only four votes: We need a lot more to vote in this poll, for it to take effect. I'll give it until the end up June 2013. There are still only four votes. More recently: - Damian added a report for the game on Sunday, 12 July 2015, which he came down to watch, post-surgery. While it was not the first report, it was interesting to read a spectator's perspective.
- Over the past few months, there is often no report for the Saturday game. For the game on 12 September 2015, Rockstar, who was neither playing, nor at the game, posted in jest a generic template style "first report". That motivated Cedric, who actually played, to provide the score, adding "Credit to [Rockstar]". I shared the $2 credit between them, $1 each. The $2 first report credit would ordinarily have gone to Cedric. Although Rockstar's "first report" was a joke, I took Cedric's comment to mean he would share the credit with Rockstar.
Where a player is entitled to the $2 first report credit adds a comment from which it appears he wants to share his credit with, or transfer his credit to, anyone else, whether another player from the game, a spectator, or any other GIFFA Player, I will do so.
I will close the poll on the Stand-Alone Polls board.
And from the report thread for the game on Saturday, 26 September 2015:
Seeing as I was central to the game taking place, I think I should post the game report. Particularly as Rockstar is lurking to post another nonsense report. .... At least the "nonsense report" incentivised others, which is the main aim of the credits anyway.
Also from earlier in this thread:
.... In future, if the first report is way off, I'll give the $2 credit to the next one. For the game on Sunday, 26 July 2015, the first report provided the score as 20-3. Another player posted that the final score wasn't that bad, more like 9-3. There was no further comment or discussion on the final score, so I split the $1 credit between the two players, as I have done before.
If the report is not completely way of the mark, but the final score provided is, I will just split the credit between the first player and the one who provides the correct score.
And from the "Payments, credits, penalties & usage" thread: .... Also, there are the following post-game credits currently available: The credits are entered into the "Other Credits" section of the P&B Spreadsheet based on the date on which the first report is posted. However, if the first reported is posted after 10 pm, the following day's date is used. To simplify matters, with effect from this month onwards the credits will be recorded against the date of the game itself, no matter when the first report is put up or the ball credit claimed. However, the credits will only be given after the first report is posted. The credits are also stated in a post on the report thread itself. The credits will be posted on the report thread when the P&B Spreadsheet is updated. I started off updating the credits within a day or two of the first report being posted. However, for some time now, I have only been updating the credits at the end of each week. It saves me time. I will do so before uploading the P & B Spreadsheet, at least once a week.
|
|
|
Post by Rajiv on Oct 31, 2017 8:10:47 GMT 8
From the "GIFFA system & playing rules" thread: The "Pre-game protocol, cancellations & weather policy" section of the "GIFFA System" thread currently provides: .... For games on uncovered pitches, if there is heavy rain and/or lightning in the hour before the game is due to start, the game will be cancelled, unless it appears that the rain/lightning is easing up, and that the game can go ahead despite the wet conditions. .... The Khalsa game on Thursday, 21 July 2016, was cancelled at 9.05 pm due to heavy rain. It eased up by about 9.20 pm, but the pitch would in any event have been too waterlogged to play on. From the schedule thread: .... It only started to rain at about 8.40 pm, with several players already there or on their way, and only became heavy about 8.50 pm. As players were already there before the game was cancelled, I will include it as a game played for purposes of the number of games played per month and by each player. I believe that has only happened once before, on 30 September 2012. We had two games on that night, both of which were cancelled. Currently, 3 of our 6 games are on uncovered pitches, Monday night at Macpherson, and Wednesday and Thursday nights at Khalsa. Before 2011, most of our games were played on covered pitches. To the best of my recollection, I doubt that more than 10 games have been cancelled due to rain since then. However, even if heavy rain stops by 8 pm, there is a risk that the game may be cancelled due to the pitch being waterlogged. This appears to be a greater risk at Macpherson, where I understand the water is very slow to drain away. The game on at Macpherson on Monday, 16 May 2016 was cancelled for this reason, even though it had stopped raining by 7.30 pm, as those who play regularly there felt the pitch would still be waterlogged at 9 pm. .... Starting last season, late cancellations have been included in the selectors/captains table. From this season onwards, late cancellations will earn the same number of points as draws. The above applies to all games cancelled after line ups are finalised due to playing conditions (bad weather, haze, or pitch unplayable). To help keep track, the report thread will for such games will remain up. Last night's game at Macpherson was cancelled at 8.20 pm due to lightning and rain. The report thread remains up.
|
|
|
Post by Rajiv on Aug 3, 2019 11:11:23 GMT 8
Like the selector/captain system, giving the first person to post an account of the game on the report thread has been in place for some time now. However, despite the $2 credit for the first report (the same as being selector), only a few players make an effort to post an account. Further, the person posting is often from the winning team. It would be useful to have an account from a player on the losing team as well. Further, I have not been giving the selector/captain credit until at least one account is provided on the report thread. This is so that I know that there are no significant unresolved issues arising from the game. However, this may be unfair to selectors, who have already done their part before the game, in working on the line ups. Of course, selectors having priority in the first 24 hours after the schedule thread for the following week's game goes up is intended not only as an incentive not to opt out as selectors, it also serves as but of the "credit" for doing so. For games that fill up fast, with players on waitlist within 24 hours after the schedule thread goes up, priority is a bigger incentive than the small monetary credit, which was always intended to be token. Going forward, and with effect from the report thread for the game today (Saturday):
- Except where I suggest line ups, selectors will each receive $1 credit after the report thread for the game being put up and the game is completed (that is, they don't have to wait until there is a report of the game). This also applies to non-playing selectors.
- The first PRG player from each team to post an account of the game on the report thread will receive $1 credit each. If any PRG players watch the game without playing in the game, and post an account of the game on the report thread, the first to post a report will also receive a $1 credit. The reports must be first-hand and genuine to receive a credit.
- Each captain will receive an additional $1 credit if a player from their team provides an account on the report thread. Unless otherwise stated, selectors are also captains. Captains should encourage their team-mates to do a report, or just do one themselves.
Therefore, the total amount of credit available for selectors/captains remains $4, but $2 will now be given upfront after the game, without waiting for a report. The total amount of credit available for reports is increased from $2 to $3.
The ball and gloves credits remains unchanged.
All of the game credits referred to above will continue to be recorded on the report thread within a week of the game.
Additionally, in the first 24 hours of the schedule thread for the following week's game being put up, the selectors, captains, and the first PRG player from each team (and the first of any non-playing PRG player) to provide an account before then, will have priority.
|
|