Status
This thread has been locked.

Meeran

Supreme
Feedback score
3
Posts
108
Reactions
35
Resources
0
Hello everyone!

I am planning to release my report system on MCMarket for roughly 15$USD per jar and $30USD for source code (Limited copies of source will be sold), some of the features already implemented/planned are;
  • Player Report Counter - Similar to MineHQs
  • Cross-Server / Single server communication - You can use your choice of Redis messaging (Useful for Mutli-Proxy setups) , Bungee messaging, RabbitMQ or just standalone use.
  • Deep integration into different messaging platforms - Discord, Slack, Telegram
  • Choice of GUI based or text based - Great way to support different Gamemodes.
  • Every message is customisable in config.yml - We are planning to add multiple language support
  • Cooldowns and report exemptions - These can be edited to your liking in the config
  • Ability to show past reports - Can either use Mongo or MySQL
This plugin will be coming out in the coming weeks, however I am looking for more suggestions/features to implement so that any server can use this plugin for their use case.

My Developer has extensively tested a system like this on a network with several servers using Redis and Mongo with player counts upwards of 100 players so this is battle tested to be perfect for any large network. We will be accepting vouch copies in the future, we are just waiting for a more polished product to show the general public.

This is an example of the telegram feature within the report system
PuuhGzm.jpg


We hope you are interested in the plugin and provide good suggestions to make the plugin even better!
 
Last edited:

Meeran

Supreme
Feedback score
3
Posts
108
Reactions
35
Resources
0
if i found out a server had this i'd spambot the shit out of this lol nice try
I mean you could go on to any other server and abuse that system aswell, but it is up to the server owner to enforce rules revolving around the use of the command.

That much detail for a reports plugin?
I am trying to cater to as many servers as possible by delivering the most features. Keeping in mind all of this is modular if you do not require a certain feature you can disable it, therefor making the plugin very versatile for any server owners needs.

I'd make it support Discord as you might get more people to look into it, but I would add more details to when the report goes in.

Example it'd pull up other information from the user if they have been reported before.
There is a discord feature planned it will display information such as: Time, Server, Player Version, Player Name, UUID, Gamemode, Report reason, reports in the past 60 minutes, etc. Keep in mind these will all be placeholders as you can create your own message formats in the config.yml
 

Meeran

Supreme
Feedback score
3
Posts
108
Reactions
35
Resources
0
My mistake, You should add ArangoDB or Redis support.
All good. Redis support is already implements but in-terms of ArangoDB I have actually never heard of it, but simple research suggests that it is very similar to MongoDB, but I can definitely look into that as a database possibility! Thanks for the suggestion.
 

Missionary

Premium
Feedback score
2
Posts
313
Reactions
245
Resources
0
All good. Redis support is already implements but in-terms of ArangoDB I have actually never heard of it, but simple research suggests that it is very similar to MongoDB, but I can definitely look into that as a database possibility! Thanks for the suggestion.
I would not use Redis for storing any data that needs to persist without data loss unless your using Redis' Append-only file (AOF) persistence method. Although using AOF can be great at making sure all your data is being persisted, there are 2 down-sides to this: file size and database performance depending on fsync settings. By default, Redis uses the RDB (Redis Database File) persistence method which takes snapshots of your data at specified times which can lead to data loss in the event something happens. Redis is sort of like memcached, they are both volatile in-memory databases with Redis having a few exceptions (e.g. the ability to persist data somewhat reliably). There are many great articles about how Redis persists data on stack overflow and the RedisLabs website. Just my opinion.
 

Meeran

Supreme
Feedback score
3
Posts
108
Reactions
35
Resources
0
I would not use Redis for storing any data that needs to persist without data loss unless your using Redis' Append-only file (AOF) persistence method. Although using AOF can be great at making sure all your data is being persisted, there are 2 down-sides to this: file size and database performance depending on fsync settings. By default, Redis uses the RDB (Redis Database File) persistence method which takes snapshots of your data at specified times which can lead to data loss in the event something happens. Redis is sort of like memcached, they are both volatile in-memory databases with Redis having a few exceptions (e.g. the ability to persist data somewhat reliably). There are many great articles about how Redis persists data on stack overflow and the RedisLabs website. Just my opinion.

Hi it seems there is a misunderstanding about how we are using Redis. We are not using Redis for its persistent storage (as it is not the most efficient way to do things but instead I am utilizing Redis for its PubSub (Publish and Subscribe) channels. This is for people with a multi-proxy setup and it will send it to every server that has the plugin (the plugins can communicate to eachother without even a proxy, just a simple jedis pool connection). Thank you for explaining why we are not using Redis as persistent storage, I do value understanding how best to optimise plugins so that the server owner can reap the rewards. If you have any other queries be sure to just reply or direct message me if need be.
 

Cranked

Owner of Cranked Factions
Premium
Feedback score
25
Posts
443
Reactions
194
Resources
1
I’d definitely buy this if there was support for a discord bot in a staff only chat room.
 
Status
This thread has been locked.
Top