Francinum Admin Report again

I did it. I don’t believe I did anything wrong in doing so.

I tried to delete it outright, it was declined.
Cargo can no longer sell BZ via cargo. by francinum · Pull Request #3514 · BeeStation/BeeStation-Hornet · GitHub

If you would like me to try again, I can.

1 Like

Oh I didn’t even read the entire post and missed this gem because I was on mobile.

I am incapable of issuing github bans, and I was not even paying attention to who was responsible for the scrubber array when I bombed it.

I don’t care who’s doing it.

1 Like

Fixing things via code sounds nice, but given how different systems interact, it can be hard or impossible.

For example, the TEG can be easily exploited to generate free electricity by using a freezer and heater connected to it. For gameplay reasons, it costs very little energy to heat or cool gas, but that same gas will generate a large amount of electricity in the TEG. Connecting a heater and cooler to a TEG will result in a large energy surplus.

Since this cannot be resolved via code easily, it is considered an exploit. Players that perform this exploit will find that their setups mysteriously explode, and if they keep doing building them, that they will receive OOC warnings or even punishment.

In this case, the player was making a gas filtering setup on Lavaland, which causes server issues due to lag, and is also exploitive of the economy because for a trivial effort to setup it generates infinite credits endlessly.

Working entirely alone and doing my mandatory shift duties, this (decent looking and optimized) set up took nearly an hour

Since when was atmos farming considered an exploit

Local admin shamelessly admits to intervening

lol why threaten me like I care what you do to your codebase. As if my (or anyone’s) opinion was factored in


I meant a personal block, not a repo ban:

You can’t report anyone for personal blocks.

If you think you are being targeted specifically I got great news for you: you are not targeted by Fran.

i retracted this and that was not even the point.

1 Like

I think it’s safe to say nobody knew you were jlsnow, the name is considerably different.

Would you expect them to deny it when there are clear logs…?

We are expected to intervene for the sake of the server and most of us do semi-regularly in more minor ways to keep things moving, or to bring long rounds to a close.

That said, I’m not endorsing this specific circumstance unless the server was already choking. I feel the same about it as I did when a different admin sabotaged an established meta fusion setup because the logic didn’t make sense to them - unless it’s exploit or the server was reaching a breaking point, I don’t agree with blatant sabotage of a setup.

I do agree that atmos farms are detrimental to the server in many ways, but in a way that requires maintainer approval to fix rather than admin intervention.


This is a long-term thing.

But I would say for the short-term, admins have been generally allowed to destroy lag machines (for example someone making too many circuits even if their actions aren’t specifically harmful.)

Thank you for this pretty impartial review. I remember reading about this fusion instance as well.

That said, I think it’s a bit toxic to sabotage systems on personal preference. Intervention without rules is not enforceable, at least not impartially, as there is no documentation saying “hey don’t do this” or “we’ll just delete your machine if we disagree”.

I have been messaged before not to do sm setups as it’s an exploit and apologized / quit before. That’s perfectly reasonable. But stealth sabo at random is poor conduct.

I want to reiterate that if the server was currently losing its shit, I am on board with the sabotage of something that would be processing-intensive, including stealthily.

Wasn’t speaking against doing this, but I also was not aware that these types of farms had the level impact they do until now.

Open air fusion has similar impact and yet someone elected to remove canister fusion, leaving it as the only option

If this is such an issue, then why are the guides for it still up if the administration does not approve of it?


Because it was in the midst of rebalance and removing it would be unbecoming of because its still a feature of beestation.

The justification of nuking is for server performance which is well justified (But i really doubt its that bad). There are many other processes at play now with recent merges i suspect. So keeping the health up is fine.

Lavaland mining is nuked anyway. Go home everyone

From admin policy.

I mean you literally see two admins disagreeing in the first post. This thing has been controversial back then which is probably why the guides weren’t outright deleted.

Defining what’s an exploit and what’s “too laggy” isn’t very simple and is only really definitive once headmins get around to dropping a ruling.

Or a fix is merged - lavaland gas mining has officially been removed because of the proven negative impact it has on server performance (and the fact it’s an additional nail keeping our economy in a coffin doesn’t help)

Gonna lock this until headmins reach an official decision.

After full review between Head Admins this report has been deemed Not Actionable. @Francinum acted in the best interests of server stability

The admin interfered with something known to cause performance issues on the server at a time when it was already facing performance issues, and we have since rolled out a fix to discourage players from performing these same actions again on a code level.