• This forum is strictly intended to be used by members of the VS Battles wiki. Please only register if you have an autoconfirmed account there, as otherwise your registration will be rejected. If you have already registered once, do not do so again, and contact Antvasima if you encounter any problems.

    For instructions regarding the exact procedure to sign up to this forum, please click here.
  • We need Patreon donations for this forum to have all of its running costs financially secured.

    Community members who help us out will receive badges that give them several different benefits, including the removal of all advertisements in this forum, but donations from non-members are also extremely appreciated.

    Please click here for further information, or here to directly visit our Patreon donations page.
  • Please click here for information about a large petition to help children in need.

Rule Violation Reports (New forum)

This is an announcement that Apotheosis69 has been demoted, banned for three months, and thread-banned from the translation requests thread, for passing off MTL as his own.

Please stop doing this people. We've caught four people doing it already. If you have, come forward and your punishment will be lesser than if we have to catch you ourselves.
Do we by chance have a rule regarding translation tools and engines (i.e. Google or Yandex Translate) on this wiki? Because if not, I was gonna suggest we create guidelines for it just so we can avoid any additional mistranslations or translation abuses in the near future.
 
Do we by chance have a rule regarding translation tools and engines (i.e. Google or Yandex Translate) on this wiki? Because if not, I was gonna suggest we create guidelines for it just so we can avoid any additional mistranslations or translation abuses in the near future.
From our Editing Rules we have:
Officially published works that have reached a high level of notability will be considered for inclusion within the VS Battles Wiki. The use of Wattpad and similar fan work sources is prohibited. However, self-published works will also be considered as long as they meet the aforementioned criteria of notability. Additionally, while official translations are preferred, fan translations that are of good and very reliable quality will also be accepted. For works that have not been officially translated, the use of original raw texts and associated translations is preferred, but it should be noted that for fully fan translated works like Visual Novels, Web Novels, etc., it may not be practical or feasible for participants to locate raw texts for the entire work and present them alongside the scan. In situations where the reliability of publicly available material is in question, the analysis of re-translations performed by members of the VSBW may be used as a means of evaluation. However, it should be noted that these translations may not necessarily be considered superior to official translations and should be evaluated on a case-by-case basis. Machine translation is not an acceptable alternative, as it is prone to errors and mistranslation, and would have to be re-evaluated by members of VSBW anyway, rendering it redundant.
And we currently have this ongoing thread aiming to clarify our rules on MTL.
 
This is an announcement that Apotheosis69 has been demoted, banned for three months, and thread-banned from the translation requests thread, for passing off MTL as his own.

Please stop doing this people. We've caught four people doing it already. If you have, come forward and your punishment will be lesser than if we have to catch you ourselves.
Was he doing it for all of his translations? If not, would we have to get things translated by him re-translated anyhow, on the off chance he did use MTL?

Bruhhhhh I’m actually about to crash out, how does this keep happening? He was such a cool dude, too.
 
Was he doing it for all of his translations?
I mean, we can't be 100% certain, but the indications of MTL lasted the whole way through, from the first request he fulfilled through to recent ones. And his confession when approached wasn't particularly specific.

His one Korean translation may have just been flawed instead of MTL, and one of his Mandarin translations might have been fine? I don't remember exactly.

But in general, he probably did.
 
This is an announcement that Apotheosis69 has been demoted, banned for three months, and thread-banned from the translation requests thread, for passing off MTL as his own.

Please stop doing this people. We've caught four people doing it already. If you have, come forward and your punishment will be lesser than if we have to catch you ourselves.
How many more cases of TH’s cheating the system will it take to just retire the role entirely?
 
How many more cases of TH’s cheating the system will it take to just retire the role entirely?
Meh, retiring the role doesn’t really accomplish much. At the end of the day, translations will still need to be done regardless, and it just means that now the brunt of translations will be done by users that haven’t even gone through the screening process we already have in-place, ineffective or not.




@WanderingGecko has not listed any of the 4 people disagreeing with their thread despite it being pointed out to them. I even listed the people who are disagreeing and why and Gecko has not put them into the disagree category, despite being active on the thread. As far as I am aware, you are not allowed to simply not count votes.
This is usually more of a problem when users don’t account for Staff votes, as that’s what would pass/not pass a thread. Otherwise, it’s pretty common for people to start counting votes, and then not really going through the trouble of updating it. In this specific case, as you point out, it seems like OP is doing it to be intentionally spiteful so I will go ahead and update it.

@WanderingGecko You can’t just refuse to acknowledge opposition, please keep that in mind moving forward.
 
Meh, retiring the role doesn’t really accomplish much. At the end of the day, translations will still need to be done regardless, and it just means that now the brunt of translations will be done by users that haven’t even gone through the screening process we already have in-place, ineffective or not.





This is usually more of a problem when users don’t account for Staff votes, as that’s what would pass/not pass a thread. Otherwise, it’s pretty common for people to start counting votes, and then not really going through the trouble of updating it. In this specific case, as you point out, it seems like OP is doing it to be intentionally spiteful so I will go ahead and update it.

@WanderingGecko You can’t just refuse to acknowledge opposition, please keep that in mind moving forward.
At the very least, please hear out my reasoning before jumping to conclusions.

I haven’t been very active on VSB over the past couple of days—just checking in occasionally due to some family matters. So far, I’ve only added people who have clearly stated their stance, such as “neutral to agree” or “agree.”

The last comment I made was in response to someone who suggested the thread to be closed for an invalid reason—simply because they felt it didn’t make sense, even though no staff member had evaluated it yet.

Now that I finally have some free time, I’ll start counting and continue working on the thread.

Edit:
I’ve added all the latest votes.
 
Last edited:
@CodeCCLL Your post is ultimately not about questions specific to Apotheosis' specific report, and doesn't have any comments on other reports, so I'm going to remove it, and any further posts about it in this thread. Please take it to another thread.

Any further posts partially about ancillary information such as the Translation Helper position as a whole will have those portions edited out by me.
 

It took 47 minutes. Not sure what caused the delay.
 
Last edited:
Mahek, please stop using the RVR for unnecessary, non-reports. A 47 minute interval between someone giving you a warning and adding it to the tracker is (1) not report-worthy (2) not a problem.
1: In technicality I was reporting myself + notifying staff to add it to the warning tracker.
2: It is technically a problem if we were dealing with someone who was less inclined to follow rules and more likely to break more rules in the time spent trying to deal with the original breach. (I'm not that type of person, but I'd be concerned if that was what we were dealing with.)
 
2: It is technically a problem if we were dealing with someone who was less inclined to follow rules and more likely to break more rules in the time spent trying to deal with the original breach. (I'm not that type of person, but I'd be concerned if that was what we were dealing with.)
This legitimately would be an issue though considering that we HAVE seen people breaching more rules/breaching the same rules again while already being reported, as well as instances of outright hostility and disrespect to the staff members and other people, even within the RVR itself.
Though, with that being said, technically by that point more staff would have been alerted to the issue due to the increased magnitude/gravity of the issue caused by said aggravation.
 
In any case, sorry again for taking up your time, but I wasn't sure where else to discuss this collectively with the staff team as a whole as to how action could be taken faster in general and/or if it should be, given (hopefully reasonable) concerns as to aggravating factors and potential further damage/disruption being caused following the original reports (also, we already have regular peeps also helping to report rule breaches by other peeps here to alert staff, Dark Souls in particular being a prime example, so this isn't necessarily new outside of the fact that I'm self-reporting).

I should probably just take the chance here to apologise to Nierre as well for pointing out the duration taken repeatedly (it wasn't out of spite or malice, just genuine concern as to why the warning wasn't added ASAP after being issued cause of fear of oversight or the warning issuance itself being buried and/or generally slipping from awareness), and hope they understand where I'm coming from.

I'm not sure if anything else needs to be said here, so I should probably just stop commenting any further for fear of unintentional further disruption.
 
Because the equation seems to be, someone speaks to Mahek, and Mahek replies numerous times with continued (in his estimation) relevant context (rather than editing a message, perhaps, or not leaving one at all if it is not too relevant), I have threadbanned Mahek for a day. This will cut the immediate conversation short.

@Mahek_The_Assassin_Silent_Killer This is the final informal warning. Don't do that here. Don't do that on any wiki management thread. It bogs it down unnecessarily. Use the threads as they are meant to be used or simply don't use them. Your post about the warning FinePoint gave you, while dreadfully ironic, is also strictly not necessary here- contact Nierre about it, or don't. But not here. This is for new reports.

The same logic applies universally to all such threads. It simply isn't the place to post three times in succession about your musings.

I will abate your current apparent anxiety and add your warning to the Tracker for you. For Christ's sake, listen to the warning, though.
 
I have (once again) thread-banned @Mahek_The_Assassin_Silent_Killer from the rant thread.

They blatantly continued to spam it even after the warning, and after I told them exactly how they could make long posts without being disruptive.

In addition, they were thread-banned before (although for different reason), but Ant and I decided to give them another chance. It was also brought up back then how they shouldn't spam long posts, both publicly and privately.

Finally, I've gotten multiple private messages now basically begging me to do something about it, which of course isn't a reason alone to take action, but it is proof that they have been regularly bothering people in the thread.

Of course, like last time, if other staff members think something else is appropriate, I would love to hear from them.
 
Last edited:
Reporting @Mahek_The_Assassin_Silent_Killer for continuous spam and flooding of the Unpopular Opinions and (Friendly) Rant thread.

I've already warned them in the thread and they've also been asked multiple times before this to stop flooding and multi posting and they don't listen. I haven't been able to add the to the tracker cause I've been busy, however since my warning, they've continued to flood and spam the thread. This has been going on for months but this has been specifically really bad as of recent.

I personally am for a ban from the thread itself, but id like to see what the rest of the staff think.
 
Last edited:
No problem. Mistakes happen. 🙏❤️

Anyway, Astral_Trinity439 wants to make an appeal to have his 6 months block reduced to 3 months instead:

Since they seemingly disproved the primary evidence against them (that no MTL actually uses "to") I would support that.

One could argue they were still cherry-picking, but at that point we're just speculating intention. I prefer to assume good faith by default.
Friends, we still need to reach a decision regarding this.
 
I've repeated at this point that I don't want to step in on translation matters because, despite arguments to the contrary, I feel that they are steeped in the context of TL-work and as such I find myself insufficient to evaluate them. Nevertheless, if nobody else will, I shall.

In my opinion, I think the reduction to the original 3 month time is fine. My impression is that he wants to help and that foolishly led him astray of our rules, but we don't need to bar him from helping for so long as a result. I approve of the appeal.
 
This guy is messing up the profiles.
jyj4X6X.png
1KsMSy1.png

aLyBq5s.png
 
I would like to report @Tempestdragon6 (again). This time for being uncivil and toxic in this thread, shown here, here, here, here, and here. And from the rant thread:

I think this warrants at least a hard warning, possibly something worse.
Yeah, that's worthy of at least a retort. Their last warning on the Tracker itself was from November 2024, so while it's possible they've had intermittent warnings, they were never logged: for now, I'd prefer to just extend a warning to not devolve into old habits.
 
Back
Top