HORUS CUP 2008
SAILING INSTRUCTIONS
The following instructions are a complement to the notice of race
1-ABBREVIATIONS
HCSI= Horus Cup Sailing Instructions
RRS= Racing Rules of Sailing (regolamento di regata 2005-2008)
R= single rule os RRS. (Es: R14)
C=letter identifying an appendix C rule.
OC= Organization Committee
PC= Protest Committee
2- COMMITTEES
Two reference committees will be created
2.1- ORGANIZATION COMMITTEE
E-mail: organization_hc08@vskitalia.com
Members: Estremo 95, Ugone, LucioDiMare, MMario, Parklane, Simone, Skyppino
It is responsible for organizing the tournament, handling the results and the complaints in case of disagreements between the syndicates
2.2- PROTEST COMMITTEE
e-mail: protests_hc08@vskitalia.com
Members: Pavana, Salsailor, Leone, Isatis, Olandese Volante, Zicus.
It is responsible only of complaints in water
3- RACING RULES OF SAILING
3.1- Races will be arbitrated by the virtual judge of VSK5 who acts - insofar as possible - according to the regulations set by the racing rules of sailing ISAF 2005-2008 part 1 (fundamental rules) , part 2 (when two boats meet), and appendix C (rules for the match race). Moreover, skippers will have the possibility to manage penalties according to the provisions set in IRHC9 “protest procedure on the water”
3.2-”The term "filled mainsail" in rule C2.4 (R 13.2) will be understood by the PC as: “the boom has clearly completed its movement and is normally positioned in relation to the point of sale. This means that a jibe will not be considered completed when the boom ends up in a position which is too central compared to the proper adjustment for that point of sale”
3.3-No boat will be penalized for breaking R14. This does not entail that a right-of-way boat has to go necessarily into contact with a give-way boat in order to prove that the give-way boat was not keeping clear to her. As to the definition of "keeping clear", avoiding actions by the right-of-way boat will be taken into account by the PC in judging whether the give-way boat was keeping clear or not.
3.4- The following interpretations of rules 15 and 16.1 are applied :
3.5- When VSK5 gives a penalty, the boat with course priority will break rule 15 if it gained its course right only by its own move and , from that moment, the boat without course right did everything possible to give room.
3.6- When VSK5 gives a penalty, the boat with course right is breaking rule 16.1 if it changes its direction and ,from that moment, the boat without course right did everything possible to give room. (With regards to this, it is necessary to underline the importance of responding immediately to the luff of a leeward boat. A delay, however little, with the purpose of gaining more speed before the luff , means that the boat is not doing its best to keep clear)
3.7-Backwards movement is not considered as a movement induced by "backing sails", thus R20.3 will never apply.
3.8-The sails and boom of the boats should not be taken into account with regards to issues about keeping clear, overlap etc.
3.9-A penalty turn is completed when it is both accepted by VSK5 and in accordance with the C7.2 a 1) and 2). One of the two alone is not enough.
3.10-VSK overlap calls of VSK5 will be trusted.It is shown that in some cases (very rare) a different delay time (lag) between PCs of racer can lead to different viewing situations. If , after a protest in water not solved in the race, the committee should identify, during the viewing and the processing of the replays , a real synchro difference that could made impossible the reaching of a judgment, the Committee could consider the possibility of repeating the race.
3.11-A boat may not use the Spinnaker before it has started. A boat starts when, having been entirely on the pre-start side of the starting line at or after her starting signal, it crossed the starting line in the direction of the first mark.
4-MEETINGS
4.1-To schedule their meetings, syndicates shall post their own availabilities and requests for challenge on the public forum, under the section named "Syndicates meeting room",where they shall open appropriate treads for each flight.
Players password = hc08
Spectators password = hcsp
Host must set at least a number of 6 spectators.
4.2-IF the two syndicates were not able to complete their races within the time limits specified by HCSI 4.7 , they will be allowed to complain to the OC within 24 hours after expiration of the deadline for the flight. The Committee will give a walkover to the syndicate that makes the biggest effort to sail and meet the requirements of the opponent
4.3-If it were not possible to state which syndicate has made the biggest effort, both syndicates will score 0 points.
4.4- In case of failure to submit complaints on this subject, 24 hours after expiration of the deadline for the races of that flight both syndicates will be awarded 0 points
4.5-It is not necessary to finish each race in order to make them official. To save time, the competitor behind may at any time give up a race if it's unlikely that he can catch up.
- FIRST ROUND: “round robin”
4.6- The number of flights will be equal to the number of subscribed syndicates, or (if it applies) included in each group, less one.
4.7-For each flight, syndicates shall sail 4 races against the assigned opponent within one week, starting from Monday 00:01 GMT +2 , due to DST to Sunday 23:59 GMT +2 , due to DST . The official day and meeting hour will be Sunday at 22:00.The date and time scheduled in the calendar for the meeting between the teams are to be considered official and should be respected. Only in special cases and by mutual agreement with the opponent , a team can anticipate the date and time of the race . In every case, variation must be requested with a post in the appropriate Tournament forum by the requesting team and there must be an affirmative response from the opponent team on the forum to validate the variation.
In the absence of an answer from the opposing team, or an agreement between the opponent teams, the appointment scheduled in the journal will remain valid.
4.8-It is allowed to start a race by the time limit of 11.59 PM of the last possible day (Sunday) and end after that limit
4.9-For each flight, each syndicate shall go at starboard entry for half (=2) of the scheduled races.
4.10- All skippers belonging to a syndicate must take part in a minimum number of races, according to the following formula
#rRR/#Ss-(R+2).
#rRR = Number of races per round robin
#Ss = Number of skippers of the pertinent syndicate
R = Difference (because #rRR may sometimes not be divided per #Ss)
+2 = To have a margin of flexibility (the number may be varied before the beginning of the tournament once the number of syndicates participating in the race have been made known)
4.11-Any member of the syndicate is allowed to take part in the remaining races (To this effect, before the beginning of the tournament and after the closing time for registration, the exact number of compulsory and free sailing races for skippers of each syndicate will be posted on the forum HC2008 in the room “Sailing Instruction Update Log”)
4.12- In case the skipper of a syndicate does not finish his minimum number of races, these can be concluded by another member of the syndicate and the score will be modified according to IHRC 6.2
- Final round : In the final phase will be played quarter finals , semifinals and finals.
4.13 a)- The first 4 syndicates each group will challenge each other in quarter-finals, with direct elimination mode, crossing the classifications of the two round robin groups: the first in Group A against fourth in Group B, the second in Group A against the third in Group B, the first in Group B against fourth in Group A and the second in Group B against third of group A. The quarter-finals will be raced to the best of 5 races. The first of the two syndicates that will reach 3 victories will move to semifinals.
4.13 b)- Each final round (semi-final and final) will take place according to the best scores of the 7 races. The first of the two syndicates scoring 4 victories will win each serie.
4.13 c)- In the whole final round (quarter finals ,semifinal + final) each member of the syndicate must sail at least one race. A breach of this rule will cause the invalidation of a victory. As a consequence, a syndicate will not be awarded the Hours Cup if not complying with this rule.
4.14-.In the final round (semi-final and final) each syndicate will have to go at starboard entry for the half of the scheduled races. The starting point of the fifth race in the quarter finals and the starting point of the seventh race in semifinals and final ,will be random (chosen by VSK5)
5- SAILING MAPS
5.1-All the races must be played in “tactical” mode and “complete (auto)” rules.
5.2- During the round robin, at the beginning of each flight, a new map will be posted on “link and download” (in the home page HC2008)
5.3- For the final round, maps will be chosen by the OC among those posted during the round robin. The choice will be made public before the beginning of the round. It is recommended to keep the maps of the round robin since they will be used in the final round
5.4- For each map, two identical copies will be created
Example
a) Horous Cup 01 “free” unblocked copy. Can be edited by everybody to study the features
b) Horus Cup 01 “fixed”. Blocked by a password. Cannot be edited
In case of official races, only “fixed “maps will be used
5.5-Guest players (including spectators) are also responsible for checking that the hosting player is using a "fixed" map. A breach of this rule, not detected before the preparatory signal is given, will not be ground for a protest and will not invalidate the race.
6- SCORES IN ROUND ROBIN
6.1-Syndicates will score 2 points for each victory and 1 point for each loss. Victories by adjudication wil be regarded as ordinary victory, while losses by adjudication will not change the score of the losing syndicate ; in this last case , no points were gained by any skipper ( neither of winning team nor of loosing team ) , in this way those races will not affect calculation of minimum number of race per skipper as written in rule 4.10
6.2-Syndacates, whose skippers don’t play the minimun expected races, will receive a penalty of -2 points for each race not played by their skippers.
7- COMMUNICATIONS ON THE WATER
7.1-During the race, the only official comunication channel between two syndicates is the vsk5 chat.
7.2 – The words that will be considered relevant to hail a protest are the words written in vsk5 chat by the two skippers involved in the race. Each skipper, during the start operations of the race and previous information to his opponent, can delegate his chat communications to another member of his syndacate; from this moment, the “official chat” will be the “delegate’s chat”.
7.3- there should be no comments by spectators on the race chat.
7.4- The Horus Cup races between registered skippers on www.vsk-match.com must be considered valid for vsk-match.com ranking too. If a competitor didn’t want the race to be valid for the ranking, then he/she shall inform his opponent before the race start.
8- DISCONNECTIONS
8.1-If a competitor is disconnected from the game due to connection problems, please relaunch another race and/or enter the vskitalia chat to communicate with the other competitor. The new race should be setup in one of the three following ways, depending on what the situation was at the moment of the disconnection.
8.2- Do a complete new race from the beginning if it was not clear that one competitor had the advantage in the race.
8.3- If one competitor had the advantage (or had escaped disadvantage during prestart), restart the race and make sure the competitor that had the advantage is given a similar advantage in the new race.
8.4-Score the race as a win to the leading competitor if the margin was so big that it was unlikely the other competitor could have caught up.
9-PROTEST PROCEDURE ON THE WATER.
9.1- A competitor may hail for protest by writing "P" or "Protest" in the race chat as soon as possible after the incident.
9.2-A competitor may also write alternatively "P Red" or "Protest Red" if the penalty qualifies for a red-flag penalty as described in RRS C6.5.b
9.3-The competitor who is protested on should as soon as reasonably possible reply with:
a) "Y" or "Yes" if he/she agree that he/she has broken a rule. A penalty should be added to his/her tally.
b)"N" or "No" if he/she disagree that he/she has broken a rule. A penalty should not be added to his/her tally, but the competitor who protested is entitled to file a post race protest to the PC. No reply (or a reply considered not “as soon as reasonably possible”)is to be considered as "No" and allow the protesting boat to file a valid protest to the PC..
9.4- If a competitor who got a VSK5 penalty claims that it should not have been given any penalty in this situation, he/she should request a penalty cancellation. The request is the regular VSK5 feature, either by clicking on the penalty icon or pressing the key which VSK5 have assigned for the feature.
9.5- A competitor who receives a request to cancel a penalty SHALL ALWAYS CANCEL THE PENALTY, regardless of whether he agrees or disagrees with the call. If erroneously the cancellation request was not satisfied , the competitor with penalty pending will have the right to continue the race and cross the finishing line without the due to solve the penalty. The other skipper will send ,about the case , a valid protest to the committee. The competitor that makes cancellation request, in fact, assumes full responsibility for this request and accept any consequences if the penalties imposed were to prove correct.
9.6-if the committee detected that a skipper refuses to cancel more than a penalty clearly wrong in the same race, the competitor may have a disqualification for R2 Part 1 of Regulation ISAF.
9.7- The VSK5 cancel feature does not work if the penalty removed a penalty from the opponent instead of adding one to the competitors tally, so in such a case a competitor has to write "C" or "Cancel" in the race chat instead. A penalty that is requested cancelled by writing "C" should also be considered cancelled by default and the opponent pen has to be considered still existing.
9.8- A competitor who disagrees with a penalty cancellation, should write "P" or "Protest" right after the penalty has been cancelled and file a valid protest to the PC after the race and the opponent can’t answer “Y” to this protest request. Should he/she mistakenly do it and/or carry out a penalty, the protesting competitor still has the right to file a protest to the PC. It makes in fact no sense that the boat requesting the cancellation of a penalty will than take the penalty just removed
9.9- If a competitor who got a VSK5 penalty claims that the penalty should have been given to the other competitor, he/she should request a penalty cancellation as described in HCSI 9.4 followed by a protest call ("P"/"Protest") as described in HCSI 9.1.
9.10- competitors who deliberately break a rule, or get a big advantage by failing to keep clear, may be punished with extra penalties in addition to the regular penalty. An example of such a maneuver is a boat ramming down the starting line in order to sacrifice a penalty instead of being pushed over the line. The protesting competitor should write "PX" or "Protest extra"; if he is claiming that the incident is classifying under this rule. The protested competitor should respond as in HCSI 9.1
9.11- Penalties given by VSK5 and penalties accepted volunteerly (with a "Y"/"Yes" as in HCSI 9.3) or cancelled by "C", should be summarized. If possible, the VSK pen tally should be manipulated in order to allow the VSK tally to represent the correct tally. Examples on how to do this is typically by cancelling a penalty if there are too many penalties, or to deliberatly take a penalty by hitting a mark.
9.12- A skipper is crossing, or has already passed, or is going to pass the finish line , must do it in compliance with ISAF Regulation. When an incident occures just before the finish line, if neither the protesting or the protested competitor has time to follow the protest communication procedure before finishing, the protest may still be valid.
10-PROTEST PROCEDURE OFF THE WATER.
10.1- At the end of a race, or of a series of races, in case of not solved protests in races , teams or their captains must watch the replay together with lucidity and analyze the happened episodes , in order to determine responsibility and infringements and reach the consequent adjustment of the race standings. A committee decision will never be exhaustive as an according on the water from the syndicates. The appeal to committee is to be considered as the last resort due to the fact it was impossible to find an agreement wich was acceptable for both teams.
10.2-To send a correct protest to the Committee , the captain or the vice-captain must :
a)-;produce the replay of the skipper actually involved (not a replay of a spectator) and a brief report of events
b)-Exact timing of presumed fault(s).
c)-Take and send a screenshot right after the response "No" (or lack of response) from the opponent.
10.3-The protest must be submitted via e-mail to the committee (protests_hc08@vskitalia.com), within 24 hours after the end of the race(s)( proof will be the time of submission of the first e-mail with the result) , placing in cc the address of captain of the opponent team involved in the protest.
10.4-If the Jury finds one of the competitors was breaking a rule at the incident, and no penalty turns were added to her tally, then she will be disquallified from the race. What happened later in the race is irrelevant. Ex: A competitor can not free her self from a protest later in the race if she did not initially confirm that she added a penalty to her tally right after the protest.
10.5- To be a protest valid and acepted, all the procedure on the water must be respected.
10.6- an appeal may be considered by the committee only if all the procedures described in IRHC 10.2-10.3 - 10.5 were matched.
10.7-The syndicate who is protested may send an e-mail in its defence within 24 hours after receipt of the copy of the e-mail with the protest. It is advisable to attach the replay of the protested competitor (not of a spectator) and possible screenshots
10.8-The Committee will analyze only the received replay and will take the committment to formalize the outcome of a protest in a time not exceeding 5 days from the date of its receiving (the official time and date of the protest are those recorded in the email).
10.9-If the situation occured prior to 2 minutes before start, then the situation is not included in the replay, however any protests will be accepted only if those will be accompanied by appropriate and clear documentation. In order to be able to protest on such incidents, you will need to record the first part of the races with some kind of video capture. A tool for capturing video while racing is Fraps ( www.fraps.com). Don't send huge video files to the jury, as they will not be read. Reduce the size, and ideally upload your case on YouTube.
10.10-The remaining of the series should be sailed while waiting for the PC decision.
10.11-. There are no appeal options. The decision of the PC is final and it will be pubblished in the HC forum "protest decisions".
11- RESULTS
11.1-At the end of disputed races , both teams must send results by e-mail to the Organizing Committee (organization_hc08@vskitalia.com) . It is possible that under agreement between the teams at the end of the race results will be sent by only one team.
11.2-Results are to be reported in the body of the message as follows:
E-mail title:
FLIGHT X - GROUP X - SYNDICATE A vs SYNDICATE B.
Text:
Skipper A vs skipper B
Winner: skipper A/B
Starboard Entry : skipper A/B
NOTE: any notes (protests and comments).
11.3-Arrivals screenshots, or surrender screenshots and races replays attached to the message.
12- OPENING RACE (big fleet)
For opening race ”big fleet” and for “round robin” phase all registered syndicates will be divided in two groups :
GRUPPO A
iTeaMyrtho = Simone (Capt) , Lorenzo (Capt) , LucioDiMare , Dariosilve.
Team La Cancalaise = Damy_FRA , Lenam Gold , Robin (Capt),
Black Hawks = Spittillo (Capt) , Marseille5 (Capt), David17 , Kent38.
Team Denmark = Rakosi (capt) , Miniden (capt) , Rudolf.
S.P.Q.R. Team = Yankee ( capt ) , Sciòsciò ( Capt ) , Luca 94 , Lupobianco.
Team Lupettidimare = Orione (Capt) , Fenis (Capt) , Virudaka.
ABnormal team = Salsailor(Capt) , Pavana (Capt), Alvarito , Mistermagoo.
YC VskSailing I-Team = Orca l'oca (Capt), L'Olandese Volante (Capt), Work In Progress , Pibedeoro
GRUPPO B
Antani Team Racing = Team Elunda (Capt) , Rocking Boat , Moro di Venezia , Gre144.
Team Vivarace.de = Checkmate (Capt) , casino (Capt) , Kwasi , Snoopy.
Team Vivavolunteers = Vriend (Harmen- Capt) , Nik (Nik- Capt) , Nessie (Carsten) , Calvin (Jan).
Team Pink = PistaXoOo (Capt) , Kresala (Capt) , Luna
Team Lupidimare = Leone (Capt) , Iceman (Capt) , Isatis , Fiu.
I-Team Colors = MMario (Capt) , Albachiara (Capt) , Superpira , Paolofico.
Onde Rocks I-Team = Raz (Capt) , Toloma (capt) , Molox ( P.R.) , FGL.
Canaglie Racing Team = Kanaja (Capt) , Giovanni , Marco Sui , Ita 38.
12.1-Date: April 2008 the 1st - Time 22:30 GMT +1
12.2- Meeting place: chat vsk Italia 20 minutes before the beginning. The race will be launched right on time. Due to difficulties in on organizing a sailing race with more than 30 boats, no delays will be allowed.
12.3-After closing time for registration, possible groupings will be posted in forum HC “sailing instruction update log”
12.4-The winner of each group will score 0.49 points. The following positions will score 0.01 points less than the winner (ex. the second position will score 0.48 points, the third 0.47 etc…). Such scores will not influence the final results of the round robin, if not with regards to even scores.
13- AMENDMENTS TO THE INSTRUCIONS
13.1-They will be posted on the tournament forum in the section “Sailing Instructions Update log” and ideally sent to all captains by e-mail. Syndicates are responsible to check possible updatings.
13.2-Amendments will be valid from the moment in which they are posted in the forum and will not be retroactive.
14-ANOTHER THING.
14.1-Any case that this regulation has not taken into consideration will be solved by the committees as more impartial way as possible in terms of common sense, and all syndivates are required to respect the delicate job and the decisions of the committees.
v1.6 07.03.2008 |
