search

sikthehedgehog / mdtools

A set of tools for developing Mega Drive homebrew
76 stars 8 forks source link

Make mdtiler not spit out multiple errors caused by the same mistake #5

Open sikthehedgehog opened 7 years ago

sikthehedgehog commented 7 years ago

Referring specifically to when it feels like doing this:

Error[paintcanvas/data/buildgfx:6]: no output file to write into
Error[paintcanvas/data/buildgfx:7]: no output file to write into
Error[paintcanvas/data/buildgfx:9]: no output file to write into
Error[paintcanvas/data/buildgfx:10]: no output file to write into
Error[paintcanvas/data/buildgfx:12]: no output file to write into
Error[paintcanvas/data/buildgfx:13]: no output file to write into
Error[paintcanvas/data/buildgfx:15]: no output file to write into
Error[paintcanvas/data/buildgfx:16]: no output file to write into
Error[paintcanvas/data/buildgfx:23]: no output file to write into
Error[paintcanvas/data/buildgfx:24]: no output file to write into
Error[paintcanvas/data/buildgfx:26]: no output file to write into
Error[paintcanvas/data/buildgfx:27]: no output file to write into
Error[paintcanvas/data/buildgfx:29]: no output file to write into
Error[paintcanvas/data/buildgfx:30]: no output file to write into
Error[paintcanvas/data/buildgfx:32]: no output file to write into
Error[paintcanvas/data/buildgfx:33]: no output file to write into
Error[paintcanvas/data/buildgfx:36]: no output file to write into
Error[paintcanvas/data/buildgfx:37]: no output file to write into
Error[paintcanvas/data/buildgfx:39]: no output file to write into
Error[paintcanvas/data/buildgfx:40]: no output file to write into
Error[paintcanvas/data/buildgfx]: unable to process batch file

Bringing it up only once should suffice.