diff --git a/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs b/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs
index 5b9a567f..b67eb619 100644
--- a/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs
+++ b/SabreTools.Helper/Dats/Partials/DatFile.Parsers.cs
@@ -59,13 +59,6 @@ namespace SabreTools.Helper.Dats
 		/// <param name="descAsName">True if descriptions should be used as names, false otherwise (default)</param>
 		/// <param name="keepext">True if original extension should be kept, false otherwise (default)</param>
 		/// <param name="useTags">True if tags from the DAT should be used to merge the output, false otherwise (default)</param>
-		/// <remarks>
-		/// TODO: Add CSV and TSV parsing.
-		///        Can they be in the same parser? All it would technically need is the delimiter that it should be looking
-		///        for and it would be able to read them individually. Also, take into account different types of formats,
-		///        possibly by looking at the first line headings, determining what columns those correspond to, and then
-		///        keeping track of what goes to what in the map. That would allow for a VERY flexible reading of inputs.
-		/// </remarks>
 		public void Parse(
 			// Standard Dat parsing
 			string filename,
diff --git a/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs b/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs
index 21d8e0d2..687662be 100644
--- a/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs
+++ b/SabreTools.Helper/Dats/Partials/DatFile.Writers.cs
@@ -999,7 +999,6 @@ namespace SabreTools.Helper.Dats
 								RepExt = "";
 							}
 
-							// TODO: Find out why this code strips out partial paths
 							string dir = Path.GetDirectoryName(name);
 							dir = (dir.StartsWith(Path.DirectorySeparatorChar.ToString()) ? dir.Remove(0, 1) : dir);
 							name = Path.Combine(dir, Path.GetFileNameWithoutExtension(name) + RepExt);