From b436e19bbbe01536707320f5c6ca3c17f57db2f7 Mon Sep 17 00:00:00 2001
From: Matt Nadareski <mnadareski@outlook.com>
Date: Wed, 28 Sep 2022 13:04:17 -0700
Subject: [PATCH] Add important Redumper note

---
 CHANGELIST.md                      | 1 +
 MPF.Modules/Redumper/Parameters.cs | 8 ++++++++
 2 files changed, 9 insertions(+)

diff --git a/CHANGELIST.md b/CHANGELIST.md
index 70258951..2c50b2a7 100644
--- a/CHANGELIST.md
+++ b/CHANGELIST.md
@@ -125,6 +125,7 @@
 - Add Redumper command generation
 - Create Redumper extensions class
 - Minor Redumper cleanup
+- Add important Redumper note
 
 ### 2.3 (2022-02-05)
 - Start overhauling Redump information pulling, again
diff --git a/MPF.Modules/Redumper/Parameters.cs b/MPF.Modules/Redumper/Parameters.cs
index bb978158..fb7df5fe 100644
--- a/MPF.Modules/Redumper/Parameters.cs
+++ b/MPF.Modules/Redumper/Parameters.cs
@@ -10,6 +10,14 @@ namespace MPF.Modules.Redumper
     /// <summary>
     /// Represents a generic set of Redumper parameters
     /// </summary>
+    /// <remarks>
+    /// TODO: Redumper natively supports multiple, chained commands but MPF
+    /// doesn't have an easy way of dealing with that right now. Maybe have
+    /// BaseCommand be a space-deliminated list of the commands?
+    /// TODO: With chained commands, how do we tell what parameters are
+    /// actually supported? Do we go one by one and if it doesn't match
+    /// any, then it's incorrect?
+    /// </remarks>
     public class Parameters : BaseParameters
     {
         #region Generic Dumping Information