You can try, but are you really interested in dealing with:
Server hosting
Community management
Repository management
Administrative organization
Writing fresh policy
Finding and/or training an entire staff team
And more.
You can try, but are you really interested in dealing with:
Server hosting
Community management
Repository management
Administrative organization
Writing fresh policy
Finding and/or training an entire staff team
And more.
Getting pop is actually the hardest part.
This as well, though for someone whoās biggest complaint is the removal of one feature, Iām reasonably sure theyād hit technical and administrative policy walls first before even caring about gathering pop.
But shouldnāt people be rewarded for learning something very deep? More effort for more reward, no?
Also, canāt you just make it a rule that whoever makes the circuit is largely responsible for the damage it causes? Just log whoever made it.
We can log a million things and make a million rules. TG did the same to NTSL.
A feature dies if the maintainer team is unwilling to support and care for it. Which at the very least me and Elon are not.
Whatās NTSL?
Their reason for circuit removal isnāt griefers using itā¦ I think.
I still donāt know their reason.
No, just log a few basic things and make a basic rule.
Log who made it, if the circuit gets out and harms people and youāre not antag man you get beaned.
Nanotrasen Telecommunications Scripting Language. A rather impressive piece of code that is basically a prototype of telecommunications circuits.
Hereās one of the more popular scripts from back in that day, as an example of how complex the stuff is.
We already have a staffing problem. Letās solve problems that we can just not have to bother with by requiring more staff attention.
I donāt understand, how does this require more staff?
I donāt have a problem with deep and complex features at face value, the problem is that circuits, like NTSL, are essentially highly polymorphic balls of hot glue that tend to hide a lot of tiny pinholes and obnoxious bugs. NTSL quietly had the ability to completely break global randomness, mute all communications traffic, and I believe around the time of itās removal, and the catalyst for such after about 2 years of dealing with itās bugs in the exact way weāre dealing with the bugs of circuits: Crash exploits.
Of which circuits have already had their share.
Problems with circuits:
I, and other people who hate circuits, have no problem with them existing. What we do have a problem with is their current implementation, which needs to go for the health of the server. If you can satisfy the above problems with a rework, Iād be totally fine with their return.
If there are exploits that can do that stuff, go ahead and disable them entirely, I canāt argue against that.
I doubt anyoneās gonna fix them, soā¦
Farewell, beloved circuits.
iām waiting for when they apply the same logic from circuits to other systems. have fun with chemistry removed because āoh bomb can keel ppl itās not like thatās part of the gameā or if someone finds an exploit that allows them to duplicate items by deep frying them or something then āwell lets just remove all the dupable items so the bug is goneā
By the sound of it itās more about the exploits crashing the server.
Could we set up a code bounty for circuit exploits or would that cost too much?
Chemistry is well logged, well developed, and highly integrated into the rest of the games.
Circuits have none of these qualities. Donāt stir shit.
then fix it
iāve literally never seen a killbot itās not like we have no time to do coding
Do it your fucking self. Nobody else on the team wants to.
i am but people are coding it out faster than i can fix