The Slice of Life channel
This was a quick idea I had for my discord server that I thought was nice; a slice of life photos channel.
Here's the channel description and rules I set;
See a rainbow? Take a photo. Share random daily moments. No selfies or photos of people, keep posting to one photo a day, and use threads for discussion. Check pins for more details.
In the pin messages there's a quick guide on how to post photos safely, and slightly expanded rules to explain the why.
I've found it kinda nice just posting random photos in the channel. Doesn't have to be meaningful. I don't have to come up with a witty caption. Just a slice in time from my day.
2 notes
·
View notes
IT'S FINISHED!
Left to Right ->
Spikangelo, & Raph(Here)
Ghost In The Shell, Ghost & Ghostlets by @amevello-blue / @bluepeachstudios
Two Souls, Aoi & his little lion by @virgilisspidey
Shellshocked, Raph & his gremlins kids by @lieutenantbiscute
Cass Apocalypse, Uncle Tello & Casey Junior by @somerandomdudelmao
The Last Ronin Becomes A Discord Admin, Slonkangelo & The Little Ones by @melonpalooza
And finally, Snapper Lou Au, feat. Snapper Lou from @kittynomore, Nini from @amevello-blue, and The Eldest Brother AU from @debb987
PLEASE check out everyone here! Their works are amazing, and I bet you'll find something that'll stick with you for a while!
I noticed the quality gets screwed up when you zoom in, so I decided to export it myself so yall can see them better. Hope it helped!
Have a wonderful day, everyone!
Oh, and I added little easter eggs, too.
853 notes
·
View notes
YOU! Yeah, you!
Are you overwhelmed by social media? Yearning for the early 2000s internet with casual games, forums, fun graphics, and HTML customization? May I offer you a goat in these trying times?
Goatlings is a super cute, simple little pet + doll maker site I've been playing that I simply adore! I'm not sponsored for this or anything, I just really love this site and want to invite more ppl to join!
There's a handful of simple games to play, and a little explore + battle mechanic too. Think Neopets, but much more and better imo!
But the best thing is how low-key it is! There's very little FOMO. Just log in when you want, you can advance at your own pace. There are some time-limited things, but they're never out of reach, and honestly everything just continues to get better and better. New stuff is added all the time!
You can adopt cute little Goatlings and customize them and their pages!
There's also a built-in Picrew doll maker for your user icon! You collect items to build your inventory, and since this site has been around for a while, there are LOADS of items!
Did I mention there's a bunch of cute items to collect too? You can add them to your Goatlings pages as treasures!
Not only that, but users (artists and non-artists alike) are encouraged to submit ideas for everything on the site! Goats, things to add to the doll maker, items, anything! A ton of items are adapted from designs submitted by users. There are contests for them too, where everyone votes on favorites and you get prizes for winning!
There's also charity drives going on at all times, so if you like to throw money at indie game companies for their fun sites, you can do that AND help support a good cause 💕
Click here to check it out!
I do get a fun lil in-game referral bonus if you use this link, but you don't have use it. I'd be happy just seeing more friendly faces there!
(btw if you sign up, I'm Zillychu on there as well! Feel free to say hi on the site or in the official discord!)
487 notes
·
View notes
Why you shouldn't use @here or @everyone on Discord
If you're like me, the first thing you do when joining a discord server is mute the server.
Then you have a look around, see that @everyone is used a lot, so you suppress @everyone and @here
Because the last thing you want is to continually get pinged from a busy server, and by bots that use either of those server-wide mentions.
Now, this can be a problem. Discord servers are my primary way of getting notified when a streamer goes live, but if they use @everyone for the notification I'll often go without.
So what do @everyone and @here do?
@here is the nicer of the two; It will only send a notification to active users. So even people that are online but have the idle status won't get the ping.
@everyone is much noisier. Everyone (surprise, surprise) gets notified. It doesn't matter if your offline, or idle. That notification also persists until you log in and clear it.
The alternative? Opt-in roles.
You've probably seen something like this in a few discord servers.
This allows people to choose to get notifications for the things they care about, rather than being caught in the shotgun blast of @everyone.
For the above screenshot I'm using YAGPDB as the actual bot and Discohook to format the message.
There's a lot of tutorials on how to set up role menus like this, even official documentation from bot makers.
So go forth and create custom roles. Save people from unnecessary notifications.
0 notes
Question of the Day - A custom YAGPDB command
This is a fun little command I set up for my discord. It uses a scheduled YAGPDB custom command to ask a 'question of the day' from a list you can set up.
Here's what it looks like;
It's a great way for your community to get to know each other. You can ask serious to silly questions. I would recommend keeping a positive sentiment at all times with the questions.
So how do you set this up? Glad you asked!
I'm going to assume you already have YAGPDB set up in your discord server. So login to the website and head over to 'Custom Commands' for the discord server you want to add this to.
I created a command group for the qotd commands, because you're going to set up four of them. This isn't necessary, I'm just very tidy (and it helps have more granular permissions from other custom commands you might have).
Name the group, set the channel where you will manage the questions in the database (add, list, delete), and set which roles can use interact with these commands (you'll want your mod roles).
Now, let's create the custom command for adding a question to the database;
Set the trigger type to "command", set the trigger to whatever you feel is appropriate, set the name so you can find it again if you need to edit it, and make sure it's enabled.
And now the fun-scary part. Depends if you're familiar with code or not.
{{$args := parseArgs 1 "Incorrect syntax. Use: -qotd-add <question:string>" (carg "string" "question")}}
{{$dbKey := (print "qotd_" currentTime.Unix )}}
{{$Uuid := <add your user id here>}}
{{dbSet $Uuid $dbKey ($args.Get 0)}}
Saved new question; {{$args.Get 0}} with key {{$dbKey}}
To give a quick rundown of what this does;
Line 1 parses the input, and tells the user invoking it if they've done it incorrectly.
Line 2, 3, and 4 formats a string so the key for the entry in the database is easily identifiable, and stores your userId, before putting the actual question in the database as keyed to your user.
Line 5 sends a messages back to the user confirming that the question was saved.
This is what it looks like when you add a question;
So now let me breeze through the delete and list commands (set both of these up as separate custom commands).
Listing questions (and getting a count of how many are left). This command does hit YAGPDB database rate limits, so I recommend only getting maximum 15 questions at a time;
{{$args := parseArgs 2 "Incorrect syntax. Use: `-qotd-list <limit:int> <offset:int>`" (carg "int" "limit") (carg "int" "offset")}}
{{$Uuid := <add your user id here>}}
{{$questions := dbGetPattern $Uuid "qotd_%" ($args.Get 0) ($args.Get 1)}}
There are {{dbCount (sdict "userID" $Uuid "pattern" "qotd_%")}} stored questions.
{{- range $questions}}
`{{.Key}}`: "{{.Value}}" created {{humanizeTimeSinceDays .CreatedAt}} ago
{{end -}}
And deleting a question;
{{$args := parseArgs 1 "Incorrect syntax. Use: `-qotd-del <databaseId:string>`" (carg "string" "databaseId")}}
{{$Uuid:= <add your user id here>}}
{{dbDel $Uuid($args.Get 0)}}
Deleted entry: `{{$args.Get 0}}`
Now, how do you get it to ask a question? There's a few steps. Let's start with code (also in new custom command).
{{$Uuid := <add your user id here>}}
{{$question := dbGetPattern $Uuid "qotd_%" 1 0}}
{{range $question}}
{{$embed := cembed
"title""Question of the day"
"description" (print .Value"\n\nAnswer in the :thread:")
"color" 1388407
}}
{{sendMessage nil $embed}}
{{dbDel $Uuid .Key}}
{{- else}}
No question of the day found :scream: Someone tell the mods!
{{end -}}
{{$questionCount := dbCount (sdict "userID" $Uuid "pattern" "qotd_%")}}
{{if lt $questionCount 5}}
{{sendMessageNoEscape <add your management channel id here> "<@&add your mod role id here> There are less than 5 messages in the database. More should probably be added!"}}
{{end}}
There's a few things going on here. Simply put;
Get the next question from the database
Ask it in the nominated channel (more on that in a bit)
Delete the question that was just asked from the database
If there's no question, let everyone know by sending a funny message
Check how many questions are left in the database
If there's less than 5 questions, send a message to the management channel nominated and ping the mods
Now we're almost there. How do we set this up to run on a schedule? Thankfully you can do it in the control panel interface for YAGPDB.
Change the trigger type to "Hourly interval", set the days and hours you want the question to be asked, and select the channel you want the question to be asked in.
I've set it up so questions are asked every Monday, Wednesday, and Friday at 8am, but you can set whatever schedule you like.
Phew.
Be aware that the scheduling works on an exclusion list, and the timezone is UTC (or GMT+0 if that makes more sense). You have to do a bit of finagling to check that you've got the schedule right.
I hope this overview was useful.
A few resources I used to set this up if you want to do your own reading;
YAGPDB template reference
YAGPDB custom command database
0 notes