Robin wrote:If you draw to a Framebuffer, rather than directly to screen, you can use Framebuffer:getImageData.

It worked, but somehow the resulting image is upside down. Do anyone know why is that?


Here goes the current version:

Note that you can only set the name of the folder to store your files in, not the location. So it will always be on the users directory? Btw, I really can't think of a way to save the image. Apparently there is no function to read a part of the screen into imagedata, or even to read a specific pixe...

I made the color sliders, kinda lame, but functional.

I could not create the save file system, don't know exactly how to do it or even if it's possible with love 0.7.2.

EDIT: Is it possible to save files outside the .love file? I think this will probably stop the development of this project.

Today I'll be working on color sliders to change the color of individual items and a way to save the picture as BMP, expect updates later.

If any of you are pixel artists or know any pixel artists who could help with the database, I would appreciate any contribution.

pk wrote:That is cool.

I do pixel art for a hobby, and one thing I can tell you from experience, is that even for free stuff like this, you'll want to explicitly set a guideline for licensing. You'll probably want to use one of the Creative Commons license for all the base images.

why exactly?

I am planning to create a RPG-ish game with a 3/4ths view, kinda like SNES-era RPGs, but I have one big problem: sprites. I wanna use original graphics, but I suck at pixel art. I used to play around with RPG Maker when I was around 14, 15 years old, and there was a pretty nice software to create cu...

It will be an action-rpg, I just want the movement to stay locked on the 64x64 grid

strange... it works fine here on 0.7.2/windows

anyone had the same problem?

looks like some issue with the / and \ characters... I used require("folder/file.lua") and it worked here


I changed a little bit of the code, see if it works now:

self.running represents wether the char is running or not. If its value is 1, it adds to the speed of the character, if it's 0, does nothing. self.px and self.py are the "target" x and y coordinates for my gridlocking system. The "move" function sets them, and the "update&qu...

This is the function used to define the "target" x/y coordinates (it's a gridlocked system) function actor:move(dir) if dir == "up" then self.py = self.py - constants.base*constants.scale end if dir == "down" then self.py = self.py + constants.base*constants.scale end i...