However, I differ on one point: even if I don't use pixel movement (for compatibility issues, as most of them get rid of mouse movements), a Collision Map Plugin for MV would be a great asset for many dev here who work with parallax mapping + diagonals. I didn't want to ask for something related to one specific pixel movement plugin, it wouldn't have been realistic to ask for someone to code a plugin entirely linked to GALV/Altimist/SAN or other pixel movement plugin. Well I understood that collision maps are linked to movement data, which is precisely why in this post I made it an open suggestion: for having collision maps for random 48*48 tiles. I use VictorEngine's plugins for diagonals/8frames and so on, but the requested map collision plugin would be purposely very light, just drawing the collision image and not depending on a pixel movement setup - as there are many. png file to put in a folder in img: maybe a new folder with a name like "collision", or even the preexisting "parallax" folder. It would be a collision map to insert while parallax mapping. Colored pixels on the collision map would be unpassable, and transparent ones would be passable. The idea would be to have just one plugin whose only purpose would be to draw a collision map on each map, maybe with a map notetag. You can find it here: Īnother one by HIME exists, but is not an MV plugin: Unfortunately it needs QMovement, which needs QPlus, and because of a long list of incompatibility reasons I can't use QMovement. The only one I could find for MV is the QCollisionMap. Out of idea, I'm asking here if any brave soul would be able and willing to code a Collision Map plugin for MV.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |