Post by Deleted on Apr 12, 2014 0:45:03 GMT
This thread contains all info and policies for Telnet. Also for those who are too lazy to find all this info.
Very little of this info I will have gotten from myself but I have done some improvements/fixes to almost everything. And the rest I had collected from other threads. I will provide links to those threads and credit to their creators. Some links provided might not be accessible for telnets.
I also apologize to those that have been mentioned in this post if your notifications have been spammed.
To start off, something everyone on every rank should know is the rules and info of the server, and be able to recall them or at least remember them. Some/all of these rules can be found on the dedicated TF website, found here.
This spoiler contains: Policies
This spoiler contains: The "Onlinemode/Adminmode States Policy".
Link to original thread can be found here.
This info has been kept the same, as it is a policy that is only kept the same unless changed or removed, but has been slightly improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy replaces any previous policy on the subject.
Onlinemode:
1. The normal server state for Total Freedom is onlinemode false (/onlinemode off command in Telnet) aka cracked. Telnets should routinely do /status to ensure the server state is false.
2. When the server is constantly full or if there is an on-going griefing attack against the server, the server be temporarily placed in onlinemode true (/onlinemode on command in Telnet) aka premium only mode.
3. When the server is no longer full (averaging less than 30 slots used over a 5 min period) or the security condition that required onlinemode on is no longer in effect, please return the server to the normal false (cracked) mode.
Adminmode:
1. From Telnet, Adminmode on can be used for very short duration by senior admins to restrict the server to admins only and kick off any non-admins. Here are the cases where it can be used:
a. A severe attack against the server or unknown server/plugin failure that cannot be resolved with onlinemode on. If this occurs, notify the owner as soon as possible.
b. For a quick huddle (approx 5-10 mins) by admins only to discuss an important admin issue by the senior (or owner) who issues the command.
c. For diagnostic and/or development testing purposes and the approval authority is either MarkByron, Madgeek or Darth.
d. A special occasion where admins can use the server alone for special events, celebrations, parties, or contests (duration no more than 2 hours). Request approval from the owner.
2. The server should be placed in Adminmode off as soon as the event that required it is finished.
{END OF SPOILER}
This spoiler contains: Chain of Command (who's in charge) and whom to call.
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
Chain of Command: "The order in which authority and power in an organization is wielded and delegated from top management to every employee at every level of the organization."
No, we're not Google or Microsoft with paid staff and employees but we do have an admin structure with different levels and I like things to be handled at the lowest level without me having to get involved in every issue and admins need to know who's in charge for handling problems and so forth. So here's some kind of a laundry list (not all-inclusive):
1. When there is more than one admin on the server (in-game or telnet), the admin in charge is the one with the highest rank (senior, telnet, or super). If there's more than one senior on, than the senior who is on the active roster and most senior (appointed to senior earliest) is in charge followed by honorary and semi-active seniors. If there's no seniors on the server, then the telnet admin that has been telnet the longest is in charge. If no telnets, then the super admin that's been super the longest is in charge. This means if there's any problem on the server, dispute between admins, etc. The admin that's had their rank the longest on at the time is the responsible person in charge to fix any problems and the others must follow. If an admin is logged in incognito (fake name - Notch, alt account, etc.) or they are flagged as impostors, they have no authority at all - that includes me (MarkByron).
2. If you have a complaint against a Super/Telnet admin (e.g. you don't like what they did on the server under rule 1 above, they're abusive, etc.), you bring it to the attention of an available senior admin or PM the Executive Officer (currently Lolz3842) via PM. I should not be the first person you contact. However, if you have a complaint against a senior admin or a problem with a lower ranking admin (that isn't being handled), then you should PM me (markbyron) directly. Also, don't air complaints in public or on the forums (Including skype group conversations) - handle these matters discreetly and without drama. Also, don't tweet me unless it's an emergency situation (e.g. admin going rogue on the server or forum).
3. For critical server problems (e.g. crash, frozen, .etc) that can't be resolved with a /stop, telnet.stopserver, send a tweet to @totalfreedommc or contact an available senior admin to get the server properly restored.
4. For server technical problems that are not critical (e.g. plugin malfunctions), post a forum message and/or PM the lead appropriate developer or lead developer (currently Prozza) via PM. If you're reporting a technical exploit, send me (markbyron) a PM or DM Tweet and don't otherwise announce it or post forum messages about it until I've responded.
5. For security matters (Confirmed DDoS, DOX, non-technical exploits, .etc), send a PM to the Security Officer (currently Sardenarin)
6. For forum problems, contact a forum moderator or the forum owner/manager - (Finest).
7. For build or map issues, post a forum message or contact the Creative Designer (currently Fluffasaurus_rex)
8. For general admin questions, support or training questions, post in the forums or contact a senior admin or the Executive Officer (currently Lolz3842).
(Keep in mind, this info is from July 10th, 2013, so I don't know if some of the people you should contact are correct or not.
Anyone that knows the correct person to contact, PM me where and who and i'll fix it).
{END OF SPOILER}
This spoiler contains: "Admin Server Rules - Respect & Authority".
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
While the subject rules at www.totalfreedom.me have not actually changed, I have clarified:
Respect between admins is essential on the server and on the forums; disputes, criticisms, and complaints bwtween admins are to be handled off-server and in the highest forum admin channel that you have access to (super, telnet, or senior) or via PM. The rule also applies to our forums (non-admin sections) or anywhere that the dispute might be viewed by the general public (e.g. Twitter)
So that means if I can read something in the system log where Admin A is disrespecting/criticizing/complaining about Admin B, then Admin A has violated the rules. Doesn't matter whether you used /mail, /r, /tell .etc Doesn't matter if your complaint is legit or not. If you actually have a legit complaint against another admin, it should be posted in the admin forums (still must be respectful) or you can PM seniors or myself (markbyron). The rule applies to all whether it's from senior to super or vice-versa.
At the same time, we're all going to get hot under the collar and violate this rule here and there (including me) but if you quickly make amends, it doesn't have to be a capital offense. The sanctions come when it turns into an admin war with endless raging and drama.
Super admins will follow the directions of senior admins with respect to any admin matter unless it violates server rules in which case a PM will be sent by the super admin to the owner.
So for example, a senior admin asks a super admin about an alleged problem and the super admin tells the senior admin off. That reflects utter stupidity on the part of the super admin because the senior admin has the power and authority to suspend the super admin. However, if a senior goes rogue (it's happened before, and could again), PM me (markbyron) with the evidence but the majority of the time, the senior is doing their job and if a super admin makes it hard on the senior, that's going to be a big problem.
(This info is as is with slight typing improvements by me, from December 7th, 2012).
{END OF SPOILER}
This spoiler contains: "Re-Super Policy - Must Read"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This is a new policy with respect to re-supering admins. If you're a senior admin or Telnet Admin, do not re-super a person unless you have verified them per our existing policy PLUS you must now check their profile on this forum and ensure they are listed as a super admin or higher. If they are listed just a 'member' or are not on the forum, do NOT re-super them. Instead, refer them to me (markbyron).
When somebody is removed from admin for causes other than inactivity, they will also lose their super admin status here on the forum or they will be booted from the forum. This is why you must verify that the person you are re-supering has a forum account in good super admin (or higher) standing.
Any questions - post a reply here.
(There's supposed to be another line of info here that links to another thread, but the thread link is 404, so I decided not to include it here).
{END OF SPOILER}
This spoiler contains: "Admin Family Member and Friend Policy"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy applies in cases where admins have family member(s) that share internet access and the family member(s) play Minecraft and come on the server. In some cases, the family member(s) might even share the same Minecraft account. This policy also covers situations where an admin shares internet access with a friend and the shared IP has admin privileges (the shared IP might be at the home of the admin or the home of the friend). Even if the policy doesn't apply to you, please keep track of all responses so that you know which admins have family members that use our server.
If this policy applies to you, please make a response to this thread that answers para 1, 2, and 3.
1. Post family member (or a friend) Minecraft account names that share the same internet connection (same IP) and who will be using our server.
2. Do any family members or friends share your Minecraft account? (Yes or No). If yes, what nickname can they use to identify themselves when logging on to the server?
3. Do you wish for us to permban a family member or friend that has or may likely grief our server? If so, list the name(s) but we cannot ban the IP since that would end up banning you as well. Also, this will not stop your family member griefer from using a mod client with a fake name when the server mode is false (see para 7).
If you answered question 1 with names, you should make all of them part of your admin crew, if you have one - see: (there's supposed to be a link here, but it's a dead link).
4. Your family members and friends are not admins even though they might have access to admin commands. However, they are allowed to use any admin command that applies ONLY to themselves (e.g. /opme) but no use of commands that would affect another player or otherwise disrupt the server. If they do, you can ask us to permban them using their name per para 3.
5. Your family member(s) or friends may apply for admin just as anybody else but they must meet the same quality standards.
6. If you answered yes to Question 2, your family member or friend must login and change their nick to a designated nickname that you answered in Question 2. Again, they are allowed to use any admin command that applies ONLY to themselves (e.g. /opme) but no use of commands that would affect another player or otherwise disrupt the server.
7. In all cases, if a family member or friend uses a shared Minecraft account or IP to grief or abuse as admin, you will be subject to sanctions including loss of admin or even permban. That might sound harsh, but we are not responsible for your dysfunctional family members - you are.
8. In the case where an admin is using a friend's IP that is supered on the request of the admin, the admin should request removal of that IP from super access when the admin no longer intends to use his/her friend's IP.
(Info is as is from December 24th 2012).
{END OF SPOILER}
This spoiler contains: "Adminworld Policy"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
1. Adminworld is designed to be a private & peaceful getaway for our hardworking admins to build or just take a break from the normal chaos found on the main maps or flatlands.
2. Rules regarding respect and privacy are no less applicable in Adminworld and admins who break the rules or grief while in Adminworld are subject to sanctions including long suspensions or removal.
3. Admins may bring in guests for supervised visits, but the guests must be with the admin at all times. Should a guest be found in Adminworld without the immediate presence of the host admin or if they break the rules while in Adminworld, the guest is subject to being perm-banned by name and the admin will be fully responsible under rule 2 above. Guests are IP matched friends or family or selected guests that can be authorized per Madgeek's command.
Command: /adminworld [<guest> [list | [[add | delete | del] <user>]]].
Info: Guests will persist on the guest list by username only, until the server restarts OR the admin that added them gets de-super'd.
{END OF SPOILER}
This spoiler contains: "Disguise and Invisibility"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
Admins regularly ask about this and so I'm providing the following:
It's been the long tradition of TF to allow disguise under the spirit of Total Freedom provided players don't abuse the privilege per our banning protocols. We also allow the use of potions including invisibility but because of the high potential for abuse, admins are allowed to use /invis smite in the same way that /uall is done.
I might be wrong here but I believe the use of /invis smite to mass remove invisibility was implemented because invisibility couldn't otherwise be easily removed. If there was a way that /uall could also remove invisibility, that would be preferable but that's an issue for devs to address. In any case, use of invisibility is not prohibited but I do give admins the latitude to prevent its misuse. I've added a rule 20 to the banning protocols to address this.
For admins that are concerned, the name of our server is Total Freedom server and we have allowed players the freedom to do things that almost every server (inc. associated servers) don't allow, and we try to live up to our name without becoming Total Anarchy. I recognize it makes admins jobs more difficult of course, but that's how it goes in the real world; where there's freedom, the cops have a hard job.
{END OF SPOILER}
This spoiler contains: "Admin Absences, Re-Super Policy, and Resigning / Quitting"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
The revised subject policy has been streamlined nd replaces all previous policies for the subject.
1. An admin that plans on being absent from the server for greater than 5 days should post an inactivity notice as a courtesy to other admins and myself. It's not required that the admin provides a reason but you should state an estimated return or state indefinite if unsure that you'll return. Regardless of posting the notice, admins are subject to automatically emoveal from server admin after 5 days and removal from forum admin if not logged into the forum for greater than 30 days.
2. If an admin loses server admin for inactivity but is still listed as a forum admin, they can be re-supered by any other admin as long as they are still listed as a forum admin - ensure verification is done to prevent giving admin to a poser. If an admin loses server and forum admin for inactivity, they must apply for reinstatement and should reference their inactivity notice to expedite approval.
3. Admins that are absent for short periods of less than 5 days do not need to post a notice - it's understandable that homework or work will keep you away for short periods.
4. Resignations or quitting. There is NO need to resign or quit on Total Freedom - the easiest option here is to post a drama free inactivity notice stating that you'll be going away for an indefinite period and your admin perms will be automatically removed in due time. Do not stir up trouble or cause drama in your posting (admin conduct rules always apply) hoever you should PM myself or Lolz if you're resigning due to a problem with another admin(s) so that we can try to resolve the problem. If you change your mind and wish to return, you're subject to the same rules above (1 & 2) with no adverse mark on your record. Very easy.
5. Rage quitting or drama resignations. If you fail to follow rule 4 and cause a public scene, your post will be deleted, you will be suspended & removed, and you'll likely end up perm banned regardless of what you're raging about. You will also have to apply for reinstatement if you wish to get admin back along and it won't be nearly as easy if you had simply followed rule 4.
Any questions about this revised policy, please reply here.
{END OF SPOILER}
This spoiler contains: "Admin Suspension Procedures" (2nd January 2014)
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy is for senior admins as they have the authority to temporarily suspend super and telnet admins but is being posted in the super admin section as info for all admins. This policy replaces all previous policies on the subject.
If a senior admin temporarily removes a member from super or telnet admin status due to misconduct or rogue activity, that senior admin must post a record of it in this section and send a tweet to @totalfreedommc as soon as possible. You do not need to post messages for removals based on inactivity, resignation requests (there should be a resignation message though), or removals made by mistake unless you weren't able to re-super them. Also, you do not need to include slap down removes made for a minor disciplinary issue where you re-supered them within a short time (e.g. 10 mins) but if it becomes a habit, you should probably post a record of it in the senior admin section. Here is the template that should be used when suspending an admin:
Subject should be "Admin Suspended - name (Minecraft Name)"
1. Approx Date and time you suspended the admin.
2. Why you suspended the admin - include relevant log entries.
3. Did you attempt to correct the admin before suspending him/her?
4. Did you notify the admin that you removed them from and why?
5. If you answered no to either 3 or 4, please explain. Except in extreme cases such as the admin going rogue and trying to crash the server or if you were undercover, I would expect yes answers for both.
Note: While a senior admin can temporarily suspend super or telnet admins, the length of the suspension for a Telnet admin is up to the owner or in the case of super admins, the owner or the Executive Admins. Executive Admins have the authority to permanently remove a super admin but this does not preclude an admin from appealing the removal.
Note: If you were undercover (using an alt and not flagged by the server as an admin) and you observe admin misconduct requireing suspension, you need not reveal your undercover alt identity. Simply go on Telnet, remove & ban the admin, and post the log entries via PM to markbyron. Note that being undercover does not give you the right to provoke or entrap the admin - if you post a suspension and I see inappropriate activity by your alt, you might be the one appealing to a suspension.
{END OF SPOILER}
This spoiler contains: "Banning Protocol for Impostors - Don't ban admins!"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
It seems that some admins are not following the banning protocols and banning admins who change IPs without giving them time to verify. To quote the protocol:
"Owner or Admin is flagged as impostor. Immediately tell the person they have been flagged, deop them, and ask them to verify via Twitter, TotalFreedom Forum, Skype, or if they are senior, to op themselves. If they don't comply within 5 minutes, temp ban them for 5 minute intervals until they comply. If you're certain that the person logging in is an impostor (e.g. the impostor starts griefing), then tempban but assume innocence before guilt."
Remember, assume innocence before guilt and use temp ban AFTER 5 minutes.
{END OF SPOILER}
{END OF SPOILER}
-----------------------------------------------------------------------------------------------------------------------------------------
This spoiler contains: Other Useful Info
This spoiler contains: All commands for telnet as of Jan 28th 2014.
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Wild1145
Any commands in PURPLE are Senior commands, meaning only senior admins may use them! And any commands in GREEN are commands I am unsure of being available to both Telnet and Senior.
Adminmode [On | Off] = Toggles the server's admin mode on and off (A server notice will be displayed when this command is used) - On = Activates admin mode kicking all non admins and stopping them from connecting
- Off = Allows all users to connect again!
Do not use this command except in extreme circumstances such as mass attacks that can't be controlled with onlinemode true, and ensure that as soon as the incident is dealt with, it is reversed back to adminmode off!
Rawsay = Sends chat with NO formatting - You may use standard bukkit colour codes when sending messages
Csay = Sends a message in the game, making it look similar to normal chat.
Ops Purge = Purges all the ops in the ops file, this is not able to be undone.
nonuke = This manages the anti-nuking system, this is already pre-set in the configs, however can be overridden from this command.
Saconfig = Manages the super admin list
- Add = Adds a member to the super admin list
- Del / delete / Similar "Stop" commands = Removes a super admin from admin
- Clean = Removes any inactive supers.
Stop = Stops the server and forces restart. Do NOT use this unless the server is locked up or extremely lagged. If the Stop command doesn't actually stop the server or the server doesn't restart, you'll have to notify a senior or the owner to do a full restart. You can now also use telnet.stopserver (See below)
Wipeflatlands = Does what it says on the tin, it wipes the flatlands however due to the way the server works, it will kick everyone, stop the server then wipe the flatlands. You will need to start the server using the clanforge system after it is completed.
Onlinemode = Changes the player validation to On (true) or Off (false)
- Off = Allows all non-premium accounts to connect and this is the preferred mode for Total Freedom. If a poser tries to login as one of the admins or an admin is using a new IP, you'll get an impostor alert and you'll have to verify their identity using the forum, Skype, or Twitter.
- On = Prevents any non premium accounts from connecting to the server. This might be temporarily needed when there is login bot attack or there's a griefer team doing mass attacks using alts. This may also be activated if the server is full and when activated there are not less than 25 players online.
Doom: This is for the rogue admins (Or annoying players ), it will remove the admin from their admin status before banning them.
Lockup: This will disable the player from being able to do ANYTHING in the game until they are unlocked (Very Evil)!
Lockdown: Locks the server down, stopping all new players from being able to connect and play, also only use this if mass griefing attack has been launched on the server!
telnet.log: Stops logging of any commands (as of Jan 28th 2014, xXWilee999Xx says its still a little buggy, so don't expect the world yet).
More commands that start with telnet. can be found with telnet.help
Link to the thread about these commands can be found here.
{END OF SPOILER}
This spoiler contains: Easy common sense info and a small piece of advice.
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Myself.
Here's some info that you should probably know.
An easy to remember common sense thing you should really know, is to NEVER use /reload (alias: /rl). The only reasons I would accept the use of this without me questioning or telling you not to use it again, is if there's a random plugin issue. All this command does is reload the plugins and nothing else, the negative side-effects of this command is that it can and will always lag the server. So don't be doing this if the server is having lag issues or currently lagging, as it can/will contribute to making the server more likely to crash by putting more stress on the server. If this doesn't reload the plugins and fix the issue the first or second time, then ask a telnet clan admin or higher to restart the server for you. Apparently you can restart the server on your own using telnet.stop but the last time I tried, it only stopped the server, so take caution.
Also, For plugin malfunctions that can't be fixed with a restart, post a forum message in the correct section and/or PM the lead appropriate developer or lead developer (currently Prozza) via PM.
Also, if you're on the server via MC Client, I personally find it useful to have Telnet open at the same time. So that way instead of looking in the logs for something that happened, I can quickly look on telnet and, for example, I see a player grief with world-edit or nick someone something offensive. I can then instantly punish that player accordingly.
There's probably more I've got to say, but I either forgot or can't come up with at the moment.
{END OF SPOILER}
This spoiler contains: Links and info about the custom telnet clients.
Link to xXWilee999Xx's original thread can be found here and Madgeek's here.
This info is only shortened and slightly changed/improved, as there is not much useful info to provide, as all can be found on the original threads.
Credit goes to: xXWilee999Xx & @madgeek.
FYI, the IP for telnet is: tf.madgeekonline.com
And the port can be found in the telnet lounge.
First off, Madgeek's telnet client.
Not much info to include for this, so i'll just provide a link here.
And now, xXWilee999Xx's telnet client.
BukkitTelnetClient+ is xXWilee999Xx's fork of Madgeek's BukkitTelnetClient, which has a bit easier to see display than BukkitTelnetClient. If you don't enjoy the blinding white background with BTC, you'll no longer have that problem with BTC+.
The rest of the info can be found on the original thread here.
{END OF SPOILER}
This spoiler contains: Tips on how to get a higher chance on earning Telnet.
Link to original thread can be found here.
This info has been slightly improved and modified by putting in my own thoughts in some parts.
Credit goes to: @striikr123.
Hello, fellow Supers, Telnets and possibly even Seniors.
I would not just like to say that over the past month that i've been Super, I've seen many Telnet apps. Some of which have been approved and some have not, but over that month I've seen a few things that I think any super applying for Telnet should change or improve on.
1: Apply when you think you're ready.
From what I've seen over the past month, is people applying as soon as they possibly can. This is fine, but if you wait a little and get more experienced and get familiar with the rank and become appreciated having you on the server by the majority of people, you'll have a much higher chance of getting the rank. My advice would be to apply when you think you're ready. I say that you shouldn't apply as soon as you possibly can. Wait 1-2 months before applying. This can, of course get you more experience, but it can also help you to get to know other admins (which I believe is important), maybe even get them to like you more, which will give you a much higher chance of getting Telnet.
2: Make sure you know what you're doing.
I've also seen some people apply, who have absolutely no idea what Telnet is and/or what the point of it is. My advice would be to look at the videos and posts that Mark and Madgeek have put up and get to know what you'll be doing as Telnet. Don't just jump right into the application, get accepted and have absolutely no idea what you're doing. It will ruin your reputation and you might have a chance of losing your position because of it. So in all, study what your job as a telnet is before you get all caught up in it.
3: Know the responsibility.
Make sure that as Telnet, you're ready to take on the much higher level of responsibility. It is important to know that as a telnet admin, you now have a much higher amount of responsibility than you did as Super Admin, and can/will be slightly overwhelming at times. But, before you apply, start training and improving on your ability on handling more than one or two things at once without getting stressed. Because if you don't, you might end up messing up, and this is never a good thing, under any circumstance.
4: Make sure that you KNOW it won't get denied straight away.
You don't want to apply, feeling really optimistic that you'll get accepted after you fall asleep, and wake up then having found out that you've got 10 objections, 2 neutrals and no vouches. Make sure that you know that it won't get denied. This doesn't mean going around spamming "Should I Apply" threads. You should know that you will get a good rating from other admins if you avoid doing this. More ways to avoid getting into a situation like this will be covered in the next number.
5: Ways to avoid getting denied.
Ways to avoid getting denied would simply be common sense. One of the best ways is to wait a bit before applying and getting to know the admins. Don't annoy them asking if they can vouch for you or recommend you. That will make them want to object even more, and probably should too, since business should come before friendship in this case. Be nice to your fellow admins and help them when they need it. This can get you a much higher chance of getting vouches on your application.
---------------------------------------------------------------------------------------------------------------------------------------
Thank you and you're welcome for taking your time to read this. I hope it helps all ranks to reach their next rank.
{END OF SPOILER}
This spoiler contains: "How to use /wm or /wileemanage"
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Polaris Seltzeris.
Some admins are confused about /wm and what it does.
/wm is my personal command with some fun/handy commands to use.
If you wanna know what commands you can use and what they do, go on the server and use /wm help or /wileemanage help.
This command includes banning commands and other administration commands.
This command has lots of old disdfreedom commands that were missed by serverl admins.
If you want to suggest a new command, then make a suggestion on the forums.
Feel free to code your own stuff into my plugin through a pull request: github.com/TotalFreedom/MobArena
Issues are also appreciated, to note bugs or anything.
Enjoy!
{END OF SPOILER}
{END OF SPOILER}
Very little of this info I will have gotten from myself but I have done some improvements/fixes to almost everything. And the rest I had collected from other threads. I will provide links to those threads and credit to their creators. Some links provided might not be accessible for telnets.
I also apologize to those that have been mentioned in this post if your notifications have been spammed.
To start off, something everyone on every rank should know is the rules and info of the server, and be able to recall them or at least remember them. Some/all of these rules can be found on the dedicated TF website, found here.
This spoiler contains: Policies
This spoiler contains: The "Onlinemode/Adminmode States Policy".
Link to original thread can be found here.
This info has been kept the same, as it is a policy that is only kept the same unless changed or removed, but has been slightly improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy replaces any previous policy on the subject.
Onlinemode:
1. The normal server state for Total Freedom is onlinemode false (/onlinemode off command in Telnet) aka cracked. Telnets should routinely do /status to ensure the server state is false.
2. When the server is constantly full or if there is an on-going griefing attack against the server, the server be temporarily placed in onlinemode true (/onlinemode on command in Telnet) aka premium only mode.
3. When the server is no longer full (averaging less than 30 slots used over a 5 min period) or the security condition that required onlinemode on is no longer in effect, please return the server to the normal false (cracked) mode.
Adminmode:
1. From Telnet, Adminmode on can be used for very short duration by senior admins to restrict the server to admins only and kick off any non-admins. Here are the cases where it can be used:
a. A severe attack against the server or unknown server/plugin failure that cannot be resolved with onlinemode on. If this occurs, notify the owner as soon as possible.
b. For a quick huddle (approx 5-10 mins) by admins only to discuss an important admin issue by the senior (or owner) who issues the command.
c. For diagnostic and/or development testing purposes and the approval authority is either MarkByron, Madgeek or Darth.
d. A special occasion where admins can use the server alone for special events, celebrations, parties, or contests (duration no more than 2 hours). Request approval from the owner.
2. The server should be placed in Adminmode off as soon as the event that required it is finished.
{END OF SPOILER}
This spoiler contains: Chain of Command (who's in charge) and whom to call.
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
Chain of Command: "The order in which authority and power in an organization is wielded and delegated from top management to every employee at every level of the organization."
No, we're not Google or Microsoft with paid staff and employees but we do have an admin structure with different levels and I like things to be handled at the lowest level without me having to get involved in every issue and admins need to know who's in charge for handling problems and so forth. So here's some kind of a laundry list (not all-inclusive):
1. When there is more than one admin on the server (in-game or telnet), the admin in charge is the one with the highest rank (senior, telnet, or super). If there's more than one senior on, than the senior who is on the active roster and most senior (appointed to senior earliest) is in charge followed by honorary and semi-active seniors. If there's no seniors on the server, then the telnet admin that has been telnet the longest is in charge. If no telnets, then the super admin that's been super the longest is in charge. This means if there's any problem on the server, dispute between admins, etc. The admin that's had their rank the longest on at the time is the responsible person in charge to fix any problems and the others must follow. If an admin is logged in incognito (fake name - Notch, alt account, etc.) or they are flagged as impostors, they have no authority at all - that includes me (MarkByron).
2. If you have a complaint against a Super/Telnet admin (e.g. you don't like what they did on the server under rule 1 above, they're abusive, etc.), you bring it to the attention of an available senior admin or PM the Executive Officer (currently Lolz3842) via PM. I should not be the first person you contact. However, if you have a complaint against a senior admin or a problem with a lower ranking admin (that isn't being handled), then you should PM me (markbyron) directly. Also, don't air complaints in public or on the forums (Including skype group conversations) - handle these matters discreetly and without drama. Also, don't tweet me unless it's an emergency situation (e.g. admin going rogue on the server or forum).
3. For critical server problems (e.g. crash, frozen, .etc) that can't be resolved with a /stop, telnet.stopserver, send a tweet to @totalfreedommc or contact an available senior admin to get the server properly restored.
4. For server technical problems that are not critical (e.g. plugin malfunctions), post a forum message and/or PM the lead appropriate developer or lead developer (currently Prozza) via PM. If you're reporting a technical exploit, send me (markbyron) a PM or DM Tweet and don't otherwise announce it or post forum messages about it until I've responded.
5. For security matters (Confirmed DDoS, DOX, non-technical exploits, .etc), send a PM to the Security Officer (currently Sardenarin)
6. For forum problems, contact a forum moderator or the forum owner/manager - (Finest).
7. For build or map issues, post a forum message or contact the Creative Designer (currently Fluffasaurus_rex)
8. For general admin questions, support or training questions, post in the forums or contact a senior admin or the Executive Officer (currently Lolz3842).
(Keep in mind, this info is from July 10th, 2013, so I don't know if some of the people you should contact are correct or not.
Anyone that knows the correct person to contact, PM me where and who and i'll fix it).
{END OF SPOILER}
This spoiler contains: "Admin Server Rules - Respect & Authority".
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
While the subject rules at www.totalfreedom.me have not actually changed, I have clarified:
Respect between admins is essential on the server and on the forums; disputes, criticisms, and complaints bwtween admins are to be handled off-server and in the highest forum admin channel that you have access to (super, telnet, or senior) or via PM. The rule also applies to our forums (non-admin sections) or anywhere that the dispute might be viewed by the general public (e.g. Twitter)
So that means if I can read something in the system log where Admin A is disrespecting/criticizing/complaining about Admin B, then Admin A has violated the rules. Doesn't matter whether you used /mail, /r, /tell .etc Doesn't matter if your complaint is legit or not. If you actually have a legit complaint against another admin, it should be posted in the admin forums (still must be respectful) or you can PM seniors or myself (markbyron). The rule applies to all whether it's from senior to super or vice-versa.
At the same time, we're all going to get hot under the collar and violate this rule here and there (including me) but if you quickly make amends, it doesn't have to be a capital offense. The sanctions come when it turns into an admin war with endless raging and drama.
Super admins will follow the directions of senior admins with respect to any admin matter unless it violates server rules in which case a PM will be sent by the super admin to the owner.
So for example, a senior admin asks a super admin about an alleged problem and the super admin tells the senior admin off. That reflects utter stupidity on the part of the super admin because the senior admin has the power and authority to suspend the super admin. However, if a senior goes rogue (it's happened before, and could again), PM me (markbyron) with the evidence but the majority of the time, the senior is doing their job and if a super admin makes it hard on the senior, that's going to be a big problem.
(This info is as is with slight typing improvements by me, from December 7th, 2012).
{END OF SPOILER}
This spoiler contains: "Re-Super Policy - Must Read"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This is a new policy with respect to re-supering admins. If you're a senior admin or Telnet Admin, do not re-super a person unless you have verified them per our existing policy PLUS you must now check their profile on this forum and ensure they are listed as a super admin or higher. If they are listed just a 'member' or are not on the forum, do NOT re-super them. Instead, refer them to me (markbyron).
When somebody is removed from admin for causes other than inactivity, they will also lose their super admin status here on the forum or they will be booted from the forum. This is why you must verify that the person you are re-supering has a forum account in good super admin (or higher) standing.
Any questions - post a reply here.
(There's supposed to be another line of info here that links to another thread, but the thread link is 404, so I decided not to include it here).
{END OF SPOILER}
This spoiler contains: "Admin Family Member and Friend Policy"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy applies in cases where admins have family member(s) that share internet access and the family member(s) play Minecraft and come on the server. In some cases, the family member(s) might even share the same Minecraft account. This policy also covers situations where an admin shares internet access with a friend and the shared IP has admin privileges (the shared IP might be at the home of the admin or the home of the friend). Even if the policy doesn't apply to you, please keep track of all responses so that you know which admins have family members that use our server.
If this policy applies to you, please make a response to this thread that answers para 1, 2, and 3.
1. Post family member (or a friend) Minecraft account names that share the same internet connection (same IP) and who will be using our server.
2. Do any family members or friends share your Minecraft account? (Yes or No). If yes, what nickname can they use to identify themselves when logging on to the server?
3. Do you wish for us to permban a family member or friend that has or may likely grief our server? If so, list the name(s) but we cannot ban the IP since that would end up banning you as well. Also, this will not stop your family member griefer from using a mod client with a fake name when the server mode is false (see para 7).
If you answered question 1 with names, you should make all of them part of your admin crew, if you have one - see: (there's supposed to be a link here, but it's a dead link).
4. Your family members and friends are not admins even though they might have access to admin commands. However, they are allowed to use any admin command that applies ONLY to themselves (e.g. /opme) but no use of commands that would affect another player or otherwise disrupt the server. If they do, you can ask us to permban them using their name per para 3.
5. Your family member(s) or friends may apply for admin just as anybody else but they must meet the same quality standards.
6. If you answered yes to Question 2, your family member or friend must login and change their nick to a designated nickname that you answered in Question 2. Again, they are allowed to use any admin command that applies ONLY to themselves (e.g. /opme) but no use of commands that would affect another player or otherwise disrupt the server.
7. In all cases, if a family member or friend uses a shared Minecraft account or IP to grief or abuse as admin, you will be subject to sanctions including loss of admin or even permban. That might sound harsh, but we are not responsible for your dysfunctional family members - you are.
8. In the case where an admin is using a friend's IP that is supered on the request of the admin, the admin should request removal of that IP from super access when the admin no longer intends to use his/her friend's IP.
(Info is as is from December 24th 2012).
{END OF SPOILER}
This spoiler contains: "Adminworld Policy"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
1. Adminworld is designed to be a private & peaceful getaway for our hardworking admins to build or just take a break from the normal chaos found on the main maps or flatlands.
2. Rules regarding respect and privacy are no less applicable in Adminworld and admins who break the rules or grief while in Adminworld are subject to sanctions including long suspensions or removal.
3. Admins may bring in guests for supervised visits, but the guests must be with the admin at all times. Should a guest be found in Adminworld without the immediate presence of the host admin or if they break the rules while in Adminworld, the guest is subject to being perm-banned by name and the admin will be fully responsible under rule 2 above. Guests are IP matched friends or family or selected guests that can be authorized per Madgeek's command.
Command: /adminworld [<guest> [list | [[add | delete | del] <user>]]].
Info: Guests will persist on the guest list by username only, until the server restarts OR the admin that added them gets de-super'd.
{END OF SPOILER}
This spoiler contains: "Disguise and Invisibility"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
Admins regularly ask about this and so I'm providing the following:
It's been the long tradition of TF to allow disguise under the spirit of Total Freedom provided players don't abuse the privilege per our banning protocols. We also allow the use of potions including invisibility but because of the high potential for abuse, admins are allowed to use /invis smite in the same way that /uall is done.
I might be wrong here but I believe the use of /invis smite to mass remove invisibility was implemented because invisibility couldn't otherwise be easily removed. If there was a way that /uall could also remove invisibility, that would be preferable but that's an issue for devs to address. In any case, use of invisibility is not prohibited but I do give admins the latitude to prevent its misuse. I've added a rule 20 to the banning protocols to address this.
For admins that are concerned, the name of our server is Total Freedom server and we have allowed players the freedom to do things that almost every server (inc. associated servers) don't allow, and we try to live up to our name without becoming Total Anarchy. I recognize it makes admins jobs more difficult of course, but that's how it goes in the real world; where there's freedom, the cops have a hard job.
{END OF SPOILER}
This spoiler contains: "Admin Absences, Re-Super Policy, and Resigning / Quitting"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
The revised subject policy has been streamlined nd replaces all previous policies for the subject.
1. An admin that plans on being absent from the server for greater than 5 days should post an inactivity notice as a courtesy to other admins and myself. It's not required that the admin provides a reason but you should state an estimated return or state indefinite if unsure that you'll return. Regardless of posting the notice, admins are subject to automatically emoveal from server admin after 5 days and removal from forum admin if not logged into the forum for greater than 30 days.
2. If an admin loses server admin for inactivity but is still listed as a forum admin, they can be re-supered by any other admin as long as they are still listed as a forum admin - ensure verification is done to prevent giving admin to a poser. If an admin loses server and forum admin for inactivity, they must apply for reinstatement and should reference their inactivity notice to expedite approval.
3. Admins that are absent for short periods of less than 5 days do not need to post a notice - it's understandable that homework or work will keep you away for short periods.
4. Resignations or quitting. There is NO need to resign or quit on Total Freedom - the easiest option here is to post a drama free inactivity notice stating that you'll be going away for an indefinite period and your admin perms will be automatically removed in due time. Do not stir up trouble or cause drama in your posting (admin conduct rules always apply) hoever you should PM myself or Lolz if you're resigning due to a problem with another admin(s) so that we can try to resolve the problem. If you change your mind and wish to return, you're subject to the same rules above (1 & 2) with no adverse mark on your record. Very easy.
5. Rage quitting or drama resignations. If you fail to follow rule 4 and cause a public scene, your post will be deleted, you will be suspended & removed, and you'll likely end up perm banned regardless of what you're raging about. You will also have to apply for reinstatement if you wish to get admin back along and it won't be nearly as easy if you had simply followed rule 4.
Any questions about this revised policy, please reply here.
{END OF SPOILER}
This spoiler contains: "Admin Suspension Procedures" (2nd January 2014)
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
This policy is for senior admins as they have the authority to temporarily suspend super and telnet admins but is being posted in the super admin section as info for all admins. This policy replaces all previous policies on the subject.
If a senior admin temporarily removes a member from super or telnet admin status due to misconduct or rogue activity, that senior admin must post a record of it in this section and send a tweet to @totalfreedommc as soon as possible. You do not need to post messages for removals based on inactivity, resignation requests (there should be a resignation message though), or removals made by mistake unless you weren't able to re-super them. Also, you do not need to include slap down removes made for a minor disciplinary issue where you re-supered them within a short time (e.g. 10 mins) but if it becomes a habit, you should probably post a record of it in the senior admin section. Here is the template that should be used when suspending an admin:
Subject should be "Admin Suspended - name (Minecraft Name)"
1. Approx Date and time you suspended the admin.
2. Why you suspended the admin - include relevant log entries.
3. Did you attempt to correct the admin before suspending him/her?
4. Did you notify the admin that you removed them from and why?
5. If you answered no to either 3 or 4, please explain. Except in extreme cases such as the admin going rogue and trying to crash the server or if you were undercover, I would expect yes answers for both.
Note: While a senior admin can temporarily suspend super or telnet admins, the length of the suspension for a Telnet admin is up to the owner or in the case of super admins, the owner or the Executive Admins. Executive Admins have the authority to permanently remove a super admin but this does not preclude an admin from appealing the removal.
Note: If you were undercover (using an alt and not flagged by the server as an admin) and you observe admin misconduct requireing suspension, you need not reveal your undercover alt identity. Simply go on Telnet, remove & ban the admin, and post the log entries via PM to markbyron. Note that being undercover does not give you the right to provoke or entrap the admin - if you post a suspension and I see inappropriate activity by your alt, you might be the one appealing to a suspension.
{END OF SPOILER}
This spoiler contains: "Banning Protocol for Impostors - Don't ban admins!"
Link to original thread can be found here.
This info has been improved by fixing typing mistakes.
Credit goes to: markbyron.
It seems that some admins are not following the banning protocols and banning admins who change IPs without giving them time to verify. To quote the protocol:
"Owner or Admin is flagged as impostor. Immediately tell the person they have been flagged, deop them, and ask them to verify via Twitter, TotalFreedom Forum, Skype, or if they are senior, to op themselves. If they don't comply within 5 minutes, temp ban them for 5 minute intervals until they comply. If you're certain that the person logging in is an impostor (e.g. the impostor starts griefing), then tempban but assume innocence before guilt."
Remember, assume innocence before guilt and use temp ban AFTER 5 minutes.
{END OF SPOILER}
{END OF SPOILER}
-----------------------------------------------------------------------------------------------------------------------------------------
This spoiler contains: Other Useful Info
This spoiler contains: All commands for telnet as of Jan 28th 2014.
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Wild1145
Any commands in PURPLE are Senior commands, meaning only senior admins may use them! And any commands in GREEN are commands I am unsure of being available to both Telnet and Senior.
Adminmode [On | Off] = Toggles the server's admin mode on and off (A server notice will be displayed when this command is used) - On = Activates admin mode kicking all non admins and stopping them from connecting
- Off = Allows all users to connect again!
Do not use this command except in extreme circumstances such as mass attacks that can't be controlled with onlinemode true, and ensure that as soon as the incident is dealt with, it is reversed back to adminmode off!
Rawsay = Sends chat with NO formatting - You may use standard bukkit colour codes when sending messages
Csay = Sends a message in the game, making it look similar to normal chat.
Ops Purge = Purges all the ops in the ops file, this is not able to be undone.
nonuke = This manages the anti-nuking system, this is already pre-set in the configs, however can be overridden from this command.
Saconfig = Manages the super admin list
- Add = Adds a member to the super admin list
- Del / delete / Similar "Stop" commands = Removes a super admin from admin
- Clean = Removes any inactive supers.
Stop = Stops the server and forces restart. Do NOT use this unless the server is locked up or extremely lagged. If the Stop command doesn't actually stop the server or the server doesn't restart, you'll have to notify a senior or the owner to do a full restart. You can now also use telnet.stopserver (See below)
Wipeflatlands = Does what it says on the tin, it wipes the flatlands however due to the way the server works, it will kick everyone, stop the server then wipe the flatlands. You will need to start the server using the clanforge system after it is completed.
Onlinemode = Changes the player validation to On (true) or Off (false)
- Off = Allows all non-premium accounts to connect and this is the preferred mode for Total Freedom. If a poser tries to login as one of the admins or an admin is using a new IP, you'll get an impostor alert and you'll have to verify their identity using the forum, Skype, or Twitter.
- On = Prevents any non premium accounts from connecting to the server. This might be temporarily needed when there is login bot attack or there's a griefer team doing mass attacks using alts. This may also be activated if the server is full and when activated there are not less than 25 players online.
Doom: This is for the rogue admins (Or annoying players ), it will remove the admin from their admin status before banning them.
Lockup: This will disable the player from being able to do ANYTHING in the game until they are unlocked (Very Evil)!
Lockdown: Locks the server down, stopping all new players from being able to connect and play, also only use this if mass griefing attack has been launched on the server!
telnet.log: Stops logging of any commands (as of Jan 28th 2014, xXWilee999Xx says its still a little buggy, so don't expect the world yet).
More commands that start with telnet. can be found with telnet.help
Link to the thread about these commands can be found here.
{END OF SPOILER}
This spoiler contains: Easy common sense info and a small piece of advice.
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Myself.
Here's some info that you should probably know.
An easy to remember common sense thing you should really know, is to NEVER use /reload (alias: /rl). The only reasons I would accept the use of this without me questioning or telling you not to use it again, is if there's a random plugin issue. All this command does is reload the plugins and nothing else, the negative side-effects of this command is that it can and will always lag the server. So don't be doing this if the server is having lag issues or currently lagging, as it can/will contribute to making the server more likely to crash by putting more stress on the server. If this doesn't reload the plugins and fix the issue the first or second time, then ask a telnet clan admin or higher to restart the server for you. Apparently you can restart the server on your own using telnet.stop but the last time I tried, it only stopped the server, so take caution.
Also, For plugin malfunctions that can't be fixed with a restart, post a forum message in the correct section and/or PM the lead appropriate developer or lead developer (currently Prozza) via PM.
Also, if you're on the server via MC Client, I personally find it useful to have Telnet open at the same time. So that way instead of looking in the logs for something that happened, I can quickly look on telnet and, for example, I see a player grief with world-edit or nick someone something offensive. I can then instantly punish that player accordingly.
There's probably more I've got to say, but I either forgot or can't come up with at the moment.
{END OF SPOILER}
This spoiler contains: Links and info about the custom telnet clients.
Link to xXWilee999Xx's original thread can be found here and Madgeek's here.
This info is only shortened and slightly changed/improved, as there is not much useful info to provide, as all can be found on the original threads.
Credit goes to: xXWilee999Xx & @madgeek.
FYI, the IP for telnet is: tf.madgeekonline.com
And the port can be found in the telnet lounge.
First off, Madgeek's telnet client.
Not much info to include for this, so i'll just provide a link here.
And now, xXWilee999Xx's telnet client.
BukkitTelnetClient+ is xXWilee999Xx's fork of Madgeek's BukkitTelnetClient, which has a bit easier to see display than BukkitTelnetClient. If you don't enjoy the blinding white background with BTC, you'll no longer have that problem with BTC+.
The rest of the info can be found on the original thread here.
{END OF SPOILER}
This spoiler contains: Tips on how to get a higher chance on earning Telnet.
Link to original thread can be found here.
This info has been slightly improved and modified by putting in my own thoughts in some parts.
Credit goes to: @striikr123.
Hello, fellow Supers, Telnets and possibly even Seniors.
I would not just like to say that over the past month that i've been Super, I've seen many Telnet apps. Some of which have been approved and some have not, but over that month I've seen a few things that I think any super applying for Telnet should change or improve on.
1: Apply when you think you're ready.
From what I've seen over the past month, is people applying as soon as they possibly can. This is fine, but if you wait a little and get more experienced and get familiar with the rank and become appreciated having you on the server by the majority of people, you'll have a much higher chance of getting the rank. My advice would be to apply when you think you're ready. I say that you shouldn't apply as soon as you possibly can. Wait 1-2 months before applying. This can, of course get you more experience, but it can also help you to get to know other admins (which I believe is important), maybe even get them to like you more, which will give you a much higher chance of getting Telnet.
2: Make sure you know what you're doing.
I've also seen some people apply, who have absolutely no idea what Telnet is and/or what the point of it is. My advice would be to look at the videos and posts that Mark and Madgeek have put up and get to know what you'll be doing as Telnet. Don't just jump right into the application, get accepted and have absolutely no idea what you're doing. It will ruin your reputation and you might have a chance of losing your position because of it. So in all, study what your job as a telnet is before you get all caught up in it.
3: Know the responsibility.
Make sure that as Telnet, you're ready to take on the much higher level of responsibility. It is important to know that as a telnet admin, you now have a much higher amount of responsibility than you did as Super Admin, and can/will be slightly overwhelming at times. But, before you apply, start training and improving on your ability on handling more than one or two things at once without getting stressed. Because if you don't, you might end up messing up, and this is never a good thing, under any circumstance.
4: Make sure that you KNOW it won't get denied straight away.
You don't want to apply, feeling really optimistic that you'll get accepted after you fall asleep, and wake up then having found out that you've got 10 objections, 2 neutrals and no vouches. Make sure that you know that it won't get denied. This doesn't mean going around spamming "Should I Apply" threads. You should know that you will get a good rating from other admins if you avoid doing this. More ways to avoid getting into a situation like this will be covered in the next number.
5: Ways to avoid getting denied.
Ways to avoid getting denied would simply be common sense. One of the best ways is to wait a bit before applying and getting to know the admins. Don't annoy them asking if they can vouch for you or recommend you. That will make them want to object even more, and probably should too, since business should come before friendship in this case. Be nice to your fellow admins and help them when they need it. This can get you a much higher chance of getting vouches on your application.
---------------------------------------------------------------------------------------------------------------------------------------
Thank you and you're welcome for taking your time to read this. I hope it helps all ranks to reach their next rank.
{END OF SPOILER}
This spoiler contains: "How to use /wm or /wileemanage"
Link to original thread can be found here.
This info has been slightly modified and improved.
Credit goes to: Polaris Seltzeris.
Some admins are confused about /wm and what it does.
/wm is my personal command with some fun/handy commands to use.
If you wanna know what commands you can use and what they do, go on the server and use /wm help or /wileemanage help.
This command includes banning commands and other administration commands.
This command has lots of old disdfreedom commands that were missed by serverl admins.
If you want to suggest a new command, then make a suggestion on the forums.
Feel free to code your own stuff into my plugin through a pull request: github.com/TotalFreedom/MobArena
Issues are also appreciated, to note bugs or anything.
Enjoy!
{END OF SPOILER}
{END OF SPOILER}