> For the complete documentation index, see [llms.txt](https://mtgmodders.gitbook.io/etg-modding-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mtgmodders.gitbook.io/etg-modding-guide/all-things-spriting/important-sprite-creation-information..md). # Important Sprite Creation Information. ## Editors: Being as a sprite is simply an image they can be created with several different image editing software. [Aseprite](https://www.aseprite.org/) and [Gimp](https://www.gimp.org/downloads/) are two common image editors that can help your spriting process. Aseprite is specifically designed for sprites while Gimp is a free open-source editor akin to photoshop. Both work fine for the processes that are required to make a sprite so pick which ever one fits your needs best. ### Spriting Things: When making sprites for an EtG mod there are some general rules that should be followed in order to get a good outcome. The first and most important thing to note when making sprites for gungeon is that the game itself generates a black border around all sprites with an auto-detection script. This means that if you have pure black near the edges of your sprite your border can look strange and bumpy. Secondly, Gungeon sprites are smaller than you may think. A good rule of thumb is to keep sprites below a 30px X 30px square. Often editing a base game sprite for practice is a good way to get a feel for how pixel art works and getting to know how shapes can be made on such a small scale. The Gungeon's sprites can be found [here](https://www.dropbox.com/s/tgkoj4xha5lkghy/DUMPsprites%28May%202019%29.zip?dl=0) or in the pinned messages in the gungeon discord server. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mtgmodders.gitbook.io/etg-modding-guide/all-things-spriting/important-sprite-creation-information..md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.