Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Pecon

Pages: [1] 2 3 4 5 6 ... 368
Off Topic / Re: what can i do on windows 2000
« on: Yesterday at 03:33:25 PM »
there was someone that installed blockland on win 98 a while back, it only ran in like 16 colours or something it was pretty dope
you cant run bl on win98. at least not retail bl. unless someone did some trickery to get it working but ive never seen that happen
Blockland is compiled for Windows NT, so it's only possible for it to work on Windows NT-based systems.

I'm not sure why that is happening. Download it from here in the meantime:

Edit: This is now fixed, the download in the OP should work just fine.


AutoModerator is a server mod for utilizing publicly available machine learning models via API to automatically moderate your server's chat. You can even fine-tune what sort of things it is sensitive to, with 8 different moderation models to utilize. Contrary to what I might be implying in the title, this mod does not implement any machine learning in torquescript as that would be horrendous. Rather, this uses Google's Perspective API to brown townyze chat after it is sent. This mod obviously cannot completely replace human moderators, but it can help moderate chat in extremely hectic situations, and can help keep your server more peaceful when there are no moderators online.

  • Keep your server moderated to some degree 24/7. Give your fleshbag human moderators a break.
  • Unbiased and impeccable scrutiny.
  • Highly customizable sensitivity. Choose what moderation models to care about, what models to ignore, and everything in-between.
  • Keeps records separately from clients. Clients rejoining won't make the AutoModerator forget what they have done.
  • Accountable. Admins are always notified about the AutoModerator's decisions, and those notifications are also logged in the console for your record keeping.
  • Fault tolerance. In the case of a service outage, chat is cached and brown townysis re-attempted until service is available again.
  • Experimental mode. You can set AutoModerator into an 'experimental mode' in which it will never take actions, but will inform you of the actions it would take under its current settings. This makes fine-tuning your sensitivity values to fit your needs much safer.
  • AutoModerator will never betray you. Probably.

  • Acquire a Google API key with the Perspective API enabled. Follow these instructions until you have created an API key and enabled the API.
  • Download
  • Place it into your add-ons folder.
  • Start a server with Server_AutoModerator enabled.
  • Take the API key from step 1 and do /autoModeratorSetKey <your api key>.
  • Shut down the server. This will ensure the package preloader is installed correctly and your API key saves.
  • (Optional) Open and edit settings.cs to configure your settings.
  • Host anything you like with Server_AutoModerator enabled!

Settings and configuration:

AutoModerator has a lot of settings. To edit the settings, you simply open settings.cs from within the zip file and edit the settings to suit your needs, then restart your server. The comments in the file explain what each setting does.

Of these settings, the sensitivity settings are probably the most important. These settings show the 8 models the AutoModerator can evaluate chat by. A higher value in a category will make the AutoModerator care more about that category and take action more quickly when a user's chat violates that category. A value of 0 will completely disable that category. As long as a value is lower than 11, it is impossible for the AutoModerator to take action based off of a single message, but it will take action when it sees a trend of violations in that category. How quickly it determines that trend is based off the sensitivity value.

Available moderation models:
  • Toxicity - A general model aimed at detecting behavior that will generally drive people away from discussions.
  • SevereToxicity - A general model also aimed at detecting behavior that will drive people away from discussions, but focused on much more 'severe' behavior which overlooks a lot of behavior that could be considered more acceptable in informal communities.
  • IdentityAttack - A model that detects language that attacks a person or group's identity.
  • Insult - A model that detects insults.
  • Profanity - A model that detects profane language. (Default configuration disables moderating this category)
  • Threat - A model that detects threats of harm or injury towards other people or groups.
  • loveuallyExplicit - A model that detects language that is highly loveual. (Default configuration disables moderating this category)
  • Flirtation - A model that detects flirtatious language, pickup lines, etc. (Default configuation disables moderating this category)

Default values for moderation models in settings.cs:
Code: [Select]
$autoModSensitivity["Toxicity"] = 1.5;
$autoModSensitivity["severeToxicity"] = 4;
$autoModSensitivity["IdentityAttack"] = 5;
$autoModSensitivity["Insult"] = 4;
$autoModSensitivity["Profanity"] = 0;
$autoModSensitivity["Threat"] = 2;
$autoModSensitivity["loveuallyExplicit"] = 0;
$autoModSensitivity["Flirtation"] = 0;

In addition to these, there are also settings for changing the AutoModerator's name, adjusting the time of mutes, writing custom warning messages, and configuration for running your own middleware if you so desire.

Commands (Super-admin only):
  • /autoModeratorSetKey <api key>
  • /toggleAutoModerator

Attack of the middleware

Unfortunately, the Perspective API requires an HTTPS connection to connect to. This means that Blockland cannot connect directly to it, and some 'middleware' is required which Blockland connects to via HTTP, and the middleware then performs the HTTPS connection to the API to request chat brown townysis. AutoModerator is pre-configured with a public middleware I am hosting, so really you don't have to do anything about this if you don't want to. However, if you wish and have the capability you may want to run your own copy of the middleware. The greatest benefit to running your own middleware would probably be that you don't have to rely on the uptime of my server for your AutoModerator. If you want to run your own copy of the middleware, you can download a copy of it here: Once you have set up the middleware, you can change the middleware settings in settings.cs to configure your AutoModerator to use it.


Q: How does the AutoModerator punish players?
A: When a player triggers the AutoModerator, they will first receive a warning letting them know that the AutoModerator doesn't approve of their chat behavior. Subsequent incidents that trigger the AutoModerator for the same category of behavior will cause mutes of increasing duration (the durations can be modified in the configuration). The AutoModerator will never ban/kick players.

Q: Can this prevent spam/moderate gameplay problems?
A: No. This is only a chat moderator. And, at least for the moment, it doesn't deal with chat spam either.

Q: Will this stop me from saying [...] on servers??
A: That will depend entirely on how the host decides to configure the AutoModerator. By default, the AutoModerator is fairly lienient and will let you do just about anything at least once without triggering; but the host could easily decide to change the behavior to be more or less sensitive.

Q: Is this an invasion of privacy? Will the AutoModerator remember everything I say forever and stalk me on myspace?
A: Chat sent to the brown townysis API is fairly anonymized. Usernames are not sent alongside chat, and typically lacks conversational context. Additionally, the fact that most AutoModerators will run through the public middleware means that the chat coming from your server will be mixed up with the chat coming from any other servers also using AutoModerator. Sorting through this information to track people or log their chat in any meaningful way would be basically impossible. That being said, all chat sent to the brown townysis API is recorded and used to further train the machine learning models; but it's anonymous data.

Off Topic / Re: night discussion topic i guess [night 1111]
« on: June 15, 2019, 09:09:45 PM »
I hereby claim the remainder of this page in the name of everyone born in 1996, you cannot post in this page unless you were born in 1996.

Off Topic / Re: Create your own Blockland Forums Tier List!
« on: June 10, 2019, 03:23:17 AM »
I know you have all been waiting patiently for my tier list, thank you for your patience and here it is!

Off Topic / Re: Straight pride month thread
« on: June 08, 2019, 01:25:38 AM »

Drama / Re: who do you dislike 2: escape to africa
« on: June 07, 2019, 12:20:47 PM »
Now that is an initiative I can get behind.

Off Topic / Re: pride month thread
« on: June 05, 2019, 11:45:36 PM »
This is truly the best month.

Was this made by request?
No, I just noticed a trend of people using that feature and wanted to make something to defeat it because I found it annoying to have to actually consider that people could see what I was doing while logged in.

Updated to v1.1

 - Fixed links in posts not opening in a new tab/window like they should.
 - Fixed this breaking some forum functionality, such as the quote button when Quick Reply is enabled.

Depending on your userscript manager it may update the script automatically, or it might not. Safest bet is usually to reinstall if you want the latest version.

Glad to see the uptake going so well!

This userscript will hide your recent actions from public visibility in the "Who's Online" list by overwriting them with a view to the board index. This does not work 100% of the time, but it should be more than enough to keep your actions generally more private.

This userscript works by hooking the click event on all urls on the forum, and quickly requesting the board index before navigating to the link. Normally you might think it would be better to simply request the board index after each page load, but this does not work since there is a ~8 second cooldown before your last action can be updated again. Hooking only the urls also means that what you are doing could be revealed if you refresh the same page over and over again rather than navigating using the links on the page. As far as I can tell there isn't much of a better way to go about this due to the cooldown on last action updates.

To install this, you will need a userscript manager such as Greasemonkey (for Firefox) or Tampermonkey (for Chrome), or something equivalent since there are multiple others out there.

Quote from: sasuke.uchiha but the post was deleted
something something umm you gonna address this unrelated thing i decided to bring up in this topic

Nah. That would be off-topic.

what did they post the same  sort of garbage that everyone active in the day/night discussion threads spews all over the forums? It seems like the socially retarded crowd here is the only ones actually bothered by them
I'm not going to go diving through their post history, but here is a screenshot of some of the stuff that was just deleted before they were banned. There was some of it on the third page as well but I didn't have that page in my cache.

Pages: [1] 2 3 4 5 6 ... 368