hiyas "Do not share or exploit sandbox breaks, as that is against the rules and will result in disciplinary action." Sometimes whether or not something is a sandbox break is somewhat unclear, or requires research with other people who know more about what's going on (ie ast). In the case where something's clearly 100% a sandbox break then yeah, but it might be worth slightly softening the "do not share" one because identifying the full ramifications of something might be unclear without help, and nobody wants to spam the xean without knowing for sure that something's an issue That said it slightly depends who these rules are for - as far as I know, behind closed doors the vets have always somewhat taken the stance that collaborating is fine for research purposes, so back when i played more people used to share that kind of info with people considered responsible parties (ie a lot of the sandbox members, eg where i posted the whole development of rng hacks) There's always been a greater sense of obligation towards the vets for helping take care of the state of the game compared to new players, and vets have generally acted with their own judgement towards this kind of thing, and that could potentially be officially codified, left unspoken, or sharing that kind of content officially banned with rules like this. Either is fine, but its probably worth clarifying if that's something that's intended to be cracked down on That said there are a few semi public sandbox breaks floating around, so there's definitely an element of being responsible by the vets however you go with this

Excuse my rambling. So, ideas for what counts as a Sandbox Break, based on my limited knowledge: - Anything that allows viewing or interacting with internal game infrastructure via unintended methods: - Being able to view or interact with internal databases, such as the one holding all scripts. - Being able to view sensitive or game-irrelevant information from internal game infrastructure. - Being able to see or edit source code of scripts you do not own, besides game-intended ways such as the owner of said script utilising scripts.quine. - Being able to manipulate GC balance without the use of the intended acct scripts. - Being able to modify upgrades. - Being able to bypass an upgrade's specified specs or cooldown. - exploiting trust scripts, such as sending more than 32BGC to a player in a single transaction. Generally, manipulation of the sandbox often requires a special game-provided script that controls the caveats of the action. If you can break the caveats of the script, use it to do something it wasn't indended for, or even manipulate the sandbox without the use of a game-provided script, chances are that it's a sandbox break. - Being able to buy something from the market for lower than the listed price. - Being able to upload a script when you do not have enough char counts. - Using PvP actions on game infrastructure users (unless told you can do that, like Walter). - Creating or modifying upgrades (unless made via a hidden script intended for player use) Now, here's the fun part: there is a way to transform certain upgrades into an almost exact replica of another. This is possible due to an unintended side effect with a trust script, and I would call this a sandbox break. You have allowed usage of it though; why was that? What makes it different from any other sandbox break?

I don't think this is a sandbox break. "Alchemy" operates entirely within the sandbox and is rather a game balance issue. It was reported to Sean when it was originally discovered and he made the decision to allow it. The reasons for him doing so are irrelevant and don't change whether or not it should be considered a sandbox break.

Sorry for the slow reply on all this. Thank you so much for your comments and feedback! I've integrated them into the newly updated post! https://hackmud.com/forums/general_discussion/how_to_report_issues Please share more comments / corrections / ideas as you have time and energy for this. :D Thanks again for your comments so far!

If the answer to the question or the deployment of a fix would give you a competitive advantage as a reporter, then report to support@hackmud.com If the question itself is a competitive advantage, then report to support@hackmud.com why no If the answer to the question or the deployment of a fix would give you a competitive advantage as a reporter or if the question itself is a competitive advantage, then report to support@hackmud.com is same also ... or if your issue is wont fix'd,... wots a wont fix'd

Thanks Ghamb! Updated.