Replies: 5 comments 6 replies
-
|
With the recent PR, #117, it has gotten slightly easier however it is still not trivial. I think a stronger separation between Pixel Agent code and the Pixel Agent asset would be more beneficial. Aseprite and atlas export is a good way to maintain a stable interface. But this needs more exploration how this should be done exactly. |
Beta Was this translation helpful? Give feedback.
-
|
@pablodelucca https://github.com/NNTin/towncord/tree/main/packages Ignore the project itself. It was born recently and it is still scaffolding. Maybe it'll die like the many others I have 😆 |
Beta Was this translation helpful? Give feedback.
-
|
Hey @itsManeka! Yes, absolutely, sprite contributions are very welcome! If you just want to focus on the art side, just draw your sprites on a tileset, send them over and I'd be happy to include them for you! Proper documentation is on the way, but if you're interested to start working now and importing them yourself, here's a quick rundown of how each asset type works: CharactersEach character is a single PNG spritesheet (112x96px): 7 frames across (16x32px each) and 3 rows down.
You can look at the existing ones in the Characters folder. Here's an example character. These are based on the amazing work by JIK-A-4, Metro City. To add a new character, just follow the same layout and add it to the folder. Floor TilesFloor patterns are simple 16x16 grayscale PNGs in Wall TilesWalls are a single PNG (64x128, 4x4 grid of 16x32 pieces) that uses a 4-bit auto-tile bitmask system. Located at FurnitureThis is where it gets a bit more involved. Each furniture item lives in its own folder under
The manifest includes things like id, name, category, dimensions, footprint size, and flags like {
"id": "BIN",
"name": "Bin",
"category": "misc",
"type": "asset",
"canPlaceOnWalls": false,
"canPlaceOnSurfaces": false,
"backgroundTiles": 0,
"width": 16,
"height": 16,
"footprintW": 1,
"footprintH": 1
}Asset ManagerIf you create a tileset (a single PNG with all your furniture/items laid out), you can import them using the asset-manager which is a browser-based tool that gives an UI to guide the import. Looking forward to seeing what you come up with! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @NNTin indeed the process is still not as straightforward as I'd like it to be. I built the Asset Manager to make it a bit easier, but at the moment its just a monster HTML app with questionable UX instead of a serious app. I'm not sure if Aseprite will allow for exporting with the required structure that Pixel Agents needs to understand how to work with the asset. If you'd like to contribute on transforming the asset-manager into a proper React app and improve its UX, that would be very much appreciated! We also saw your PR on the browser preview, we're evaluating how best to integrate it, but it's awesome, thanks for your work! |
Beta Was this translation helpful? Give feedback.
-
|
The Asset Manager code is so interesting. I will take a look. I can't promise a workable result but I learned from it a bit and it makes me re-evaluate my approach. Very cool! |
Beta Was this translation helpful? Give feedback.





Uh oh!
There was an error while loading. Please reload this page.
-
Can I contribute by drawing sprites?
If so, what is the best way to contribute?
Beta Was this translation helpful? Give feedback.
All reactions