Please make sure to go through the Basic Installation before going through with this setup. Post feature requests, report bugs, and have in-depth discussions about knowledge management. if you want Moderators names to synchronize, you need to have the Bot role above the Moderator role) Get help, ask quick questions, and get to know other Obsidian users and their setup Obsidian forum. Make sure the new Bot role is above any roles you want to synchronize using our role/nickname synchronization system (eg. Required for the voice lobby and voice category Move Members, Mute Members and Manage Permissions Optionally for embedding ingame-posted links and required when embed messages are used death, join/Leaveįor mentioning if added to allowed mentions in config.yml and mentions enabledįor when the bot reacts with "?" and "❗" to notify a truncated message is being sent from Discord to Minecraft When messages are deleted by playerlist & chat channel commands Required for DiscordSRV's channel options (including console and voice lobby), the voice module category and any other channels you want for canned responses (Server-wide permission is recommended, but can be applied on a per-channel basis) Role synchronization and adding roles to linked playersĬhannel topic updater and the voice module This list can/will change and new permissions will need to be added for any new features that require them. If you don't feel comfortable with this, you can define the following permissions that the bot requires for certain features. The only way this can be abused is by keeping the bot token secure. We recommend it because it makes the installation process easier on the server owner, and DiscordSRV doesn't do anything that would jeopardize the server. Usually it's not recommended to give the bot the Administrator permission, since it gives the bot complete control over your server. You'll be surprised with how many features this plugin hasĪdvanced Information ? Giving the bot the administrator permission ? Now run through all the config options in config.yml. Set the Role ID(s) and group name(s) in the synchronization option Get Role ID(s) for the role(s) you want to sync Get the name(s) of the minecraft group(s) you want to sync Giving the bot the administrator permission Give the bot the discord permissions it needs to run įrom the bottom of our hearts to all of you, thank you.Enable the Privileged Gateway Intents options Phun and I couldn't have done this alone.Īnd to the amazing Staff we've had the pleasure of working with over the years, we love each of you dearly and you'll always be family. Most especially, we want to thank those of you that believed in WebFlake and supported us financially through donations. We want to thank you, each and every person that has visited, discussed, provided support, shared content, and has helped provide a home for fledgling creators all of these years. In the unlikely event that we ever decide to reopen, we will notify you via our Twitter our Discord which will enter read-only in a few short weeks as well. We don't have alternatives though and we would much rather go out on our terms than just fade into obscurity, which we are dangerously close to doing. It's not lost on us that by closing WebFlake we're ending this chapter in our lives but also sealing a wealth of information and content from the world. Phun and I love this community and we've enjoyed working with so many amazing people over the years.
#SERVER FOLDERS DISCORD PLUGIN SOFTWARE#
I'm not saying forum software is obsolete or that forums are no longer useful - I'm saying that WebFlake cannot continue to find sustained success distributing unlicensed software in a market that's driven by instant gratification. Forums simply don't hold the same appeal that they once did. I love Discord and I don't blame its success for WebFlake's recession. Over the last couple of years, with the advent of Discord and other content management solutions, we've seen a dramatic dip in interest. WebFlake has seen its fair share of ups and downs. But was it really? I've seen an untold number of wonderful, well-intentioned communities rise up and blossom into magnificent creations that otherwise wouldn't have been possible. We've always known that on some level, both ethically and legally, that WebFlake was "wrong". Building a community of aspiring webmasters that just wanted a fair shake at constructing their dreams without the mind-numbing costs that are associated with sophisticated forum software. Together. In essence, that's what WebFlake was always about. In that time, we accomplished both the unthinkable and the impressive. Next month would mark nine (9) years since WebFlake first launched. This is a difficult announcement, and while I always thought I could assemble some grand soliloquy for this moment, I'm honestly just going to wing it.