What makers do you use?

● ARCHIVED · READ-ONLY
Started by The Mighty Palm 20 posts View original ↗
  1. As a content creator, I feel like I wanna help out as many people as possible. So I'm doing this little poll for reference.

    Answer all the makers you use. You can do more than one vote if you have multiple.
    Talk about your favorite, why you prefer it over the others. What do you like about it? What do you wish was different?
    And hopefully more content creators will see this too and think "I didn't know x had an audience, maybe I'll make something for that"

    So if you wanna see more stuff for your engine of choice, make like Tom Hanks and cast away.
  2. There is IG Maker as well; although its not very popular.

    I voted for MV and Ace. I've used Ace the most and while I feel like generally I'm moving past it and going to MV now more full time I wouldn't ever discredit the idea I'd never use it again.

    To be honest though, I have several of the other makers that I've yet to touch; 2k3, XP, IG Maker and I can't recall at the moment if I have vx or not; I know off the top of my head I don't have 2k though and I don't have Visual novel maker, although its one I'm interested in. Out of those admittedly I'm curious to experiment with 2k3 a bit for fun sometime and feel like I should get some use out of IG maker and at least make something with it considering I bought it during a sale with the intention of using it.
  3. Since IG Maker has no support, and is essentially discontinued, I'm not including it.
  4. Actually, there are already a few topics with the same question...
  5. Awwh, poor IG Maker. :( Does it still have a sub-forum on here? I've used most of them at some point, but I mostly use MV now.
  6. Ace and MV. Although I have a slight preference for MV. And it has been some time since I've used any engines that use Ruby over Javascript.
  7. I talked about my preference in other thread, however as a fellow content creator, I've seen people asking more for MV which is kinda discouraging to create something for VXAce. So I thought it a lot for myself if I do want to create a content for people, or just to play around with myself, however I choose the latter. Talk about my need, I don't need MV. The concept I'm making can be done in VXA, and I've already build the engine for myself pretty well. Building that in MV? nah...
  8. XP still. Though I have some smaller side projects in MV as well.

    Btw Palm, it's from a couple of years ago, but maybe these polls shed some light as well: which RTP and which style. Even though it's from two/three year ago, I don't think that much has changed.
  9. XP, VX (albeit not really anymore, I just got it due to some previous license needs), VX Ace, and MV.

    Mostly I use Ace
  10. VX, VX Ace and MV
    95% of the time I use VX because my main project is being made with it. The other versions were used for several occasions like last year's IGMC.

    Hard to tell which one is my favorite, though.
  11. I voted VXAce, and 2k/3. I mostly use VXAce and occasionally work with MV but I've got a real soft spot for 2k/3, especially 2k since it was the first engine I worked with and I still find that it does a phenomenal job of forcing you to be creative with how you implement custom features.
  12. Once again, this is game development related, so moving to General Discussion.
  13. I use MV almost exclusively. It was the first Maker I picked up (going off the probably-flawed reasoning of "It's the most recent one; surely it'll be the best!"), and it's what I'm used to now.

    I've thought about doing something with VX Ace beyond just using its default database as a reference, as it's been around for longer, still has quite a bit of support, and might work better with less powerful machines/certain graphics cards (and also because I like its RTP better than MV's) but ultimately I don't want to give up a convenient plugin manager and a built-in sideview system. I'd also like to take a crack at making something in 2003 at some point; despite the complete lack of scripting, the default ATB and a lot of event commands/general things that just aren't in MV for some reason (like the ability to have an enemy attack set a switch without the need of a comment event) are big draws.
  14. richter_h said:
    VX, VX Ace and MV

    Haha, we voted for the same thing!

    Well I voted those three because they're the ones I've enjoyed using the most. :)
  15. I started using 2k, but now Im using 2k3. Maybe in future I will test Xp or MV.
  16. I think majority of rpg maker users use MV. I think second is rpg maker vx ace. The main reasons why people prefer MV are recently rpg maker officials make continuous update it, sometimes Stream has a discount for Rpg maker MV and other RPG makers too, and for some reason, people like something that say new on it.
    I think you should make your art for MV because of people just resize into smaller without losing the resolutions.

    You can see my bias mile away because I use MV always the time and the users in the future probably pick first.

    Thank you for your hard work, genousity, and considerate which shares some of your artworks with this community.
  17. @Kupotepo You are incorrect to think that one can resize into smaller without problems.
    I would also hesitate to say that it is a clear majority using MV. True, there is a lot more activity in the MV forum, but that's in part because there are a lot of new MV users. Maybe experienced Ace users don't need to post so frequently.
    I think in surveys like this, it is better to stick to answering the question i.e. what are you using, rather than trying to second guess everyone else.
  18. @Kes, could you explain more in details about what are problems with resize into smaller size? That would educate and helpful for me.
    Sorry, speculating or gussing on the survey.
  19. Same, I don't get resizing into smaller size would be problem. The problem is the opposite if you want to resize it into a bigger size. People tend to make a HD asset then resize into their appropriate media than the opposite.
  20. To discuss in detail the problems of resizing down would be to derail this thread, so not appropriate here. But in brief, you would have to rescale by 66.66666% - pixel details cannot be carried over in a 3:2 ratio, you'd get a cleaner image if it was 2:1, but then it would be the wrong size. Example in the spoiler, using a sprite by hiddenone. On the left is the original 48x48 sprite, on the right, converted to 32x32. I would not accept that quality in my games.
    Spoiler
    MV to Ace.png