FormatException when using brace symbolsError
Im getting the following after adding formatted text to my lang file:
(03:28:23) | Failed to run a 300.00 timer in 'AutoBroadcast v1.0.8' (FormatException: Input string was not in a correct format.)
at System.Text.StringBuilder.AppendFormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) [0x000ae] in <a8ed250850854b439cedc18931a314fe>:0
at System.String.FormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) [0x00023] in <a8ed250850854b439cedc18931a314fe>:0
at System.String.Format (System.String format, System.Object[] args) [0x00020] in <a8ed250850854b439cedc18931a314fe>:0
at Oxide.Plugins.AutoBroadcast.Lang (System.String key, System.String id, System.Object[] args) [0x0000e] in <5959c08b47f04dbe90dd0a615e54ffe3>:0
at Oxide.Plugins.AutoBroadcast.<Broadcast>m__0 () [0x00111] in <5959c08b47f04dbe90dd0a615e54ffe3>:0
at Oxide.Core.Libraries.Timer+TimerInstance.FireCallback () [0x00018] in <b0a93b504f034a0db8b1c3d2503c0987>:0


This is my lang file:

{
  "Addon Commands": "Can't remember an addons commands? Type /info and go to Server Addon tab!",
  "Rules": "Read the rules under the Rules tab in /info. Not knowing a rule isnt an excuse!",
  "Server Staff": "Report players without [#CC00FF]{OWNER}[/#] , [#00D0FF]{CO-OWNER}[/#] , [#FF0000]{ADMIN}[/#] or [#FF9900]{MODERATOR}[/#] that are claiming to be staff!",
  "Discord": "Join our discord over at discord link to keep up to date with the latest changes!",
  "Server Issues": "Is there an issue with the server? Have a suggestion? Join our discord @ discord link and let us know!",
  "Hackers/Rule Violation": "Report players with [#FF0000]/Report <player name> <reason> <message>[/#] if they are violating rules. You must replace < and > with quotation marks for this to work!"
}
This is the config file also:

{
"Broadcast Interval (Seconds)": 300,
"Randomize Messages (true/false)": false
}
The { and } are that you've added are causing the issue. I can add handling for that in a future version, but for now I would avoid those.