Alternate Battlegrounds

Alternate Battlegrounds 시리즈

Alternate Bttlegrounds 대체 전장 @Qnixu 제작 날짜 {{{#FFF 최근 업데이트 날짜 2024년 11월 18일 }}} {{{#FFF 최대 플레이어 수 14명 }}} {{{#FFF 플랫폼 #!wiki style="margin-top:2px'' [[PC|{{{#fff PC}}}]] / [[휴대 전화|{{{#fff 모바일}}}]] / [[콘솔|{{{#fff 콘솔}}}]] }}} {{{#FFF 커뮤니케이션 #!wiki style="margin-top:2px'' [[파일:Roblox 마이크 아이콘 Real White.svg|width=15]] 마이크 }}} {{{#FFF 장르 액션 / 배틀그라운드 및 격투 }}} {{{#FFF 권장 연령 9세 이상[1] }}} {{{#FFF 기어 허용 }}} SNS

1. 개요

2. 시스템

2.1. 자원

• 마나: 화면 왼쪽 아래 주황색 게이지. 어떠한 공격의 피해를 방어로 막아내거나, 이동기를 사용하거나, 스킬을 사용하면 일정 수치만큼 깎인다. 바닥나면 서술할 행동들을 할 수 없다. 넉다운 시 다시 일어나는 시간도 마나의 영향을 받아, 마나가 많을수록 더 빨리 일어난다.
• 스태미나: 화면 왼쪽 아래 하늘색 게이지. 달리기, 대시를 시전하면 일정 수치만큼 깎인다. 바닥나면 서술할 행동들을 할 수 없다.
• 궁극기 게이지: 화면 왼쪽 아래 보라색 게이지. 피해를 주거나 입으면 일정 수치만큼 받는다. 궁극기 게이지가 필요한 스킬을 사용하는데 쓰인다.

2.2. 이동

• W,A,S,D: 이동
• W,A,S,D 2번 연타: 대시. 일정한 양의 스태미나를 잡아먹는다. 스태미나가 더 없으면 대시를 멈추고, 더 이상 시전할 수 없다. 마나와 스태미나 회복 속도는 대시의 영향을 받아, 대시 시전 시 잠깐 동안 둘 다 회복되지 않고, 그 후 점진적으로 회복 속도가 증가한다.
• SHIFT+W, A, S, D: 달리기. 어느 한 방향으로 대시 후 그 방향키를 계속 누르고 있으면 자동으로 달리기를 시전한다. 달리기는 일정한 양의 스태미나를 지속적으로 잡아먹으며, 스태미나가 없으면 달리기를 멈추고 더 이상 시전할 수 없다. 대시처럼 마나와 스태미나 회복 속도도 달리기에 영향을 받는다. 달리기 시전 중에는 둘 다 회복되지 않고, 그 후 점진적으로 회복 속도가 증가한다. 락온된 상대를 향해서 달린다면 달리기 속도가 빨라지지만, 락온한 상태로 뒤나 옆으로 달리면 그 속도가 느려진다.
• R: 이동기. 현재로써는 순간이동밖에 없다. 일정한 거리를 즉시 이동하며, 락온하지 않은 상태라면 마우스 포인터가 있는곳[3]으로 텔레포트를 하고, 락온한 상태에서는 상대방 바로 앞으로 텔레포트한다. 텔레포트 가능한 거리 까지만 텔레포트를 하므로, 락온하지 않았어도, 락온했어도 자신이 원하는 위치로 가지 못할 수도 있다. 텔레포트는 마나를 잡아먹으며, 시전 시 잠깐동안 마나, 스태미나 회복을 멈추고, 잠시 후에 회복이 시작된다. 쿨타임은 2초.

2.3. 전투

• 기본 공격(LMB)[4]: 마우스 좌클릭, 혹은 모바일에서는 빈 공간을 누르면 아무런 마나, 스태미나 소비 없이 시전할 수 있는 기본 공격을 사용한다. 기본 공격을 할때 시전 가능한 횟수는 캐릭터마다 다르다.
• 방어(F): F키를 누르면 플레이어 캐릭터가 특수한 모션을 취하며, 특정한 공격을 제외한 모든 공격의 피해를 막는다. 마지막 기본 공격은 늘 방어를 무력화하여, 상대를 잠시동안 기절시킨다.[5] 몇몇 스킬은 방어를 무효화하여 잠시 기절시키고, 또 몇몇 스킬은 방어를 무시하여 피해를 준다.
• 퍼펙트 블록: 게임의 핵심. 상대방의 평타와 거의 동일하게 방어를 시전하여 평타를 막아낸다면, 퍼펙트 블록을 시전하여, 상대방을 잠시동안 기절시킨다. 역공의 기회를 제공하는 셈. 핑이나 딜레이같은 게임 외적 요소에 영향을 받는다. 다른 게임에 많이들 존재하는 패링의 개념을 생각하면 이해가 훨씬 빠르고 쉽다.
• 궁극기: 궁극기 게이지가 다 차있어야 시전할 수 있다. 궁극기 시전 시 궁극기가 적중했든 적중하지 않았든 게이지는 완전히 증발하여 처음부터 다시 모아야 한다. 궁극기는 스킬을 나타내는 버튼의 숫자 밑에 작게 (ult)라고 써져있다.
• 챌린지: 혹은 1v1. 채팅창에 /challenge (유저 이름) 혹은 /1v1 (유저 이름)[6]을 입력하면, 그 유저의 오른쪽 상단에 일종의 초대장이 도착한다. 이를 수락하거나 거절할 수 있으며, 수락할 시 외부의 개입이 없는 직사각형의 공간에서 둘만이 남아 결투를 펼치게 된다.[7] 공정한 싸움을 위한 나름의 장치.
• 넉다운(기절)[8]과 무적: 특수한 스킬에 당하거나, 마지막 평타 혹은 스킬에 넉백되었을 때 나온다. 잠시동안 바닥에 쓰러져 아무것도 할 수 없다. 넉다운이 일어나는 밀치기는 특유의 이펙트가 따로 있다. 스킬 피격 판정은 그대로이나, 넉다운 시 평타는 맞을 수 없다. 전술했듯 마나의 양과 캐릭터가 일어나는 시간은 서로 반비례한다. 일정한 시간 후 다시 일어날 때 특유의 애니메이션이 출력되며 캐릭터가 흰색으로 깜빡이고 잠시동안 무적을 얻는다.[9] 주의할 점으로, 강제 넉다운 스킬들에 당했거나 넉백당해 벽에 박혔을 때, 혹은 기절했을 경우엔 남은 마나의 양과 상관없이 정해진 시간이 지나면 다시 행동이 가능해진다.
• 강제 기상: 몇몇 스킬들의 특징으로, 넉다운 상태의 적을 강제로 일으켜 세워 평타 혹은 다른 스킬을 통한 추가적인 딜링이 가능하게 한다. 이 경우에도 넉다운 상태와 마찬가지로 아무것도 할 수 없으며, 일정한 시간 후에 똑같이 일어나는 애니메이션이 출력된다.
• 락온(L 혹은 마우스 휠 버튼): 상대방 캐릭터에 마우스 커서를 올리고, 상응하는 키를 누르면 자신의 캐릭터가 알아서 상대방 캐릭터를 향한다. 마우스로 일일이 스킬을 조준하거나, 방향키로 캐릭터 방향을 조절하여 스킬 방향을 맞추지 않아도 되게 하는 편의 기능. 단, 일부러 캐릭터의 약간 밑을 조준하고, 날아가는 속도를 전혀 계산하지 않기에 스킬을 대충 쓰면 빗나가게 된다.
• 락온중 3인칭 시점 변경(C): 락온을 한 상태로 상응하는 키를 누르면 3인칭 시점을 변경할 수 있다. 캐릭터들의 스킬을 알아보거나, 본인이 벽에 박혔을 때 상대가 어떤 스킬을 쓰는 지 보는데 쓰인다.
• 충돌: 만약 상대방과 자신의 기본 공격이 맞부딪혔다면, 퍼펙트 블록, 방어가 무효화 및 무시당했을 때 나는 소리와 같은 소리가 나며, 두 캐릭터 모두 일정 거리만큼 밀쳐진다. 만약 날아오는 기본 공격을 막아내지 못할 것 같다면 공격이라도 하여 턴을 만들어내라는 의미.
• [!] 스킬: 상대방 머리 위에 나타나는 것과 시전자 머리 위에 나타나는 두 가지 유형이 있다. 상대방 캐릭터에 나타날 경우, 락온 시 사용이 가능하며, 상대가 방어를 시전하거나 스킬이 성공적으로 시전되기 전에 시전자가 타격당하면 취소된다. 시전자에게 나타날 경우, 방어 무시 스킬을 준비한다는 뜻이다.[10] 시전자가 스킬을 시전하기 전에 타격당하면 취소되며, 보통 일직선으로 움직이는 스킬들이 대부분이기에 피해주면 된다.

2.4. 기타 시스템

• 유저 점수판: 킬 수가 많은 유저부터 내림차순으로 나열되며, 유저 이름, 킬 수, KDR(죽인 횟수를 사망 횟수로 나눈 것)[11][12], 연속 처치, 지역이 표시된다. 지역은 국기로 나타낸다.
• 더미: 로블록스 기본 표정인 Smile 표정에 아무 옷 없이 회색 몸체를 가진 개체들로,[13] 채팅창에 /dummy (더미의 닉네임)[14]을 입력하면 자신의 위치로 소환할 수 있다. 더미는 플레이어처럼 공격을 받을 수 있다. 하지만 더미가 스킬을 난사한다던가, 콤보를 쓴다던가 하진 않고 공격 더미[15]를 제외한 더미들은 맞기만 한다. 특이한 더미로는 상시 방어중 판정인 더미와 기본 공격을 시도하면 퍼펙트 블락에 당한 판정을 가지는 더미, 상시 카운터 스킬을 켜놓은 판정인 더미[16], 모든 움직임이 느린 더미가 있다.[17] 더미를 이용해 콤보를 만들거나 연습하고 스킬들도 익힐 수 있게 해준다. 사실상 이런 게임에서 빠질 수 없는 시스템. 전투중일 때 더미를 소환하려 하거나 더미가 누군가한테 맞고 있을 때 소환하려고 하면 "Dummy in use"[18]가 채팅창에 출력되며 소환이 안 된다.

3. 캐릭터 및 스킨

4. 맵 및 패치 내역

5. 팁

• 다만, 단점이 있는데, 히트 박스 표시가 대부분 빨간색 원[25]으로 표시되어 시야에 영향을 줄 수 있고, 버그로 인해 공격이 안 통해 혼란을 주는 경우가 빈번하다. 또 히트박스는 아주 살짝만 닿아도 공격을 받은 걸로 인정된다. 이렇기 때문에, 옆 동네보다는 히트박스 효율이 안 좋은 편이다.

6. 기타

• 이쪽도 티밍이 가장 큰 문제점인데, 다른 문제점은 킬 스틸, 때리고 도망가기 등이다. 개발자들은 "티머가 모인 친목서버나 그런것은 전혀 신경 쓰지 않지만, 발견 즉시 사살할 유저 리스트가 있는 서버의 구성원은 가차없이 밴하거나 게임 데이터를 전부 지우겠다" 라고 말했다.

• 원작인 SoulShatters Test Place의 설명은 This is a fighting game, "randoming" doesn't exist. 이다. 번역하면, 이것은 싸우는 게임이다. "시비"란 존재하지 않는다. 인데, 소울섀터를 정신적으로 계승한 AB 또한 이 룰이 적용된다고 볼 수 있다. 특히나 이것이 중요한 이유는, 소위 "시비"를 호소하는 사람들이 채팅에 도움을 요청하여 애먼 사람만 티밍당하는 경우가 있기 때문이다. 이건 모든 지역을 통틀어서 늘 있는 문제이다. 사실 게임에 들어오는 순간부터 암묵적으로 언제든 공격당할 수 있다는 룰에 찬성하는 것이다. 전쟁터에서 악수하고 차 한잔 마신 뒤 싸우진 않을 거 아니야 이럴꺼면 왜 싸우는 겜에 들어왔는지
  
• 제작진들은 현재 Alternate Battlegrounds: A[28] 라고 명명된 대규모 업데이트[29]를 준비중인데, 이참에 무려 낡은 코드들을 전부 새것으로 바꾸는 중이라고 밝혀 다음 업데이트는 조금 오래 걸릴 것으로 예상된다. 이유는 최적화 개선과 순조로운 개발을 위해서라고 한다. AB:A에서 추가될 컨텐츠로 일단 확인된 것은 , 글리치테일 프리스크 리워크, 스토리쉬프트 차라 궁극기 추가[30], 새로운 캐릭터 초상화, 랭크 게임 모드, 서버 선택 입장 기능, 킬러[31]와 인새니티 샌즈[32], 오공 블랙[33], 공허 가스터[34], 버질[35] 스킨 추가, 타임 패러독스[36] 추가, 편의성 업데이트, 게임 시스템 리워크, 대규모 밸런스 패치 등이 있다. 또한 원래 추가될 예정이었으나, 개발자 대거 이탈로 인해 갈아엎어졌거나 무기한 연기된 것은 델타 샌즈[37] 추가, 언더테일 샌즈와 글리치테일 가스터[38]현재의 가스터에서 매우 이질적으로 변할 예정이라고 한다. 결과는 압도적인 리워크 찬성. 아쉽다.] 리워크, 크로스 & X차라 분리 가 있다. 당연히 상기된 모든 내용들은 언제든 변경점이 있을 수 있다.
  
• 2023 만우절 당시, 게임이 완전히 밈으로 떡칠되었다. 맵이 완전히 바뀌고, 몇몇 스킨과 캐릭터의 대사가 매우 이상하게 바뀌었다.[39] 채팅 소리도 변경되었으며, 대부분의 효과음들이 변경되었었다.

• 생각보다 잠수함 패치가 잦다. 패치 내역 알림은 안 올라오고 내용도 없었는데 샌즈의 뼈 3번 스킬 피해량이 하향된 것이 그 예시이다.

7. 이스터에그

7.1. 메인 화면

• 확률적으로 메인 화면 테마가 바뀐다.
• 메인 화면 테마가 바뀌는 것 보다 더 희박한 확률로 Friday Night Funkin'처럼 바뀐다. 오른쪽에 더미가 어떤 여자처럼 있는 걸 볼 수 있다. 2023 만우절 한정으로 접속 시 확정적으로 등장한다.(현재는 확률적으로 등장함) 흥겨운 비트에 맞춰 게임에 대한 간단한 소개가 한 문장씩 나오는데, 마지막 설명이 대미를 장식한다. "Get ready to get teamed on"으로, "티밍당할 준비나 하셈" 이라고 적당히 번역할 수 있다.

7.2. 업데이트 화면

• 업데이트가 된 후, 바로 들어가면 AI로 그려진 AB의 간판 로고가 나온다.(...)

7.3. 스노우딘(2번째 버전)

• 샌즈의 눈을 가진 눈사람을 볼 수 있다.
• 동굴에서 뚫려있는 위쪽으로 들어가보면 표지판 3개와 저장하게 해주는 별과 그 사람의 수염을 착용하고 있는 더미와 전부 디자인이 다른 모자 4개를 볼 수 있다.
• 표지판 1

• 표지판 2

• 표지판 3

• 크리스마스 한정으로 턱이 요상한 사람이 달 위에 이미지 상태로 있었다.

8. 논란 및 사건사고

8.1. 개발자 대거 이탈 사건

• 대부분의 사건들은 한국 시간으로 새벽에 일어났기 때문에, 정보가 사실과 조금 다르거나 서술이 부족할 수 있다.

8.1.1. 발단

8.1.2. TylerPee의 폭로

8.1.3. 닉스의 사과문

8.1.4. Koda의 어뷰징

8.1.5. 반응과 여파

8.1.6. 마스터소드의 문서

[ 전체 글 ]

>DISCLAIMER:

NOTHING IN THIS DOCUMENT IS INTENDED TO PERSONALLY ATTACK ANYONE MENTIONED OR FURTHER INCLUDE THEM IN THE DRAMA THAT HAS >ALREADY OCCURRED. PLEASE DO NOT SPREAD ANY HATRED TOWARDS THOSE INVOLVED, ESPECIALLY JADEN. THIS DOCUMENT ONLY SERVES THE >DEFENSIVE PURPOSE OF EXPLAINING AND/OR DISPROVING ANY ALLEGATIONS HELD TO AB IN THE TYLERPEE ANNOUNCEMENTS. THIS IS NOT AN >EXPOSÉ.


Miscellaneous Explanations
=================================================
Why Was TylerPee Demoted and Banned?
TylerPee’s demotion incentives are fairly straightforward - he pinged everyone in an announcement out of the blue and >stirred by far the worst drama AB has ever seen in its year of existence. I don’t blame him for this announcement, as with >the information he collected at the time, his perspective was logical, but through recent evidence we’ve collected we have >decided TylerPee is without a doubt purely an antagonist towards AB as a whole. It has been confirmed in both leaks of a >server he’s participated in and even messages to the members of AB that TylerPee has intended to burn down the AB >community entirely (seen in evidence #22 - #39). He bragged about his actions in regards to destabilizing the server and >admitted to scheming a plan for tarnishing both Nix’s and my reputations further, as well as damaging the AB server and >game as much as he could in the process. Additionally, the way he planned to go about doing so was evading his ban by >using his friend’s account and hosting a false game night. Due to this, we cannot allow TylerPee to ever return to AB >again.

Why Was TylerPee’s Announcement Deleted?
Despite initial assumption by some, TylerPee’s announcement was not deleted in an effort to “censor” or “suppress” what >his message was trying to get across. I initially deleted it because, at the time I had seen it, I was at work and only >had the time to read a few sentences. The most I saw in that moment was the fact it pinged everyone and his claims of Nix >and I being manipulative liars, so of course I deleted it in an attempt at preventing any drama stirring before I could >facilitate the server when I got home. Unfortunately, I deleted it too late, and instead the effect was a riot of furious >people under the assumption I was trying to censor what he said. I said “sorry for the ghost ping” after his announcement >was deleted because, although the message itself was gone, the everyone ping still alerted every member of the server, and >those who hadn’t read the message yet would be wondering what was happening. I can’t just let an everyone ghost ping go >without at least that form of a short apology. To support this, for the people who had caught wind of his message, I said >“expect an explanation” for any and all accusations TylerPee had against AB, Nix, or myself. Upon getting home and realizing the deletion of the message was impulsive, I read the entire message and reposted it in announcements for anyone who was curious to be able to see it, as again, almost everything he stated was explainable and is explained in the document you’re currently reading. My motive was not to censor anything he was saying, as again, I did repost the message in announcements, but to prevent rioting and any unnecessary burdens on the then smaller mod team.

Why Did We Hide Jaden’s Demotion Plan?
In TylerPee’s announcement, Nix and I were portrayed as manipulative liars due to the fact that we hid our plan to demote Jaden from the admin team. While it is true that we did hide it, it’s not for the reasoning hinted at in his announcement. We are not, in fact, ‘manipulative liars’. The reasoning behind Jaden’s demotion is seen below, in its respective section, but I’ll begin with the history of the plan and why we hid it. In summary, Jaden and I have had our issues over the past 10 months or so, which began to increase in intensity and promise worsened possible outcomes over the past 2-3 months. Because of this, Nix and I wanted to demote Jaden in an attempt to finally resolve some of these issues. It was a difficult decision, but when we came to our conclusion we couldn’t just outright demote him at that moment. Due to an agreement Jaden had with some of the staff, if he were to leave, they agreed to leave with him. Demoting him without a trial and a proper explanation wouldn’t seem fair, so AB would have no chance at maintaining the admins that we hoped to keep, even in Jaden’s absence. To ensure us our best chance at keeping as many as we could after Jaden’s demotion, I had to write an explanation doc to share with all of the admins during the process. That document is the one you are reading right now, which is why you’ll shortly see a message I wrote a month ago referring to the admins in the Jaden’s Demotion section. As time went by, the document (which at the time only had our reasoning behind Jaden’s demotion and was intended for the admins) was approaching its completion. Before we could actually demote Jaden and have a discussion with him and the admins, unfortunately, the night where Nix and I played around with the Jit bot took place. Jaden understandably had an issue with the things that were taking place in lounge, and began to take action on them, which caused a disagreement, considering it was 5-6AM for Nix and I and we certainly weren’t acting with our best judgements. In the end, he resigned from his position as Manager on his own, and in light of the undefendable things that took place that night, the admins left with him. We had no way of preventing this after the disagreement, as the document was nowhere near finished and it never covered the Jit bot messages anyway, so the worst possible outcome of Jaden’s demotion happened without us demoting him in the first place. Because Jaden was already out of AB and the admins that would leave with him had already left, the document and the plan behind Jaden’s demotion no longer served a purpose. With that in mind, I chose to stop working on the document and not reveal the plan, as revealing it to the admins that stayed despite what unjustifiably happened that night would only make things worse, with them potentially leaving as well. Sure, AB lost a lot of admins that we certainly would’ve preferred not to, but with Jaden gone, the issues had already been resolved. I thought that the worst of the situation was already behind us, and we would only move forward from Jaden’s resignation. Unfortunately, TylerPee’s announcement followed a bit later, claiming that Nix and I hid the plan for malicious reasons and that Jaden was banned by us unreasonably, despite the fact that he resigned on his own. Afterwards, I was forced to explain a variety of things behind this drama to the AB community (including our reasons behind Jaden’s Demotion plan), so I was brought back to this document that was initially intended for the admins.

Was Jaden Banned For The Jit Bot Messages?
As stated previously, Jaden was not banned for the Jit bot messages, nor was he demoted by us at all. Despite TylerPee’s announcement, Nix and I did not intend to demote Jaden for opposing the change to Jit and what we were doing with it, as his opposition was fully reasonable. Not only would we have no basis to demote him on if that were the case, but the document and plan behind Jaden’s demotion were started before the night of those bot messages, so any correlation between the two would be impossible. Again, I believe there’s no real justification for what took place that night, which is why that’s the only thing not explained in this document, but the claim that the actions themselves were behind our intent to demote Jaden is completely false. Additionally, the bot no longer acts this way. It stopped the morning after.

=================================================

DISCLAIMER:
There is a significant portion of the following section that is now considered by both Jaden and I as outdated after recent discussion. These include the Koda demotion issues within Contention 2 and the issue in Contention 1. I am aware they are outdated, and they will be further elaborated in Jaden’s video, which is linked in the same announcement this document is. I have decided to keep them, however, as they were still nonetheless a part of our reasoning behind wishing to demote Jaden. They were truthful and honest to my and various other staff’s best assumptions at the matters they discussed, and thus will be used to defend the challenging of our reasoning by TylerPee. Once again, although they may be outdated now, they were the most we could honestly confirm at the time of their writing, and are certainly not the reasoning TylerPee has claimed supports the Jaden demotion plan. Contention 1 especially holds no current value against Jaden’s administrative abilities and certainly his character - which is fine - as damaging Jaden’s reputation or challenging his character is NOT the purpose of ANY of these contentions or this entire document at all. As previously stated, this document is purely a defensive resource to the allegations brought upon AB, myself, and Nix by TylerPee. Additionally, please keep in mind the section addressing the admins is also outdated. It was written during the time in which this document only served the purpose of justifying Jaden’s hypothetical demotion to the old admins, as discussed earlier in the Miscellaneous Explanations section. I have decided to not change anything in this doc from how it was originally written to address the admins simply because it is now meant for the members’ eyes, and to stay as transparent as possible.


===================================================
Jaden’s Demotion & Permanent Ban from AB
There are a plethora of reasons that AB has chosen to permanently relieve Jaden of his administrative roles, as well as in regards to the fact that we do not believe Jaden has a place at AB anymore. Before I go into any of these in this explanation, please understand that this decision IS final. There is nothing you can do or say to change that. And no, this is not a joke like the Koda and TylerPee promotion to Manager.
===================================================

For the admins reading this, please note that I completely respect each and every single one of your decisions. I acknowledge the fact that in light of Jaden’s absence, some of you may choose to leave with him. Although I definitely prefer that all of you stay, and I will make an attempt at achieving this, it is true that you may have your own personal reasons. If you want further elaboration or clarification from me in any way, I am happy to help you out. Otherwise, please keep the inevitable discussion in the GC civilized. There is no need for an argument, as AB’s decision will remain stagnant. All your previous conditions will remain valid, and new ones are up to request.


===================================================
Reasoning
Contention 1
Our first contention is by far the most foremost and objective, which is the fact that, if we were to proceed with inaction regarding Jaden and his place in the staff team, we would be harboring a suspended user and be actively condoning his authority. To appeal his suspended Discord account, he would have to prove to Discord that he is above the US age of consent (18) because of the various excessively explicit contents of his DMs (those are his DMs though, I’m not judging him by those it’s just Discord TOS). Common sense states that, as a community server, this would be unacceptable, and could result in punishment of the AB discord as a whole. I’m sure that you all, as administrators, can realize that. Alone, this should be enough cause to rid Jaden of his power roles.

Contention 2
Our second contention concerns Jaden’s irresponsible usage of power and irresponsible behavior, specifically revolving around unjustified and personally-driven punishment dispensed to those undeserving. A prime example of this was seen in cmpdr’s case. As many of you know, Jaden has carried a very potent personal grudge against cmp (evidence #3) for a considerably large amount of time, roughly 3 months. This had only escalated, however, after cmp offered to help stabilize AB in response to Jaden’s threats of crumbling it and removing most of the administrators the morning after he sent the following message (evidence #1 in the proof library). Others who Jaden both publicly and privately lashed out against for this same reason include Vietnam and BenAE. Conveniently, following cmp’s leak of the singular joke Uza made, he was immediately demoted without notice. Although I agree that cmp’s demotion was fair, as leaking staff chat is breaking a rule, I know that the process by which it was carried out was completely unacceptable. In fact, the reasoning behind cmp’s demotion was deliberately hidden from him by Jaden (as shown in evidence #17). Fortunately, it was a failed attempt, but upon having noticed that cmp knew why he was demoted, Jaden reacted furiously, essentially grilling any of the staff with access to high ranks (as seen in evidence #2).

An extension of this unprofessionalism and irresponsible behavior was showcased by Jaden before this, during the week or so he sat in AB without any power roles. Essentially each day, for almost a week straight, Jaden sat in lounge and began to publicly spread drama and insult various members, especially me. Post-resigning then, Jaden’s reasoning for staying in the server was to “watch AB burn” and “make fun of that joke Mastersword”. He went as far as to create problems for Astral, disturbing the members to the point of which some of them even asked him themselves to change the topic of conversation. All of this can be seen in the proof library (evidence #4 - #11). Of course, he did not change the topic of conversation. On top of that, frequent rants like these occurred even unprovoked. I had not sent a message in AB 30 minutes to an hour prior to Jaden’s first message in lounge in that session of his activity. Not only does this act as another reason for Jaden’s removal, as it showcases the extent to which his unprofessionalism and emotion can override his logical capacity regarding myself (his coworker), it serves as an incentive to keep Jaden completely out of AB, regardless of role or power status, since he has proven to cause issues in the server with or without his administrator perms.

As for a more recent example, the situation between XEventia and Jaden showcases some instances of his irresponsible usage of power. On one occasion, he decided to game ban Spirit_Kana in AB’s lounge for no apparent reason after an argument (as seen in evidence #16). Upon us inquiring his reasoning for doing so in a vc, his only response was that it was for “getting a message across”. After causing problems and getting into personal beef with high ranks and the owner of the XEventia server, Jaden lost his admin role in XEventia, and proceeded to rant about it. His immediate reaction was to purge and delete the server in retaliation, as he was fairly upset, but conceded after about 30 minutes of Nix and I talking with him. Even though Jaden had a good reason to have an admin role in XEventia initially, the showcase of his immediate destructive tendencies gave us another reason to be skeptical of Jaden being fit to manage AB. While it is true that Jaden played a role in helping XEventia out of its undeniably degenerate state, he lost his role far after the server was amended, whilst they still maintained Uza’s role and thus his ability to watch over the server. Still, Jaden reacted with a desire to execute unprecedented and extreme force. XEventia has since not had any issues with the respectability and quality of its community’s messages, regardless of Jaden’s presence or absence. Unfortunately, after Jaden’s fiasco with the XEventian leaders, he amassed a notably bad reputation with its important people and active members (as seen in evidence #12 - #15).

Staying on recent examples, there has been an issue between Jaden, some of the staff, and Nix & I regarding Koda. Since I’m sure you all are in the admins GC to observe Jaden’s rant about it, I’ll just summarize the issue and how it fits into this line of reasoning. Today (at the time of writing, Jun 17, 2023), Koda was demoted from her position as Moderator, advocated mainly by Astral, Ponko, and more importantly, Jaden, for the following reasons: “Had Vintage write responses on her mod app so she could pass”, “Displayed attention seeking behavior”, “Manipulated behavior via sympathy”, and “Has broken the rules and made too many references to stuff we are not allowed to mention (Im guilty of this too tho)”. Although none of the reasons correspond to her actual performance as a moderator, the legitimacy of the reasons themselves can be argued by both sides, which is why I’m not challenging them. Koda even admitted herself that she recognizes how her past behavior could have been perceived as ‘attention seeking’. There were two separate problems found in this situation, respectively addressed by Nix and I. Nix found a minor and completely reparable issue with how he was never told about any staff occurrences or major events, such as the addition or removal of moderators/administrators from the staff team. I, however, found a problem in Jaden’s conduct regarding Koda’s newfound access to viewing high ranks. True, an ex-mod should not be able to view the contents of the high ranks channel, but the “jeopardizing” of high ranks that caused him to move the channel to the bottom of the lowest text category piqued my interest. Before Ponko could delete the channel, or was told to delete the channel, I was able to see various messages degrading Koda and showcasing an extremely negative sentiment, even while she was a moderator, with DM leaks and messages that gave both Nix and I a reason to believe that Jaden, along with some other staff, intended on hiding their backstabbing from Koda. The notion that separates Jaden’s offense here from the other staff involved is the fact that Jaden has been proven to have these negative tendencies, with other cases to support that claim, yet the rest of the admins had only committed this one violation (as far as I’m concerned). This both ties back to the instance of Jaden’s display of excessive desire to hide the truth and segways into our next contention: dishonesty.

Contention 3
Our third contention is in view of Jaden’s previous objective dishonesty and obstruction of others’ attempts at work. On countless occasions during my extensive time working as Head of Development/Co-Owner of AB, Jaden and I ran into various issues regarding each other and the leading of the dev team. Because we had worked together for such a long time, I’m not going to get into the specifics for a lot of the issues and instead mainly summarize, saving prolonged discussion for only a few select instances. The main way tension between Jaden and I had all started was due to these disagreements and petty behavioral conduct. In the beginning, however, all was mostly well. AB development over the summer of 2022 was fine, until my school year started in late August. Once school had started, I was too inconsistent with my activity to efficiently guide development at the same pace I previously was. Jaden thankfully stepped up to the plate despite whilst only considered being Server Manager, and was picking up in places where I left off during the weekdays. Even though I was consistently able to take over on the weekends, Jaden began to ‘overstay his welcome’ in terms of leading development and slowly exhibited his desires to spread his control into the full week, even if I had opportunities to do my job during the weekdays or weekends. Over the course of a month or two, he successfully established his own authority with the devteam, and although the developers would still listen to me they would naturally look to Jaden in most cases. It was from then on where Jaden and I would get into most of our fights. Despite my efforts and clear intent to continue working, he would frequently undermine me and disregard anything I say, creating an everlasting tension between the two of us. Still, I was always able to do my 2nd job of building maps. This all skyrocketed, though, at some time in October of last year. Development to me seemed a lot slower, nothing was being said in the development server we had, nor in my DMs or in the AB server itself. Everything seemed off, and I didn’t hear a word of anyone taking any breaks. I decided to look into it, and as it turns out, Jaden made and was using a completely separate group chat (that wasn’t full) to go about development, with all of the other main developers and even Nix. After confronting him and being added to it, he told me that it was because “group chats are easier to use”, but I believe I have a very solid reason to think it was for the sole purpose of excluding me from whatever he was doing with my devteam, especially since it wasn’t full and I was never told about it. Of course, I was infuriated, but in light of all the positive work he’s done for AB even up to then, I decided to let it slide and told him to never do anything like that again. Although I was now in the development gc, the team that I had previously worked with became the most toxic working environment I’ve ever been in. For months, both Jaden and some of the developers were calling me useless, among other things, to my face and constantly talking behind my back while Jaden would continue to undermine me. To put it bluntly, I was treated like shit, but I can’t blame the developers. Since the creation of that gc they were always hearing things about me from Jaden, and since he was with them more often, they would always look to him. Once I was completely excluded and left in the dark about these things, they only had the presence of Jaden and the apparent absence of myself to formulate their new opinions of me, so I can’t say I was surprised. Still, I continued to work at a normal pace and push through the coming months, always building and leading where I could.

Fast forward many, many issues and a considerable amount of time later, one of the more recent major issues occurred. Some time in mid-late May, Lord was facing issues with previous UTPR staff who embezzled over 100k robux and many of the game’s assets from him, so a couple of our AB developers reached out to help him stabilize his game. In return, Grimbo, a talented builder at UTPR, kindly offered to temporarily help AB with anything development related. At around the same time, we were working on the Player event. Now, before Grimbo was hired by AB, a separate gc was made by Meemster to solely serve the purpose of working on the Player event. This was before any building for it was necessary, and since not all the developers were working on it, creating a separate and single-purpose gc for it was completely understandable. I simply asked to be added to it when building was necessary, and promptly was. After Grimbo’s hiring though, it ceased activity. Although building was then needed, Grimbo working with us meant to Jaden that he no longer had to rely on me, although he had absolutely no authority to be calling any shots development wise anyway. Of course, he created yet another separate dev gc despite being told not to back in October and chose to both exclude me from it and not mention a word. Consequently, he added Grimbo and took over Meemster’s initiative on the Player event. Not surprisingly, Grimbo was soon to be specifically instructed to not listen to anything I say to him and completely disregard me doing my job (as seen in evidence #18 - #19). Clearly, Jaden does not respect my authority in the field of development, so there should be no reason for me to respect his authority in the field of server management. Not only, however, does he jump at any opportunity to undermine me, his wishes to outstretch his authority here are both seen in this development-related contention and the issues with XEventia back in Contention 2. Additionally, I wasn’t the only developer that had various problems with Jaden. There was an instance of Jaden again obstructing development by overstretching his boundaries with Maple, at around the same time period (as seen in evidence #19 - #20). Maple previously hosted an event with the prize of her time paradox skin, which was already being worked on. By the time Jaden stepped in to stop the production of the skin, it already had assets made for it and was planned far before his intended influence on the skin. It was already promised to a member for completing Maple’s event, and considering she was Skin Manager, this was a completely reasonable decision. To this day, Jaden’s incentives for stopping its production are unknown to me.

Conclusion
As of wrapping up this document, the date is Aug 8, 2023. Jaden has parted ways with his position as AB’s Server Manager for a while now, and both of us would have it no other way. Jaden and I have remained friends even since his leave, and to be honest, things are much calmer. We both know how to separate friendships from work, and even during the issues we had, we were always able to enjoy time off together and laugh at the things we memed. Essentially, we are still on good terms. I physically cannot urge you more to NOT spread any hate for any mistakes he has made in the past. I believe that he is a good person inside, and I know through our conversations that he’s already been through more than most people ever will have. Plus, even if he were to make double the mistakes he did during his career at AB, it would be dishonest of me to say that AB would be the same without him. He undeniably played a major positive role in forming the community and game into what it is now, and for that I have nothing but respect for him. I can’t help but feel bad that I had to write all this about him, even though he had nothing to do with the TylerPee drama, as he was caught in the middle of his announcement. If you were to say anything to Jaden now, as a member, it should be “Thank you”.

[ 번역문 ]

>주의 사항:

이 문서의 어떤 내용도 언급된 누군가를 개인적으로 공격하거나 이미 일어난 일에 또 다시 연루되게 하려는 의도가 없음을 밝힙니다. 관련된 이들에게, 특히 제이든에게 증오를 퍼뜨리지 말아주세요. 이 문서는 오로지 방어적인 목적의 설명과 타일러의 주장을 부정하기 위함을 밝힙니다.

세부 사항 설명
=================================================
왜 타일러가 권한을 뺏기고 밴을 당했는가?
타일러의 권한 박탈에는 딱히 수상한 의도가 없습니다 - 그는 공지 사항에 언급된 이들을 전부 적으로 돌렸고 AB 탄생 이후 최악의 드라마를 이끌었습니다. 전 이 공지 때문에 타일러를 탓하는 게 아닙니다. 그가 당시에 모았던 정보들을 보면 그의 의도는 논리적이었으나, 저희가 수집한 최근의 정보들을 바탕으로 저희는 타일러를 한 치의 의심도 없이 완전히 적으로 간주하기로 했습니다. 그가 참여한 서버에서 그가 말한 내용과 AB 멤버들에게 말한 내용들을 보면, 타일러는 AB 커뮤니티를 완전히 붕괴시키려는 의도를 가지고 있었습니다(증거 #22 ~ #39). 그는 디스코드 서버를 불안정하게 한 자신의 행동을 자랑했고 저와 닉스의 평판을 훼손시키는 계획을 짰다는 것을 인정했습니다. AB 디스코드 서버와 게임을 그가 할 수 있는 만큼 망가뜨리려고 한 것 또한요. 추가적으로, 그가 자신의 계획을 실행에 옮기기 위해 생각해낸 방법이 자신의 친구 계정을 사용하여 밴을 피하고 게임 나이트 이벤트를 가짜로 여는 것이었습니다. 이러한 점들 때문에, 저희는 타일러가 다시 AB로 복귀할 수 있도록 허락하지 않을 것입니다.

왜 타일러의 공지 사항이 삭제됐는가?
사람들의 초기 추측에도 불구하고, 타일러의 공지사항은 그가 전하려고 했던 메시지를 "검열"이나 "억압"하기 위해 삭제된 것이 아닙니다. 제가 그걸 초기에 삭제한 이유는, 처음 공지를 봤을 때 저는 일을 하는 중이었고 몇몇 문장밖에 읽지 못했기 때문입니다. 제가 그 당시에 바로 알아차린 것은 그가 모두에게 핑을 친 다음 저와 닉스를 교묘한 거짓말쟁이로 간주했다는 사실이었고, 제가 집에 도착해서 서버를 관리하기 전에 어떠한 드라마가 일어나지 않도록 삭제했습니다. 당연한 일이니까요. 불행히도, 공지를 너무 늦게 삭제하게 됐고, 그 결과는 그가 말하려 했던 것을 제가 검열했다는 추측 때문에 분노에 휩싸인 사람들의 폭동이었습니다. 저는 "여러분 고스트 핑[52] 죄송해요" 라고 그의 공지 사항이 삭제된 뒤에 말했는데, 메시지가 삭제되었음에도 전체 인원 핑이 서버의 모든 인원들에게 영향을 줘서 공지를 읽지 못한 사람들이 무슨 일이 일어나고 있는건지 궁금해 할 것이기 때문에 그랬습니다. 전 에브리원 고스트 핑이 최소한의 짧은 사과도 없이 흐지부지 되는 꼴을 참을수가 없어요. 또한 제 주장을 뒷받침하기 위한 근거로는, 타일러의 메시지를 포착한 사람들에게 저는 타일러가 AB, 닉스, 혹은 저 자신에게 제기한 의혹들에 대한 설명을 기다려 달라고 말했다는 사실이 있습니다. 집에 도착하고 공지 사항 삭제가 감정적이었다는 것을 깨달은 뒤, 저는 전체 메시지를 쭉 읽어봤고 그것을 다시 공지 채널에 올렸습니다. 그 공지를 다시 볼 수 있는지 궁금해 하는 사람들을 위해서요. 다시 말하지만, 그가 주장했던 것들은 설명이 가능했고 실제로 당신이 읽고 있는 문서에 설명이 전부 되어있습니다. 강조하건대, 제 의도는 그가 말한 것을 검열하려는 것이 아니었습니다. 확실히 전 공지 채널에 메시지를 다시 올렸고, 그 의도는 사람들의 폭동과 당시에 더 작았던 모더 팀들이 질 수 있는 불필요한 부담들을 막기 위해서였습니다.

왜 우리가 제이든의 권한 박탈 계획을 숨겼는가?
타일러의 공지 사항을 보면, 저희가 어드민 팀에서 제이든을 쫓아낼 계획을 숨겼다는 이유로 저와 닉스를 교묘한 거짓말쟁이로 만들어 놨다는 것을 알 수 있습니다. 저희가 이 계획을 숨긴 것은 사실이나, 타일러의 공지 사항에서 그가 암시한 이유 때문에 계획을 숨긴 것은 아닙니다. 저희는 "교묘한 거짓말쟁이" 가 아닙니다. 제이든의 권한 박탈은 별도의 문단에 후술하겠지만, 계획의 과정과 그걸 숨긴 이유부터 말하겠습니다. 요약하면, 제이든과 저는 지난 10달 정도 문제를 겪었고, 점점 그 강도가 심해지며 지난 2~3개월간은 갈등의 결말은 최악일 것이라는 암시하는 나날이었습니다. 이 때문에, 닉스와 저는 이 문제들 중 몇 가지를 좀 해결하려고 시도하기 위해 제이든을 추방시키고 싶었습니다. 힘든 결정이었지만, 저희가 결과를 내렸을 때는 제이든을 추방시킬 수 없었습니다. 제이든이 몇몇 스태프들과 한 약속 때문에, 제이든이 나간다면 그들도 제이든과 함께 나가기로 했기 때문입니다. 별도의 재판과 명확한 설명 없이 그를 추방시키는 것은 공평해 보이지 않기 때문에, 제이든이 없음에도 저희가 계속 밀고 나가고 싶었던 어드민 팀을 유지할 수 없었을 것입니다. 제이든의 추방 뒤에 최대한 많은 것을 유지할 수 있는 최선의 기회를 보장하기 위해, 저는 추방 과정동안 모든 어드민들과 공유할 설명 문서를 작성해야 했습니다. 그 문서가 여러분이 지금 읽고 있는 문서고, 그렇기에 조금 있으면 제가 한 달 전에 제이든의 추방 관련해서 어드민들에게 쓴 글을 볼 수 있을 겁니다. 시간이 흘러, 문서는 (당시 제이든의 추방 항목밖에 없었고 어드민들을 위한 것이었던) 완성에 가까워지고 있었습니다. 저희가 제이든을 추방시키고 그, 어드민들과 대화를 나누기 전에, 불행히도, 닉스와 제가 디스코드 봇을 가지고 놀았던 밤이 찾아왔습니다. 제이든은 라운지 채널에서 일어나고 있는 일들이 불편했고(충분히 이해할 수 있습니다.), 이에 조치를 취하기 시작했는데, 저와 닉스에게 있어서 오전 5~6시였고 저희가 최상의 컨디션을 가지고 행동하지 않았다는 것까지 고려되며 사람들이 제이든의 추방에 대해 반대하는 모습을 보였습니다. 최종적으로, 제이든은 스스로 매니저 자리에서 사임했으며, 그날 밤에 일어났던 변명할 수 없는 일들 때문에, 어드민들도 제이든을 따라 나갔습니다. 저희는 어드민들의 반대 이후 이것을 막을 방도가 전혀 없었습니다. 문서는 아직 완성되지 않았고 어쨌든 디스코드 봇에 대한 것은 언급되지 않았으니까요. 그래서 제이든의 추방이 불러올 수 있는 최악의 결과가 제이든을 추방시키지도 않았는데 일어난 것입니다. 제이든과 그와 함께 갈 것이라던 어드민들은 이미 AB를 떠났기 때문에, 문서와 제이든의 추방 뒤에 숨겨진 계획들은 이제 쓸모가 없습니다. 그걸 염두에 두며, 저는 문서 작업을 그만 두고 계획을 공개하지 않기로 했었습니다. 그날 밤에 일어난 것들에도 불구하고 스스로 AB에 남아있던 어드민들에게 이 사실을 알리는 것은 단지 그들도 나가는 상황을 만들어낼 것 같았습니다. 확실히, AB는 많은 어드민들을 잃었으나, 제이든이 떠나며 문제는 이미 해결됐습니다. 저는 최악의 상황은 이미 저희 뒤에 있다고 생각하며, 저희는 제이든의 사임으로부터 앞으로 나아가면 될 것이었습니다. 불행히도, 타일러의 공지가 조금 뒤에 나타났고, 닉스와 제가 좋지 못한 이유들로 계획을 숨겼고 제이든이 저희에 의해 밴 되었다는 불합리한 주장을 했습니다. 그가 스스로 사임했다는 사실에도 불구하고. 그 후로, 저는 AB 커뮤니티에게 이 드라마 뒤에 숨겨져있는 많은 것들을 설명해야 했고 (제이든의 추방 계획 뒤에 숨어있는 이유들까지), 그래서 원래는 어드민들을 위한 것이었던 문서로 다시 돌아온 것입니다.

제이든이 추방된 이유는 디스코드 봇 때문인가?
전술했듯, 제이든은 디스코드 봇 이슈 때문에 추방된것도 아니고, 애초에 저희가 추방시킨 것도 아닙니다. 타일러의 공지에도 불구하고, 닉스와 저는 제이든이 디스코드 봇을 손보는 것과 저희가 그걸 가지고 한 일들에 반발해서 그를 추방시키려 한 것이 아닙니다. 그의 반발은 충분히 이유가 있었으니까요. 만약 이게 사실이었다면 저희는 그를 추방시킬 근거가 없을 뿐더러, 문서와 계획 자체는 그 디스코드 봇을 가지고 놀았던 밤보다 훨씬 전부터 준비됐었기 때문에, 둘 사이의 연관성은 0에 수렴합니다. 다시 말하지만, 저는 그날 밤에 일어난 일에 대해 변명할 생각이 없습니다. 완전히 잘못된 것이었으니까요. 그렇기에 이 문서에서 유일하게 설명되지 않은 것입니다. 그러나 이 디코 봇 문제가 제이든 추방 계획의 일부였다는 것은 완전히 잘못된, 거짓입니다. 추가적으로, 봇은 이제 이런 식으로 활동하지 않습니다. 바로 다음 날 멈췄어요.

=================================================