The more structures a modpack has, the more I appreciate this both as a player and as a modpack dev.
Reputation ranks
Ranks only ever go up; points can drop but your rank stays.
About reputation ranksModerates flagged and pending content, enforces the reviewer guidelines, and keeps project pages accurate.
This review is their own opinion. Staff reviews follow the same guidelines and moderation as everyone else's.
WITS is an incredibly simple mod. Don't know what mod the structure you just stumbled upon is from or want to know specifically what it's called? /wits will tell you. But what if there are multiple structures nearby? /wits will list them all. Importantly, it does both of these without needing to enable cheats.
This is great for two main scenarios:
-
I'm playing a modpack with either unfamiliar structure mods or a large amount of structure mods.
(If I like the structure, I might want it for my own modpacks. Or maybe the structure makes more sense contextually once I see what mod it's from.) -
I'm playtesting a modpack I'm developing, and I curiously happen upon a structure.
(This is useful in a few ways, such as changing a structure's spawn rate, spawn radius, or otherwise tweaking it; Without WITS, I wouldn't know what structure to tweak.)
Given its simplicity and straightforward execution, I add this to pretty much every modpack I make.
As an aside...
I actually didn't know about the admin tool to target a specific spot in a specific dimension, as opposed to just wherever you happen to be. Personally idk how I would apply this, as my first thought to check a structure where another player is would be /execute as <player> at <player> run wits, but /execute at <player> run witsop ~ ~ ~ could work too.
