Jump to content

totemo

Tech Admins
  • Content Count

    785
  • Joined

  • Last visited

Community Reputation

438 Excellent

1 Follower

About totemo

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Australia

Recent Profile Visitors

1,672 profile views
  1. User bruno_vera Issuer totemo Server p.nerd.nu Reason xray on pve nerd.nu/appeal Time Banned May 2, 2019, 5 a.m. Sorry to keep you waiting. I only found out about this appeal today. At the time, your inventory was cleared and all your edits removed from the world, and the same treatment applied to DonGusY2K. That was a year ago and the map has been reset twice since then. The normal ban duration for a first time offence is 1 week, which has long since passed. Please be mindful of the rules this time around. You are unbanned. DonGusY2K will need to open an appeal to be unbanned if you want them to play as well.
  2. Players who get banned stay banned until they appeal. It doesn't matter if it was last week or 3 years and 3 months ago. User fran_ (e722d359-e2a3-4a64-9738-f69a18844ce6) Issuer totemo Server c.nerd.nu Reason xray on PvE nerd.nu/appeal Time Banned Feb. 3, 2017, 4:30 p.m. I don't have the screenshots any more so we can't really talk about that. You're unbanned.
  3. User coolkid1455 Issuer totemo Server c.nerd.nu Reason fly hacks, crop grief, advertising on P nerd.nu/appeal Time Banned Feb. 3, 2016, 4:31 p.m. You're unbanned.
  4. Ban details: User WhiteTileMozart Issuer totemo Server p.nerd.nu Reason xray/xray resourcew pack on PvE nerd.nu/appeal Time Banned April 4, 2020, 10:22 p.m. All of your edits have been removed from the world. The ores that you mined have been removed from the world after the rollback. Your inventory and ender chest have been cleared. The ban duration is 7 days for xray. Longer on repeat offences. You start again from scratch on the 11th of April. If I forget to unban you, you can comment here as a reminder to us. It's customary to show evidence. I have a wide selection of screenshots. Since you've admitted fault, just one example of xray rule violation will do, herewith, three screenshots: before, before and after you removed the diamonds. First before shot shows your tunnel with the diamond put back.
  5. Thanks for being up front. Bit busy at the moment. The ban duration is 7 days. I'll deal with your appeal in full later today (my time zone).
  6. FWIW: Dedotating moar wam didn't help. Switching (back) to Aikar's JVM flags didn't help. What has worked absolutely stunningly well is waiting for the PaperSpigot guys to add more chunk loading optimisations. The server's running a lot better today and I attribute that to PaperSpigot build 155. The previous build was 146. They optimised a few things in between. https://papermc.io/ci/job/Paper-1.15/changes Build 156 has even more chunk-related optimisations, so we'll try upgrading again.
  7. https://wiki.nerd.nu/wiki/Server 6 physical cores, 12 virtual. All the map and config are on the SSD. 16GB/64GB allocated to PvE. JVM flags: java.cli-extra=-Dlog4j.configurationFile=/home/minecraft/shared/log4j2.xml -XX:+UnlockExperimentalVMOptions -Xlog:gc:gc.log -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Garbage collection pauses about a tick every 20-30 seconds: [716.024s][info][gc] GC(55) Pause Young (Normal) (G1 Evacuation Pause) 10809M->1170M(16384M) 31.630ms [746.407s][info][gc] GC(56) Pause Young (Normal) (G1 Evacuation Pause) 10802M->1188M(16384M) 29.309ms [772.753s][info][gc] GC(57) Pause Young (Normal) (GCLocker Initiated GC) 10820M->1201M(16384M) 29.421ms [798.676s][info][gc] GC(58) Pause Young (Normal) (G1 Evacuation Pause) 10833M->1218M(16384M) 32.409ms But that's with 24 players. It tightens a bit under heavier load but still on the order of tens of seconds between pauses. It's running on Java 11 atm. I encountered stability issues on Java 13, with Shenandoah; 12 was fine but is no longer getting updates. Spigot timings have not been helpful in pinpointing the issue. My current theory is that chunks are getting hindered on the way out of the box. They're clearly loaded, since physics does work in invisible chunks, e.g. swimming. The chunks are just not reaching the client. Mob counts are sufficiently low. Timings are good enough. So I'm looking at extricating plugins that utilise ProtocolLib (LibsDisguises) so I can test without that plugin-based network code. It takes time to make those code changes, however. The other candidate I want to look at is taking the BungeeCord proxy out of the loop. That's where our ban management happens, so again there is work in extricating it. I would not be at all surprised if it turns out to be an algorithmic complexity faux pas in some bit of network-queue processing code. Since it only really kicks in above a certain load level, and then really bites. Like a polynomial algorithm or exhausting some time allocation per queueing theory. Open to suggestions on freely available tools I could use to track it down. But bear in mind: it has to be debugged on a box with similar load and hardware specs. And fiddling with JVM flags and even the Java version itself has made fuck all difference over the last two versions of Minecraft. We're running at decent enough TPS up to about 50 players. Also, the general consensus on https://reddit.com/r/admincraft is that Minecraft performance sucks. And finally bear in bind that the time I spend humouring armchair experts (not to denigrate your particular skills) takes away from the time and energy I have available to (start) meet my current deadlines. I might also add that MobLimiter had a severe impact on TPS and has been reconfigured not to load extra chunks (synchronously on the main thread!). That's another avenue of investigation.
  8. We clear out all of you edits and inventory because it's hard to be certain that you haven't used xray in more subtle ways than we were able to detect, and xrayed materials allow for faster progress in the game. You have the pleasure of starting over from scratch. You're unbanned.
  9. User Altun505_ Issuer totemo Server c.nerd.nu Reason xray on pve nerd.nu/appeal Time Banned Sept. 4, 2019, 11:14 p.m. Please read the ban duration guidelines. http://wiki.nerd.nu/wiki/Server_Policies#Ban_Duration_Guidelines Please re-familiarise yourself with the rules, particularly those pertaining to x-ray: http://www.redditpublic.com/wiki/Rules You're banned for 7 days from the time of the ban. On the 11th, comment here as a reminder to me to unban you. Your name comes up a lot in modreqs, in a bad way. Taking things, killing pets, annoying people. Stop all that. You took a shulker. We've returned that. I don't want to hear of a similar incident happening again. This is why you were banned:
  10. That command is /usepack silent-dragon. You'll need to allow the server to send you resource packs. Any problems: clear out ~/.minecraft/server-resource-packs and try again. You can alternatively download SilentDragon.zip from https://nerd.nu/resourcepacks to your Minecraft resourcepacks folder and install it through the client. There's also /usepack windy-dragon if you would prefer (I do) a fart sound instead of absolute silence. EDIT: I should add that I implemented these as of just a few minutes ago.
  11. I think it would be technically feasible to develop something for 1.14 that allows TNT outside WorldGuard regions, but disallows TNT damage to player-placed blocks, villagers, passive mobs, named hostile mobs and hangings. That is, protections over and above what WorldGuard offers. We already have BlockStore, which knows whether a block was placed by a player and could be used in the implementation. For the protection of structures built on top of natural terrain, e.g. rails on original stone, it might be prudent to make TNT fizzle when the list of blocks affected by the explosion includes player placed blocks (indicating proximity to a build). The above would not be foolproof but might be low-enough risk to try.
  12. Aizen_OP and Firesjin are both unbanned.
  13. User Firesjin Issuer totemo Server c.nerd.nu Reason xray on pve nerd.nu/appeal Time Banned June 2, 2019, 3:39 a.m. Ban duration guidelines: http://wiki.nerd.nu/wiki/Server_Policies#Ban_Duration_Guidelines The rules, which you should read, particularly those pertaining to x-ray: http://www.redditpublic.com/wiki/Rules You're banned for a week, until the 9th of June. Your inventory and edits have been wiped. You've been xraying diamond exposed next to lava. I won't bother with all the screen shots I took since you're admitting it, but here are a few just for proof, paired with images of how the area looked before you mined it.
×
×
  • Create New...