LogoLogo
Join The CommunityCommunity ResourcesLuafaq.orgLua Org
  • Welcome
  • Frequently Asked Questions (FAQ)
  • Legacy API
    • Test The API
    • Warning
    • Character
      • v1/wear
      • v1/remove
    • Games
      • v1/games/details
    • User
      • v1/user/request-data
      • v1/user/avatar
      • v1/user/get-by-username
      • v1/user/get-token
      • v1/user/verify-password
      • v1/user/login
      • v1/user/chat/send-message
      • v1/user/chat/chat-summary
      • v1/user/get-messages
      • v1/user/chat/chats
      • v1/user/friends
      • v1/user/friend
      • v1/user/search
    • Guild
      • v1/join
    • Asset
      • v1/sell
      • v1/take-offsale
      • v1/purchase
      • v1/purchase-reseller
      • v1/create
      • v1/get
  • OPEN CLOUD
    • READ ME
    • NPM Package
      • Introduction
      • Tutorials
        • Webhook Configuration
      • Bot Account
      • OpenCloudClient
      • WebAPICliet
        • Client
        • login
        • quit
        • Friends Endpoint
          • SendFriendRequest
          • GetFriends
        • User Endpoint
          • GetAvatar
          • GetPlayerByUsername
        • Guild Endpoint
          • JoinGuild
    • Open Cloud
    • Webhooks
    • Asset Types
    • Beautiful JSON Display
    • V2 API
      • Asset
        • Edit
      • Publish
        • Asset
        • World
      • Feed
        • reply
        • all/{page_cursor/{feed_cursor}
      • Cloud
        • oauth
          • create
        • git/{channel}
        • version
        • database
          • get
          • set
        • credentials
          • list
          • delete
          • create
        • bricklinks
          • list
          • delete
          • create
      • Webhook
        • delete
        • create
        • list
      • User
        • feed
          • send
        • search
        • register
        • login
        • username-available
        • email-available
        • phone-available
        • validate-beta-key
        • id
        • username
        • edit-setting
        • transparency-request
      • Auth
        • send-beta-key
        • get-active-sessions
        • terminate-session
        • get-token
        • session
        • is-authed
        • join-game
        • bot-login
      • Notifications
        • unread
        • all
        • erase
      • Worlds
        • /{universe}/{server}/server/metadata/update/{token}
        • /{universe}/shutdown/all/{token}
        • /{universe}/shutdown/server/{server}/{token}
        • /{universe}/join/server/{server_id}
        • /{universe}/join/random
        • /{universe}/join/user/{user_id}
        • /client/{join_key}
        • /create-universe/{ownerId}/{ownerType}
        • /create-world/{universeId}
        • /worldtree/{worldId}
  • Developer Guide
    • Empowering Responsible Gameplay: A Guide to ModerationService in BrickVerse
    • Empowering Game Creators: A Deep Dive into ENVService with Lua API in BrickVerse
    • Leveraging ENVService as an FFlag System
    • What's Authority?
    • Roblox Vs BrickVerse Classes
    • DRM - Digital Rights Management
  • BrickLua - Coding With Lua
    • Introduction
    • Learn Lua
      • Functions
      • Strings
      • Tables
      • Boolean
      • Conditional Structures
      • Opeartors
      • bit32
      • Numbers
    • Player Event
  • GAME API
    • API
      • Intro
      • math
      • debug
      • coroutine
      • Enum
        • UserInput
        • Humanoid
    • Classes
      • ServiceProvider
        • Enum
        • InteractionService
        • ENVService
        • Void
        • WorldstoreService
        • WorldSettings
        • DiscordRichPresence
        • ClientGui
        • AuthorityService
        • SharedStorage
        • WebService
        • RunService
        • NetworkService
        • AdService
        • UserInputService
        • Scene
        • ChatService
        • Lighting
        • SoundService
        • Players
        • ServerStorage
        • ScriptService
      • DataType
        • CFrame
        • Instance
        • Vector2
        • Vector3
        • Color
      • Dynamic
        • Dynamic3D
          • SpotLight
          • SpawnPart
          • Projection3D
          • PartMaterial
          • OmniLight
          • BasePart
          • InteractionPrompt
          • Page
          • DirectionalLight
          • Brick
          • BasePartConstraint
        • ScriptDynamic
          • ScriptModule
        • BaseUI
          • ScrollFrame
          • ImageButton
          • TextButton
          • ImageLabel
          • TextLabel
          • Frame
          • ViewportFrame
          • ScreenUI
  • Employment
    • List Of Administrators
Powered by GitBook
On this page
  • Introduction
  • ModerationService Overview
  • Best Practices for ModerationService

Was this helpful?

Edit on GitHub
  1. Developer Guide

Empowering Responsible Gameplay: A Guide to ModerationService in BrickVerse

Introduction

Welcome to BrickVerse, the dynamic social platform that empowers teens to unleash their creativity and craft captivating gaming experiences. In this developer article, we'll delve into the robust ModerationService provided by BrickVerse, a powerful tool designed to maintain a safe and enjoyable environment for all players. ModerationService allows game creators to enforce rules and regulations seamlessly, ensuring responsible gameplay and fostering a positive gaming community.

ModerationService Overview

ModerationService is an integral part of BrickVerse, offering developers a comprehensive set of tools to moderate in-game players effectively. This service enables the enforcement of rules and policies by targeting players through their Hardware ID (HWID), IP address, and UserId. With features such as kicks, temporary bans, and permanent bans, ModerationService empowers game creators to maintain a healthy and secure gaming environment.

For privacy reasons we will not display HWID, IP addresses, etc. to game developers or players. This is strictly automated internally.

Basic Usage

Integrating ModerationService into your scripts is straightforward, thanks to the user-friendly design of BrickVerse's API. Here are some basic examples of how you can utilize ModerationService:

-- Temporary ban ArkInfinity for 10 hours with a reason
game.ModerationService:TemporaryBanAsync(game.Universe.Players.ArkInfinity, "Reason", 10)

-- Permanently ban ArkInfinity with a reason
game.ModerationService:BanAsync(game.Universe.Players.ArkInfinity, "Reason")

-- Kick ArkInfinity from the server with a reason
game.ModerationService:KickAsync(game.Universe.Players.ArkInfinity, "Reason")

These simple calls demonstrate the versatility of ModerationService, allowing you to take appropriate actions against players who violate the rules of your game.

Key Features

  1. HWID, IP, and UserId Moderation Link: ModerationService provides the flexibility to moderate players based on various identifiers, ensuring a targeted approach to rule enforcement.

  2. Temporary and Permanent Actions: Whether it's a temporary ban for a specified duration or a permanent ban, ModerationService offers the flexibility needed to address different levels of rule violations.

  3. Reasoning: Adding a reason when applying moderation actions enhances transparency and communication. Players will understand why a particular action was taken, promoting a sense of fairness.

Best Practices for ModerationService

  1. Clear Rules: Clearly define and communicate the rules of your game to players. This helps in justifying moderation actions and encourages responsible gameplay.

  2. Consistent Enforcement: Apply moderation actions consistently to maintain fairness and trust within the gaming community.

  3. Periodic Review: Regularly review and update your moderation policies to adapt to evolving community dynamics and ensure the continued effectiveness of your rules.

Previous/worldtree/{worldId}NextEmpowering Game Creators: A Deep Dive into ENVService with Lua API in BrickVerse

Last updated 1 year ago

Was this helpful?