ccshiro/How to get an account Secret

## How to get an account
IMPORTANT:  Upcoming tests will be announced on twitter.com/corecraft_shiro.
            Realmlist will be given out in #corecraft during the test period,
            just read the topic during an ongoing test and you'll get
            connectivity info.
IMPORTANT2: One of the most important parts of testing the server is making it
            crash, to identify crash points and patch them up. If you don't like
            the instability that comes along with that and sometimes being stuck
            for an hour doing nothing, then testing is probably not for you!
            You can read more about crashes and their purpose at our blog:
            https://www.worldofcorecraft.com/content/crash-course-crashes

1. What we want you to test
Generally speaking the intent of upcoming tests are to try things, watch them
break, and then report found issues to us. Anything you want to test (given it
doesn't break the terms) is fair game. Just remember that you have to report
found issues as well, or they will remain issues!

Some tests we have further directives or requests with things that need extra
attention. They will appear in the irc channel's topic during the test.

2. How to report bugs
There are two type of reports:
1. Things that are indisputable bugs.
   This includes content that has broken, spells that don't do what they should,
   and so on. In other words, things that are explicitly stated to work one way,
   yet doesn't.
   These issues can simply be reported with the guidelines listed below.

2. Things that seem incorrect.
   This might be mobs in a heroic doing more damage than you seem to recall they
   should, or a mechanic working opposite to what you think is correct.
   Basically, the implementation is working without flaws, yet it does not do
   what you anticipated it to.
   When you report these kind of issues, you need some form of evidential basis.
   Our implementations are based on research, and re-researching it for each
   report that claims they remember it differently is not viable. For that
   reason we require the person reporting it to provide basic evidence of
   his/her claim.
   Good claims are videos or screenshots of retail TBC, decent claims are
   well-discussed topics from reputable forums at the time, and poor claims
   are for example wowwiki articles not citing resources.

Report guidelines:
   When reporting issues, make sure you clearly state how to reproduce the
   issue, as well as any circumstances or states your character was in.
   For example, the following is a poor report:
   "Mark of the Wild doesn't work for me." (DON'T)
   A better report could be:
   "Mark of the Wild does not give me its advertised resistance. I have no other
    buff or debuff on me except for cat form. I'm wearing full PvP gear. This is
    fully reproducable by creating a night elf druid, getting PvP gear and
    switching to cat form." (DO)
   To submit a report, please visit our bugtracker at
   https://github.com/ccshiro/cc-buglist/issues
   If you don't have an account make one. After you've made sure no one else has
   reported the same issue, press New issue and type your issue out. Please
   consider revisiting your issue until it has been marked as solved as further
   input might be required. Thanks!

3. Terms, dos and don'ts
== Don't try to intentionally sabotage for the server or other testers. We're
   here to make corecraft the best server we can. Be nice and respectful to
   fellow participants.
== Don't gank or grief people trying leveling content. During the test there
   are options to roll a low-level character to help test the leveling
   experience. Griefing these players will get you banned from testing.
== Don't use cheats, hacks or exploits. Our anti-cheat system is disabled to
   make it impossible for people to gauge its workings pre-release. If you have
   some exploit or cheat that you wish to share with us, so that we can protect
   against it, please contact shiro in a PM instead of just trying it on the
   server.

4. How to get your account
If you've not yet typed !account in #corecraft, do so now. You'll be messaged
privately by ccbot. To him you need to (in private chat) type the following:
"I have read and accept the content of the paste." He will then give you your
account. Please note that you can only get one account, and that we cannot help
you recover lost information (so save the account details somewhere).

5. Tips and useful tricks
== Macro to learn all spells from any trainer (not sure where this one
   originates from, so can't give proper credits):
/run LoadAddOn"Blizzard_TrainerUI" f=ClassTrainerTrainButton f.e = 0 if f:GetScript"OnUpdate" then f:SetScript("OnUpdate", nil)else f:SetScript("OnUpdate", function(f,e) f.e=f.e+e if f.e>.01 then f.e=0 f:Click() end end)end

== In-game command to level up weapon skills and such:
(NOTE: You need to target yourself first)
.maxskill

== In-game commands to manage your pet:
(NOTE: You need to target your pet first)
.pet loyalty 6
.pet tp 350
.pet maxhappy

## Test information
NOTE: Please read the "seen a movement bug?" below.

## Seen a movement bug?
Please target the NPC that is bugging, and while the bug is happening, type
".movegens --verbose" in chat (without quotation marks) and take a print screen
of the output and the broken NPC visible in the screenshot. Any movement bug not
including this will be ignored (as we can't really debug them)!

## Goals of the test
1) Test whatever you like. If we're looking for something extra to be tested, we'll write
about it in the #corecraft topic.
2) Issues we need help with are listed here:
https://github.com/ccshiro/cc-buglist/issues?q=milestone%3A%22Needs+Testing%22
3) We've also added material vendors if you want to test professions (they can
be found in the middle of Shattrath).
4) As always, crashing the server and finding bugs in general is welcome! So,
anything you want to test is fine (within the rule-set).

## How to report a bug
# Step 1
Make sure you've read the ccbot's paste ( http://pastebin.com/QDjQBrU0 ) so you
know what constitutes a bug and what needs to appear in your report.
# Step 2
Make sure your report is actually a bug and if evidence needs to be included
(e.g. you're claiming something to be true) please provide it. Or your issue
will most likely be closed.
# Step 3
Visit our issue tracker https://github.com/ccshiro/cc-buglist/issues and use the
search functionality to make sure no one has reported your issue already.
Duplicate reports make it really annoying to organize and work with the issue
tracker. Please help us out by putting some time into using the search
functionality.
# Step 4
Now you need to log in or create an account.
# Step 5
Press the "New issue" button and submit your issue, describing the steps to
reproduce it thoroughly. Make sure your instructions to reproduce the bug are a
valid way to trigger it. If having screenshots or videos help explaining the
issue, please provide that.

## Connection issues?
Check the WoC's FAQ for details (Q21).

## Lost your password?
A lost password, like the bot told you when you got the account, cannot be
retrieved or reset. We can give you a new account, however. Preferably you ask
us for a new account outside the test period as we are generally busy during. If
it's during the test period it doesn't hurt to ask, but we might not respond (or
it might take a while until we respond) if we're preoccupied.

## What devs are present?
If you check the topic of #corecraft you can see what devs are currently
present.

## Other issues?
Ask for help in #corecraft, maybe someone can help you. If you PM a developer
expect a delay in response as we're most likely busy during tests. You can also see
which developers are present in the topic of #corecraft.

## Realmlist
See the #corecraft topic for the realmlist
	IMPORTANT: Upcoming tests will be announced on twitter.com/corecraft_shiro.
	Realmlist will be given out in #corecraft during the test period,
	just read the topic during an ongoing test and you'll get
	connectivity info.
	IMPORTANT2: One of the most important parts of testing the server is making it
	crash, to identify crash points and patch them up. If you don't like
	the instability that comes along with that and sometimes being stuck
	for an hour doing nothing, then testing is probably not for you!
	You can read more about crashes and their purpose at our blog:
	https://www.worldofcorecraft.com/content/crash-course-crashes

	1. What we want you to test
	Generally speaking the intent of upcoming tests are to try things, watch them
	break, and then report found issues to us. Anything you want to test (given it
	doesn't break the terms) is fair game. Just remember that you have to report
	found issues as well, or they will remain issues!

	Some tests we have further directives or requests with things that need extra
	attention. They will appear in the irc channel's topic during the test.

	2. How to report bugs
	There are two type of reports:
	1. Things that are indisputable bugs.
	This includes content that has broken, spells that don't do what they should,
	and so on. In other words, things that are explicitly stated to work one way,
	yet doesn't.
	These issues can simply be reported with the guidelines listed below.

	2. Things that seem incorrect.
	This might be mobs in a heroic doing more damage than you seem to recall they
	should, or a mechanic working opposite to what you think is correct.
	Basically, the implementation is working without flaws, yet it does not do
	what you anticipated it to.
	When you report these kind of issues, you need some form of evidential basis.
	Our implementations are based on research, and re-researching it for each
	report that claims they remember it differently is not viable. For that
	reason we require the person reporting it to provide basic evidence of
	his/her claim.
	Good claims are videos or screenshots of retail TBC, decent claims are
	well-discussed topics from reputable forums at the time, and poor claims
	are for example wowwiki articles not citing resources.

	Report guidelines:
	When reporting issues, make sure you clearly state how to reproduce the
	issue, as well as any circumstances or states your character was in.
	For example, the following is a poor report:
	"Mark of the Wild doesn't work for me." (DON'T)
	A better report could be:
	"Mark of the Wild does not give me its advertised resistance. I have no other
	buff or debuff on me except for cat form. I'm wearing full PvP gear. This is
	fully reproducable by creating a night elf druid, getting PvP gear and
	switching to cat form." (DO)
	To submit a report, please visit our bugtracker at
	https://github.com/ccshiro/cc-buglist/issues
	If you don't have an account make one. After you've made sure no one else has
	reported the same issue, press New issue and type your issue out. Please
	consider revisiting your issue until it has been marked as solved as further
	input might be required. Thanks!

	3. Terms, dos and don'ts
	== Don't try to intentionally sabotage for the server or other testers. We're
	here to make corecraft the best server we can. Be nice and respectful to
	fellow participants.
	== Don't gank or grief people trying leveling content. During the test there
	are options to roll a low-level character to help test the leveling
	experience. Griefing these players will get you banned from testing.
	== Don't use cheats, hacks or exploits. Our anti-cheat system is disabled to
	make it impossible for people to gauge its workings pre-release. If you have
	some exploit or cheat that you wish to share with us, so that we can protect
	against it, please contact shiro in a PM instead of just trying it on the
	server.

	4. How to get your account
	If you've not yet typed !account in #corecraft, do so now. You'll be messaged
	privately by ccbot. To him you need to (in private chat) type the following:
	"I have read and accept the content of the paste." He will then give you your
	account. Please note that you can only get one account, and that we cannot help
	you recover lost information (so save the account details somewhere).

	5. Tips and useful tricks
	== Macro to learn all spells from any trainer (not sure where this one
	originates from, so can't give proper credits):
	/run LoadAddOn"Blizzard_TrainerUI" f=ClassTrainerTrainButton f.e = 0 if f:GetScript"OnUpdate" then f:SetScript("OnUpdate", nil)else f:SetScript("OnUpdate", function(f,e) f.e=f.e+e if f.e>.01 then f.e=0 f:Click() end end)end

	== In-game command to level up weapon skills and such:
	(NOTE: You need to target yourself first)
	.maxskill

	== In-game commands to manage your pet:
	(NOTE: You need to target your pet first)
	.pet loyalty 6
	.pet tp 350
	.pet maxhappy
	NOTE: Please read the "seen a movement bug?" below.

	## Seen a movement bug?
	Please target the NPC that is bugging, and while the bug is happening, type
	".movegens --verbose" in chat (without quotation marks) and take a print screen
	of the output and the broken NPC visible in the screenshot. Any movement bug not
	including this will be ignored (as we can't really debug them)!

	## Goals of the test
	1) Test whatever you like. If we're looking for something extra to be tested, we'll write
	about it in the #corecraft topic.
	2) Issues we need help with are listed here:
	https://github.com/ccshiro/cc-buglist/issues?q=milestone%3A%22Needs+Testing%22
	3) We've also added material vendors if you want to test professions (they can
	be found in the middle of Shattrath).
	4) As always, crashing the server and finding bugs in general is welcome! So,
	anything you want to test is fine (within the rule-set).

	## How to report a bug
	# Step 1
	Make sure you've read the ccbot's paste ( http://pastebin.com/QDjQBrU0 ) so you
	know what constitutes a bug and what needs to appear in your report.
	# Step 2
	Make sure your report is actually a bug and if evidence needs to be included
	(e.g. you're claiming something to be true) please provide it. Or your issue
	will most likely be closed.
	# Step 3
	Visit our issue tracker https://github.com/ccshiro/cc-buglist/issues and use the
	search functionality to make sure no one has reported your issue already.
	Duplicate reports make it really annoying to organize and work with the issue
	tracker. Please help us out by putting some time into using the search
	functionality.
	# Step 4
	Now you need to log in or create an account.
	# Step 5
	Press the "New issue" button and submit your issue, describing the steps to
	reproduce it thoroughly. Make sure your instructions to reproduce the bug are a
	valid way to trigger it. If having screenshots or videos help explaining the
	issue, please provide that.

	## Connection issues?
	Check the WoC's FAQ for details (Q21).

	## Lost your password?
	A lost password, like the bot told you when you got the account, cannot be
	retrieved or reset. We can give you a new account, however. Preferably you ask
	us for a new account outside the test period as we are generally busy during. If
	it's during the test period it doesn't hurt to ask, but we might not respond (or
	it might take a while until we respond) if we're preoccupied.

	## What devs are present?
	If you check the topic of #corecraft you can see what devs are currently
	present.

	## Other issues?
	Ask for help in #corecraft, maybe someone can help you. If you PM a developer
	expect a delay in response as we're most likely busy during tests. You can also see
	which developers are present in the topic of #corecraft.

	## Realmlist
	See the #corecraft topic for the realmlist