By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!I meant the --- >@everyone <--- that the webhook puts into Discord. I posted that quote as an example![]()
"Keywords":{
"Your Tribe killed "false:true,
" was killed"false:true,
" demolished a ":false,
" claimed ":false,
" unclaimed ":false,
" was added to the Tribe!":false,
" was removed from the Tribe!":false,
" was auto-decay destroyed!"false:true,
" starved to death!":true,
" was destroyed!"false:true,
" destroyed their ":false,
"Tamed a":false,
" was promoted ":false,
" was demoted ":false,
" set to Rank Group ":false,
" uploaded ":false,
" downloaded ":false,
" froze ":false,
" unfroze ":false,
" destroyed your ":false,
"Tribe name changed ":false,
"Tribe owner changed ":false,
" now online!":false,
" gone offline!":false,
" has been born."false:true,
" has been hatched."false:true
}
},
So.... In the config I need this?:
Code:"Keywords":{ "Your Tribe killed "false:true, " was killed"false:true, " demolished a ":false, " claimed ":false, " unclaimed ":false, " was added to the Tribe!":false, " was removed from the Tribe!":false, " was auto-decay destroyed!"false:true, " starved to death!":true, " was destroyed!"false:true, " destroyed their ":false, "Tamed a":false, " was promoted ":false, " was demoted ":false, " set to Rank Group ":false, " uploaded ":false, " downloaded ":false, " froze ":false, " unfroze ":false, " destroyed your ":false, "Tribe name changed ":false, "Tribe owner changed ":false, " now online!":false, " gone offline!":false, " has been born."false:true, " has been hatched."false:true } },
yeah that's what i am trying to explain to you. I want those active but not for the plugin to @everyone on discord. I just want it to silent post in the channel not mention anyone.
MySQL integration seems to work bad after server restart and tribes have to do /tlr again. Changed to sqlite and issue was resolved.
Bug Fix - MySQL support had an error preventing tribe webhooks from loading from the database on server restarts. This is the reason that resetting the webhook after a reboot would allow discord messages to flow again.
MySQL integration seems to work bad after server restart and tribes have to do /tlr again. Changed to sqlite and issue was resolved.
Yes, I was using mySQL, I will update the new version on Monday. I try not to do updates on the weekend.I'll probably switch to sqlite if there's no benefits to mySql, right?
For some reason the log on discord always uses ServerName for the name no matter what I change it to.
Change the name in the config.json that is the only place the name in the logs come from.
{
"General": {
"ServerName": "Ragnarok",
"ForceTribeMembership": true
},
"Mysql": {
"UseMysql": true,
"MysqlHost": "0.0.0.0",
"MysqlUser": "tribelogrelay",
"MysqlPass": "-----",
"MysqlDB": "tribelogrelay"
},
"Messages": {
"Sender": "Tribe Log Relay",
"ChangedWebhook": "Successfully set your tribes Discord Webhook!",
"Invalid": "<RichColor Color=\"1, 0, 0, 1\">Webhook appears to be an invalid discord webhook!</>",
"Error": "<RichColor Color=\"1, 0, 0, 1\">Webhook did not get updated, try again!</>",
"NotAllowed": "<RichColor Color=\"1, 0, 0, 1\">Only the tribe owner is allowed to use this feature!</>",
"NotFound": "<RichColor Color=\"1, 0, 0, 1\">Unable to locate your tribe entry! Contact the server admin.</>",
"Usage": "\nTribe Owners Only!\nUsage: /tlr <discord webhook>\nVisit https://bit.ly/33Jw8i5 for information about Discord Webhooks.",
"ForceTribe": "Tribe membership is required. You have been added to your own tribe."
},
"Commands": {
"CommandText": "/TLR",
"UsePermissions": true,
"PermissionName": "TLR.Add"
},
"Discord": {
"UseAdminLogging": true,
"AdminDiscordWebhook": "------",
"DiscordLinkFormat": "https://discordapp.com/api/webhooks/[^/]+/[^/]+",
"DiscordPingCooldown": 0,
"UseTribeID": true,
"TribeFormat": "{1}:{0}"
},
"Detection": {
"DetectCyroUnfreeze": true,
"DetectTribenameChange": true,
"DetectTribeOwnerChange": true,
"DetectCyrofreeze": true,
"CryoItems": "PrimalItem_WeaponEmptyCryopod_C,SoulTrap_DS_C",
"DetectTribeLogin": true,
"DetectTribeLogoff": true
},
"KeywordMatching": {
"UseKeywordMatching": true,
"Keywords": {
"Your Tribe killed ": false,
" was killed": false,
" demolished a ": false,
" claimed ": false,
" unclaimed ": false,
" was added to the Tribe!": false,
" was removed from the Tribe!": false,
" was auto-decay destroyed!": false,
" starved to death!": false,
" was destroyed!": false,
" destroyed their ": false,
"Tamed a": false,
" was promoted ": false,
" was demoted ": false,
" set to Rank Group ": false,
" uploaded ": false,
" downloaded ": false,
" froze ": false,
" unfroze ": false,
" destroyed your ": false,
"Tribe name changed ": false,
"Tribe owner changed ": false,
" now online!": false,
" gone offline!": false,
" has been born.": false,
" has been hatched.": false
}
},
"Localization": {
"TribeOwnerChanged": "Tribe owner changed from {0} to {1}",
"TribeNameChanged": "Tribe name changed to ({0})",
"UnCryo": "{0} unfroze {1}",
"Cryo": "{0} froze {1}",
"Login": "{0} is now online!",
"Logoff": "{0} has gone offline!",
"NewBaby": "'Baby {0}' has been born.",
"EggHatched": "'{0}' has been hatched."
},
"AdminKeywordMatching": {
"UseKeywordMatching": true,
"Keywords": {
"Your Tribe killed ": false,
" was killed": false,
" demolished a ": false,
" was added to the Tribe!": false,
" was removed from the Tribe!": false,
" was destroyed!": false,
" destroyed their ": false,
" destroyed your ": false,
"Tribe name changed ": false,
"Tribe owner changed ": false
}
},
"Notifications": {
"NotificationDisplayTime": 10,
"NotificationScale": 1.3
}
}
This is an edit of the default config with my values put in.ServerName is what gets put in by default if it didn't read your server name from the config. Use the default config and fill in your values.
(S-Ext) (1304270659:Aces) Day 3151, 11:35: froze Juvenile Managarmr - Lvl 235 (Managarmr)
(S-Ext) (1695372094:Satchel of Richards) Day 3151, 11:35: Cheney trapped: Managarmr Male (Lvl 235 Managarmr)
We use essential cookies to make this site work, and optional cookies to enhance your experience.