THEOALLEN'S PROFILE

1. Main Theme (The Elder Scroll, from III to V, all are good)
2. Main Theme (Fallout 4, specifically. The prior game main theme sucks even though they're sharing the same melody identity)
3. Arctic Battle 3 (Starbound)
4. Map 3-4 Boss Battle (Azur Lane)
5. Silent Flower (Space Ranger 2)
6. Enough is enough (Fallout 4)
7. Metal Gleamed in The Twilight (Child of Light)
8. Yggdrasil Theme (Granblue Fantasy)
9. Go Down (Unreal Tournament 1999) - Redux version (UT 2004) - UT3 Version (Technically they're all the same song, different remix)
10. Battle (Battle for Wesnoth) - Yes, the filename literally named as "Battle.ogg"

Theodoric was taken from Theodoric the Goth from Age of Empire 2. Because "Theo" also sounds like my irl name. I took this name as my internet name from 2009 to 2011. However, in mid-2010 I was on a dilemma whether to use Theodoric or TheoAllen. The latter resembles my name more than the former.

I created this account in RMN solely just to participate music challenge back in 2011, and I hadn't made up my mind yet to choose my internet name, so I went by this name. In 2013, I pretty much fixed my internet name as TheoAllen (that I wish I also could change it here).

My twitter handler is theolized. Simply because TheoAllen is a common name that also commonly taken. Theolized is taken from my friends who kept telling me that my style of art is distinguishable that people could easily tell if it's my art (both music and pictures). To put it simply, it means "My way of doing stuff". My battle system script I named after this name because "It's my way of doing battle system".

Depends on the mood, usually I find mapping is quite chore when I want to test my game, and I had to map it before it's test-able. The product of the map usually just random, un-adjusted, and the like. If however, I find myself want to map, it will be better.

My fave part are balancing, setting skills, and play with the attack animation. My games are revolves around it, so it usually the first one that I did in my game.

One thing to note as well, RGSS3 scripts are dying. People stop making a new script, so new plugin stuff mostly for MV. Most of nowdays scripter aren't interested to make new RGSS3 script. Or at least, as far as I know. However, that doesn't deny the fact that there are already plenty of RGSS3 scripts that available and already enough to make a lot of stuff.

Majority of VXAce user afaik are veterans and know what they are doing. They know how to deal with this fact, and maybe even create their own stuff for themselves. A new user (that maybe also don't know how to deal with the back-end of the script) should look at MV for better support.

Instead of pros and cons, it will be better to tell the difference between them since pros and cons are depends on each individual.

1. First, and the first thing I noticed when tried MV is. It doesn't play MIDI. It understandable on the design perspective since MV value is for multi platform. Whether it's a pros or cons is up to you. But for me, it was the whole reason I don't use MV.

2. MV does not have built-in script editor. If you're a scripter, and you want to use your fave IDE or text editor, you can. Unlike VXAce that you're bound to built-in script editor. If you prefer built-in script editor, you don't like MV.

3. Plugin control has more friendly config that you can easily turn on / off make it easier to control. And (maybe) a config that lead to less user config error, unlike VXAce which sometimes require the script user to have a little knowledge on scripting.

4. RTP, the new project you created in MV imports all(?) the resources in your project, effectively adds almost 400mb by creating a project alone. VXAce in other hand, referenced the RTP to their respective folder. Creating multiple project is much space friendly than MV.

5. Bigger tileset. MV use 48px tiles while Ace use 32px. Whether you like or not is entirely up to you. There had been a plugin that allow you to switch to 32px tiles, but afaik, it's really not convenient.

6. MV natively support bigger screen by default. VXAce can only support 640x480 before you started to use third party tool like resolution breaker script or RGD.

7. The selling point of MV itself, a multiple port. Cmiiw, the exe(?) of MV is effectively a browser, which mean it supposed to be able to run in other platform well. If you are aiming for multiple port, you should go with MV instead of sticking with Ace and try to get a workaround with it.

8. A dark theme in MV editor for people who prefer it.

9. Built-in sideview battle system and a better character generator that doesn't exist in VXAce. Granted, VXAce also has generator, but do people already use that?

10. Also another selling point of MV is that the developer still care about it and keep updating it. You can even suggest the improvement of it. While VXAce, you're stuck with this current version. No UI update, no QoL update whatsoever.

EDIT 2:
11. It also claimed that MV also use GPU advantage unlike VXAce that only use CPU that is supposed to make it run faster/smoother, yet in fact many reported that MV runs horrible compared to VXAce, so take it with a grain of salt.

There might be more things I missed, but idk.
-------------------
My personal preference?

I don't need all the additional features offered by MV. All they did was to remove something I need and introduce something I don't need. Including removing MIDI player and built-in script editor. I don't need multiple port so I have no reason to jump to MV.

Besides I already settled all the things I need for my game. I know how to script, and already have custom battle system in my hand. I don't want to redo all the things myself. Including to learn js and deal with external text editor.

I think multiple port itself is enough as a reason to jump over to MV though.
-------------------

EDIT: As for the question whether you want/need to buy it though, I'd say buy it anyway. But wait for sales. Even if you don't use it, having MV itself is already worth, just in case in future or so. Besides the new RTP resources aren't that bad