If Looks Could Kill

If Looks Could Kill Official Thread Logs can be found here: http://www.worldoflogs.com/guilds/67992/

Progress Report: http://wiki.aie-guild.org/index.php?title=Raiding_Progression#10.2F25_Member_Cataclysm_-_Tier_12.2B

Agrgloth Feb 02 12/12 Magmaw Feb 02 Halfus Feb 09 ODS Feb 21 Conclave March 02 Maloriak March 23 V&T March 27 Atramedes April 06 Chimaeron April 18 Ascendant Council April 27 Al'akir May 8 Cho'gall May 16 Nefarian May 23

Current Raid Lineup This first post is a regularly updated record of membership status and policies. ALL confirmed and preferred/friends will receive calendar invites for all If Looks Could Kill activities. We'll do our best to include preferred/friends members on Sunday nights. A calendar invite does not necessarily guarantee participation will be possible. See the Team Membership section below for details.

Tanks Tigglath (in-raid leader; tank team leader; team bank alt Urukhan) Newdamda (team bank alt Newmoo)

Healers Eade* (team bank alt Elarista) Tuketu (team bank alt Hakkea) Wolfshayde* (healing leader; team bank alt Idiot)

DPS Shmage (team bank alt Minishmage) Thunderclese (team bank alt Tadgi) Thunderhoss (dps leader; team bank alt ) Tinkbottom (team bank alt Lamepaw) Vanterax (buff leader)

Summer Member SouthPaw

Preferred (alphabetical order with preferred then friends; if you wish to be on this list contact Eade or Wolfshayde) Helghast Kamarag Lydeeia Morgaenna Pastormetro (team bank alt Zizzt) Trynnity (team bank alt Jaedynn)

Friends Badjah Beazle Brain Gotdice Haulke Magnand Mairabelle Matarael Puppypelt Vampp Zodapalooza/Zodder/Zodrageous

Hiatus Kuboifox Trikkajin (team bank alt Geldgierg) Yokor

• If Looks Could Kill overall team leaders

If Looks Could Kill (Si Vultus Could Iuguolo)

Motto:

Together We Shine (Una Nos Fulsi)

Overall Team leaders:

Eade, Wolfshayde

What this thread is for:

This thread is for announcements, status changes, updates, questions etc.

This thread is not for suggestions/voting. If you have a policy change suggestion or complaint, please contact a leader directly.

Philosophy:

Above all we emphasize having a good attitude and being team players. At its best, raiding can be a blast. But when pushing the edge, raiding can be a stressful experience. You will be expected keep a positive attitude and endeavor make the team better by being a good team player. During fights keep vent free for the team leaders. If you have a suggestion, whisper it to your team leader. Your team leader may ask to speak with you in a "team chat" channel if you have detailed suggestions or questions. Attitude is number one for this group. You will shine by making others better. Where a loose collection of shining stars would fail, we will succeed as a brilliant team.

Leadership:

The overall team leaders are responsible for recruitment, organization, and general team building. Essentially, if it happens before or after a raid, it is our responsibility. If it involves issues of management or organization during the raid, it is our responsibility. Whisper a leader for help. The overall team leaders are final arbiters and make all final decisions.

Leadership roles:

During a raid three members will have special responsibilities: the tank, healer, and dps team leaders. Team leaders are determined by the overall team leaders.

i) The tank leader will have primary responsibility for calling "ready checks" and either reviewing the mechanics of the fight or assigning someone to do so. Tanks will be responsible for their own readiness status. No need for tank leaders to install RBS. Every encounter will have at least a one sentence summary of the mechanics. Overall raid leaders retain general responsibility for the goals of the raid and pacing. An encounter should proceed as follows: Raid leader: "tank leader it's all yours" (this is an indication "downtime" is over)

Tank leader: "Healer leader you ready? DPS leader you ready? Ready check on the way!"

The tank leader is the anchor for the team and responsible for in-raid strategry.

ii) The healing leader will check with the healers to determine their readiness status regularly with RBS. The healing leader will assess the stress levels of his or her healers regularly. The healing leader will be ready to offer suggestions or make healing assignments when queried by the tank leader. The healing leader should whisper a raid leader if they detect personnel problems during the raid (e.g. "hey you may have missed it, but I think Joe has to go"). The healing leader is the emotional leader of the team.

iii) The dps leader will make sure the damage dealers are ready with the addon RBS. The dps leader should install the addon Recount and Omen or Skada and monitor dps and threat throughout the raid. The dps leader should work to manage damage done and threat throughout the raid. The dps leader should work toward being a positive motivational force for the damage dealers. The dps leader is the motivational leader of the team.

Team Members:

The final responsibility of raid performance and functioning falls to the overall team leaders.

If you've noticed something that people are doing which is causing problems, whisper it to an overall team leader and let them address it. They will pass it along to a team leader if necessary.

Team Leaders and Members:

Please remember that attitude and teamwork is priority for this team. Your performing five times better than your teammates will not be as valued as you helping your teammates perform as well as you (even if that means you do not shine as brightly as you could). Remember that as a team we can accomplish more.

Vent/Mumble Management:

During an encounter the team leaders have vent priority.

Between encounters the team leaders have vent priority.

If you have a suggestion whisper it to your team leader and/or a overall team leader.

If you have a suggestion for a member of a team for which you do not belong, whisper it to an overall team leader.

After an encounter is accomplished and when moving between an encounter is downtime.

Downtime is "fun time" and there's plenty of downtime in any raid, so rejoice.

During an encounter and between encounters (i.e. after a fail and before a retry) let the team leaders have vent.

Team Membership:

ALL confirmed and preferred/friends will receive calendar invites for all If Looks Could Kill Activities.

Confirmed team members should be in-game by 8:45 and be ready and available for invite by 9pm.

As a team leader be prepared to assist the overall team leaders if holes exist in your team. If you must, you may consider confirmed positions as permanent, but we should understand that our statuses may change depending on our real lives. You may request your status to be upgraded or downgraded at any time. Just let an ILCK leader know. Your status and priority as a member may change/rise and fall with attendance, preparedness, seniority, role requirements, attitude, competence, fit, etc. Our goals as overall team leaders are to create the most stable team possible while giving the most folks a chance to play. If you attend, fit with, and contribute to the goals of the raid team within our philosophy, you should consider that you have found a "permanent" home.

If confirmed members cannot run, we need you to post in this thread letting us know (reason not needed). It is a requirement of confirmed status that you will post here letting us know at least one hour in advance you will be absent/late. Preferred status may be upgraded to confirmed by regular attendance and/or status posting on your part. You MUST include the name of your toon in your post to be guaranteed that we will recognize who you are.

This structure should allow us to have the most fun while also accomplishing the most. If you have policy suggestions please contact a leader directly via private message on this board or via in-game whisper or vent.

Attendance Policies

A suggestion for maintaining confirmed membership is 75% on-time attendance (9:10 or earlier). Missing a regular raid night without one hour prior forum notification is a particular hardship on the raid team. No excuses or explanations will ever be necessary. The result of not meeting the attendance policy will be rotation to preferred/friend status. This structure should be helpful to those confirmed members needing time away from the game and those preferred/friend members waiting for a chance to play more regularly. As always, policy will be implemented with sensitivity and at the discretion of the team leaders. Members may want to access [url="http://www.worldoflogs.com/guilds/67992/character/"]Recent attendance for ILCK[/url] for an unofficial record of recent attendance.

Loot Policies

Open rolls by default. When attendance is regularly 8/10 or more confirmed members KSK. KSK will be used as a tool rather than a final arbiter. In other words, KSK may be overridden at the discretion of the team leaders (e.g. significant guest participation in a particular run). In this case, the master looter will report that an item is being held for discussion prior to distribution. Also, any confirmed team member may (before loot has actually been transferred) request in mumble or via whisper to the master looter "could this item please be held for discussion". If any loot items have been held for discussion, raiding will terminate 15 minutes early to allow for resolution/explanation and distribution.

Preferred/friends members are inserted randomly into our SKS list only at the discretion of the team leaders. This determination will be largely dependent upon contributions and class/role considerations. This will be explicitly discussed at the beginning of any raid containing a preferred/friend member. For these preferred/friend members, list placements will reset after breaks in contiguous attendance and random insertion will occur upon return. In other words, preferred/friend members may advance in the loot list only for as many back-to-back nights they contribute.

Guests will be, and preferred/friends members may be, placed at the bottom of our SKS list and do not advance. In this case, guests/preferred/friends members only receive loot if confirmed members fail to bid for main spec. Guests/preferred/friends will receive 1/10 value of any BOEs sold and will receive 3,000g per run if an eligible upgrade item(s) drops for which they are not given the opportunity to bid. If no bids occur, guests/preferred/friends may participate in open rolls and in this case no gold is awarded regardless of outcome. BOEs may not be available for open rolls at the discretion of the team leaders.

Any ALTs will be tethered to mains for KSK purposes.

Summary Loot Guidelines

Confirmed members should install the KSK addon if practical. Three confirmed members will have KSK installed and will synchronize these installations regularly (Eade, Fox, and Wolf). Members are encouraged to familiarize themselves with potential loot prior to raiding (install Atlas Loot and as we wait to form up, review you wish list). Members are encouraged to make bids/rolls promptly. If a member is anticipating placing a last second bid/roll they should announce in mumble "I am considering placing a bid/roll". If a member feels they need more time they should request in mumble "I need more time to consider a bid/roll please". Discussion is acceptable, but the master looter may ask for “loot silence” and at that point only questions directed toward the master looter or requests for an item to be held for discussion should be offered.

KSK will used as a tool for convenience and may be suspended at any time. We have been fortunate to have a fantastic group with an excellent esprit de corps with loot distribution never being a problem. In other words, it’s business as usual with KSK providing some convenience only. If you find this tool leading to competitive thinking, let the team leaders know. Remember, together we shine.

Your overall team leaders,

Eade and Wolfshayde