I retired as the Ranger team Lead. Check the Herald for the current Team Lead. I am leaving this page here for posterity though.
Greetings and well met. I am Larian
LeQuella of Armyn ab Treanid.
I serve as your Team Lead. What is a Team Lead you may ask. Well, I will
serve as your voice to Mythic to get our issues raised to them, and
hopefully make our class better. Mythic themselves have put up a bit of a
page to explain the whole system if you are interested. Find out about
Team Leads Here. I have set up this series of pages to help you keep
track of how I have been doing as well as to let you all know what I am
thinking. You can even leave additional comments for me HERE
if you want. Please bear with me as I get these pages up to snuff. A lot
of construction going on!
Here is a compilation of all the ranger reports. These reports are
written in a specific format dictated by Mythic. They will outline the
basics of what this web page has, but in a condensed and concise format.
Each reporting period these reports get sent to Mythic, and the Team Lead Coordinator
makes feedback. Once I get the feedback, I will post the report with the
feedback as well. Rebuttals or replies to the feedback will be put into
the next report if appropriate. If the issue is too large for inclusion
into the report, then I will put it up on the web page and direct Mythic
to that (as well as sending them an email on the subject).
Issues and Bugs
Even though the Ranger class is doing well, there are still MANY issues and concerns that plauge
us. While I try to summarize most of them on the reports to Mythic, there
just isn't enough room. Also, many of the issues cannot be adequately
addressed in the report. As such, I made all these pages to keep track of.
Each issue will get updated if something changes as well as added to if we
have any ideas or feedback that apply. I look to you, the ranger
community, to help we keep this relevant and up to date. Please send
feedback to me at Larian@LarianLeQuella.com if you have any.
Melee and Celtic Dual
Player Feedback Comments
Team Lead Program
Blatantly stolen, erm, I mean borrowed, from Oaklief's Scout
Page. I hope he doesn't mind too much! Keep in mind this was written many years ago. While the exact content may not be 100% accurate, the sentiment is what matters.
"I continue to have people ask what the Team Lead program is all about,
and how it works, and why I don't get scouts fixed after reporting the
same things month after month, after month, after month... Well,
here's my best shot at an answer. Most of it comes from the summary
of what the team leaders responsibilities and focus is supposed to be that
I wrote with input from the other Team Leaders and which Sanya kindly posted on
the Herald, though what you see here is updated slightly due to some minor
changes that have occurred since that article was first posted.
First, the Team Leaders are players, NOT Mythic
employees. They are volunteers who have chosen to spend some of their free
time helping to make the game better for everyone, often at the expense of
being able to play the game for fun. So be aware that they are players,
not employees, and don't always wear the Team Leader hat when in game -
please respect their choice if they ask you to post your feelings,
observations, or concerns to some message board because they are playing
and not testing at the moment. Also, Team Leaders are not customer service
representatives. Many of them have their /advisor flag set to "on" when
they play, but they cannot make changes in game, unstick characters, or
perform other CSR functions, so please don't ask them to do that.
The testing teams were introduced to help the individual
developers stay on top of important issues that might otherwise be missed.
These teams are to delve into the strengths and weaknesses of each area in
depth, and note bugs, issues, concerns, and areas where there is
imbalance. Each class has a testing team, a tradeskill team, and a large
encounter team (for things like the dragons and other high-end multi-group
encounters). These testing teams include players on the live servers as
well as on the Pendragon test server.
The primary role of the Team
Leaders is ensuring that the realms are balanced against each other, and
bringing bugs and other concerns to the developer's attention. Their
secondary role is to act as a class advocate; making suggestions to keep
the class fun to play while not being overpowered or underpowered within
the limits of the vision for each class. Team Leaders and team members are
encouraged to dabble with other classes to get a feel for their balance
and a fresh perspective on their own class. Please note that their highest
responsibility is to help create a balanced game, not looking out for a
particular class or realm although they are advocates for their area. Many
Team Leaders have called for strengthening their class when its weak, and
called for weakening their class when it's too strong - that is their
role. However, they are not the last word on class balance. They provide
feedback and suggestions, and then the developers make their own decisions
The duties of the Team Leader include reading the
closed Team Leader boards, reading and moderating their area forums on the
closed Pendragon test-server boards, and maintaining contact with the
player base beyond that as they see fit. Their presence on any board other
than the Pendragon test-server board is not mandatory.
test any changes that affect their area as they are implemented on
Pendragon, keeping in mind the overall balance and vision. It is then
their responsibility to collate the opinions, observations, and data
pertaining to their area and present that information in an unbiased
fashion to the developers. This usually happens the second weekend after a
live-server version patch with a Team Leader Report that they may choose
to share on public boards if they wish, though they are not required to.
The Team Leaders are not involved with developer discussions about their
reports and posts on the Team Leader board once they have been made, nor
are they part of prioritizing changes, new content, and new features. They
are not informed of changes being made before the patch notes are put on
the Herald and the Pendragon test-server boards. Here is how the
- We gather the feelings of the community and data to back up those
feelings with the help of our testing teams. We present those
issues/ideas to the TL Coordinator and any other dev who cares to read
the TL Reports. She makes short summaries of the issues in each report
and consolidates them into one document for consumption by the
developers not reading the reports. Several other developers
specifically read the reports as well looking for items in their
- Several other devs specifically gave us their emails when there is
an issue in their bailiwick. That leads to an email conversation
- We participate in discussions about issues on the TL Only board,
which any dev who can spare the time joins in on. Typically we see the
TL Coordinator, the Producer, and several CSRs and developers who have
some spare time to keep tabs on what we are doing. Other
developers make appearances when the TL Coordinator calls their
attention to a thread in their purview. These discussions are often
passionate, and give the developers a chance to see pros and cons of
situations from different class/realm perspectives.
developers mentioned above are not the only developers we see, they are
the ones we see most frequently. When an issue is in a certain
developer's area, they get the information they need. Sometimes it just
gets fed to them from us or the bug teams, sometimes they need to come
back to us for clarification. Sometimes they work with our suggested
solutions, sometimes the developers have come up with a different
solution to try... our suggestions are just that - brainstorm starting
- So far, you will notice that all of the information is basically
flowing into Mythic from us, with opportunities for clarification to
make sure the issues are understood and pinpointed. As I
understand it, the issues are then brought to a general meeting if they
are new, prioritized, and handed off to the dev in charge of that area.
Other issues that have been waiting a while will also be brought up at
the meetings before work begins on them to make sure that a better
solution might not have presented itself with the revisions to the game
since it was first brought up. If they require collaborative effort to
make the dev-chosen fix take place, that adds a wrinkle as the involved
developers all need time to work on it together among their other
- The item is coded and tested on the dev-only test server. It is then
evaluated and the results brought back to a dev meeting to see if anyone
has issues with the way it appears to work in that small
- Passing that, it is added to the next Pendragon patch. Sometimes
Team Leaders get a heads up about what is going in before the patch
notes come out, for the majority of the changes in a patch we find out
the specifics when the notes go up on the Herald. The Pendragon
community then beats on the changes for a while looking for issues that
might appear in the larger test community. Again, discussion and issues
are reported back to the devs about the current Pendragon patch via
class boards like these, the tradeskill boards over at DAoC Tradeskills, and any
other boards that a TL may look at like the various Vault Communities;
my two chosen boards are listed above. These issues are time sensitive
so they receive priority when reported.
- Once the devs decide the patch has been beat on enough, it is sent
live. Issues may still crop up, and depending on their severity may
receive top priority or may be added to the general to do list with some
lesser priority for future revision.
What avenues do normal players have for bringing an issue to the
developer's attention then?
- They can do a bug report /appeal that will be passed directly to the
bug testing team for verification. When verified it will be passed to
- They can raise an issue where they know a TL will take a look at it.
We generally test it ourselves to verify it, sometimes with the help of
the testing team we have assembled, and then it gets reported on the TL
Only board or emailed to the appropriate dev. It also will usually end
up in a TL Report somewhere, for addition to that process.
- They can email Sanya with the issue. If its a bug, she'll pass it on
to the bug people that would have seen it if you did an /appeal, so that
just wastes her time. She's better suited for dealing with the balance
issues and answer questions about how the mechanics of the game work
behind the pixels.
The important part to stress here is that the process is slow, no
matter how obvious the fix is to you, and getting irate about it tends to
cause delays because emotion filled posts give the developers less to work
with than data filled posts do (analysis of what a log is supposed to show
helps, as does statistical analysis of repeated trials).
The Team Leaders are volunteers, in many cases they have
spent over two years putting in a daily effort to make DAoC a quality
game. They continue to provide data, concerns, and support for the players
and the developers, asking for little more than being treated
respectfully." - Oaklief