From 8597f97991e08cb0bb96980e23c2eb00c20f405b Mon Sep 17 00:00:00 2001
From: OliM <250004@aylesburyutc.co.uk>
Date: Wed, 9 Sep 2026 15:35:47 +0100
Subject: [PATCH] Support 'toml' format in custom egg documentation

Added 'toml' to the list of supported formats for parsers.
---
 docs/eggs/creating-a-custom-egg.mdx | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/eggs/creating-a-custom-egg.mdx b/docs/eggs/creating-a-custom-egg.mdx
index 6076c583..70761e3d 100644
--- a/docs/eggs/creating-a-custom-egg.mdx
+++ b/docs/eggs/creating-a-custom-egg.mdx
@@ -90,6 +90,7 @@ In this example, we are telling Wings to read `server.properties` in `/home/cont
 - `ini`
 - `json` (supports `*` notation)
 - `xml`  (supports `*` notation)
+- `toml`
 
 Once you have defined a parser, we then define a `find` block which tells Wings what specific elements to find and replace. In this example, we have provided four separate items within the `server.properties` file that we want to find and replace to the assigned values. You can use either an exact value, or define a specific server setting from the server configuration. In this case, we're assigning the default server port to be used as the `server.port` and `query.port`. **These placeholders are case sensitive, and should have no spaces in them.**