Bedrock cubecraft report no longer working - El informe de cubecraft ya no funciona

[SrMuerto7w7]

Solo quiero sus opiniones.

English
I just want your opinions

Report

 

[SfenKer]

Hi, report system works, but at the moment when you created report, probably there wasn't any online staff member. In-game reports are automatically closed after some time, if e.g. player logs off from the network.

However, you can create player report with evidence in the Player Reports category.

Player Reports

Learn about reporting rulebreakers and where to report them here.

www.cubecraft.net

 

[SrMuerto7w7]

Hi, report system works, but at the moment when you created report, probably there wasn't any online staff member. In-game reports are automatically closed after some time, if e.g. player logs off from the network.

However, you can create player report with evidence in the Player Reports category.

Player Reports

Learn about reporting rulebreakers and where to report them here.

www.cubecraft.net

Hola, me encanta tu aporte, teniendo en cuenta que no haya ningún personal de cubecraft o del staff para hacer el respectivo ban el sistema debería ser auto suficiente con un hacker tan evidente, volando e incluso persiguiendo al jugador que quería matar, que no haya ningún miembro de cubecraft no debería ser una excusa para que los hackers estén por todo el servidor dañando la experiencia.

English
Hello, I love your contribution, taking into account that there is no cubecraft or staff member to do the respective ban, the system should be self-sufficient with such an obvious hacker, flying and even chasing the player he wanted to kill, the fact that there is no cubecraft member should not be an excuse for hackers to be all over the server damaging the experience.

 

[SfenKer]

Hello, I love your contribution, taking into account that there is no cubecraft or staff member to do the respective ban, the system should be self-sufficient with such an obvious hacker, flying and even chasing the player he wanted to kill, the fact that there is no cubecraft member should not be an excuse for hackers to be all over the server damaging the experience.

There's anticheat, but it's very weak in my opinion (and probably not only mine). Also I think the report system was introduced only to notify staff members about cheaters, because anticheat doesn't need to be told if someone is cheating or not. At this moment best thing that you can do is just report players with evidence through player reports. This is the only thing that guarantees that the player will be punished.

 

[tacoman222xx]

Sentinel is still not really functional, you can still fly undetected but the infamous chunk glitch is insta ban often :) You just have to spend like 10 minutes posting clips on yt and making a report manually, which we all love

 

[SrMuerto7w7]

There's anticheat, but it's very weak in my opinion (and probably not only mine). Also I think the report system was introduced only to notify staff members about cheaters, because anticheat doesn't need to be told if someone is cheating or not. At this moment best thing that you can do is just report players with evidence through player reports. This is the only thing that guarantees that the player will be punished.

Es una afirmación muy asertiva y correcta, la verdad desconocía la forma en que funcionaba el proceso de manera interna, aun así, mirando el tiempo del reporte (es decir desde que lo publique porque realmente cuando reporto, yo reporto todo desde la página) se lleva mucho tiempo, no solo los 15 minutos, 5 por cada partida ya que si vez en las evidencias son 3 partidas diferentes y quien sabe cuántas más, el hacker pudo hacer y deshacer en el servidor, el problema real yace en que el sistema ahora mismo es negligente para una media de 10k (en promedio es lo que visualizo esto no es oficial), se puede tener un sistema mejor para una comunidad tan grande.

English
That's a very accurate and correct statement. I honestly didn't know how the process worked internally. Even so, looking at the reporting time (that is, from when I post it, because when I report, I report everything from the website), it takes a long time, not just the 15 minutes, but 5 minutes per game. If you look at the evidence, there are 3 different games, and who knows how many more. The hacker was able to undo the changes on the server. The real problem is that the system is currently inadequate for an average of 10k players (this is the average I see; it's not official). A better system could be implemented for such a large community.

 

[SrMuerto7w7]

Sentinel is still not really functional, you can still fly undetected but the infamous chunk glitch is insta ban often :) You just have to spend like 10 minutes posting clips on yt and making a report manually, which we all love

Hola, lamento ser el portador de estas malas noticias, pero eso tampoco es tan correcto. Como se muestra en las evidencias, realicé el reporte a las 9:09 AM y el usuario fue sancionado unas 10 horas y media después.

Apoyando el debate sobre el Sentinel frente al sistema manual, me gustaría poner sobre la mesa un análisis de probabilidades y datos hipotéticos sobre el impacto real de este tiempo de espera:

• Duración promedio de partida (Escenario Hipotético): Un tramposo con Fly o KillAura liquida una partida de SkyWars rápido, promediando unos 4 minutos por juego (incluyendo lobbies).
• Partidas estimadas: Si el infractor jugó sin parar durante las 10 horas y 29 minutos (629 minutos) que tardó en caer el baneo:
  629/4 min(por partida) = 157 partidas jugadas
• Impacto probable en la comunidad: En SkyWars Solo (11 víctimas por mapa), este único hacker pudo arruinar la experiencia de aproximadamente 1,727 jugadores. Si jugó en Teams, la cifra supera fácilmente los 3,500 usuarios afectados en un solo día.

Conclusión:

Este cálculo estadístico no es un hecho absoluto, sino una simulación de lo que un solo usuario puede lograr en el servidor. No busca demeritar al staff, que cumplió con banearlo, sino demostrar por qué la mejora constante del Sentinel es vital. Los reportes manuales son una excelente red de seguridad, pero por pura probabilidad matemática, la automatización inmediata es la única forma de evitar que miles de personas sufran una mala experiencia antes de que un moderador humano pueda intervenir.

English
Hello, I'm sorry to be the bearer of this bad news, but that's not entirely accurate either. As the evidence shows, I submitted the report at 9:09 AM, and the user was sanctioned approximately 10 and a half hours later.

Supporting the debate about the Sentinel system versus the manual system, I'd like to present a probability analysis and hypothetical data on the actual impact of this waiting time:

Average match duration (Hypothetical Scenario): A cheater using Fly or KillAura can quickly finish a SkyWars match, averaging about 4 minutes per game (including lobbies).

Estimated matches played: If the offender played nonstop for the 10 hours and 29 minutes (629 minutes) it took for the ban to be issued:

629 / 4 min (per match) = 157 matches played
Probable impact on the community: In SkyWars Solo (11 victims per map), this single hacker could have ruined the experience for approximately 1,727 players. If they played in Teams, the number easily exceeds 3,500 affected users in a single day.

Conclusion: This statistical calculation is not an absolute fact, but a simulation of what a single user can achieve on the server. It is not intended to diminish the staff, who fulfilled their duty by banning the user, but rather to demonstrate why the constant improvement of Sentinel is vital. Manual reports are an excellent safety net, but based on pure mathematical probability, immediate automation is the only way to prevent thousands of people from suffering a bad experience before a human moderator can intervene.