RPG MAKER VX ACE WINDOW LIGHT CODE

Have categories for 'the general rule' for what weapons and armours a character can use, and then allow you to add exceptions. Anyway, in my mind, Ace should have combined the old system with the new one. I'll admit it's only a problem for obsessive people like myself. You've got small shield, large shield, and then 'Richard's Armours', which doesn't fit as well. You add a new armour type for it, but then the naming convention gets a little messy. Another minor problem is if you want a weapon to be usable by a single character. VX-Ace's system, while saving time, has separated the class from the weapons and armour they can equip, and has summarised them into these categories. Being able to see a class beside every weapon/armor object he can wield helps visualise how that class will play at different stages in the game, and whether or not they're underpowered or overpowered. On the face of it, this seems like a good idea, but in practice, I'm not so sure. This is to replace VX's ultra-specific class weapon/armor requirements. Now lets look at the System and Terms tabs. everything has 3 letter acronyms, most of which mean absolutely nothing, unless you look them up. I fully understand the potential that Ace offers, and I think it's good that it's there, but perhaps there's just too much interface to look at at once? I look at the Damage box of the Skill editor, and I can't work out what it's doing, and why does attacking have a 'Normal attack' state, why is that necessary?Īnd lets not get started with the Features box, and that Param tab. I don't want to be spending several minutes trying to figure out and test each individual item or skill I make (and this is coming from a programmer). While the class/skill/item/weapon/state editors in Ace are more advanced and allow unparalleled control and flexibility compared to VX, they are also slightly cryptic, time-consuming and confusing to use, which for me is a turn-off.

RPG MAKER VX ACE WINDOW LIGHT CODE

VX on the other hand has rectangle-based areas for encounters, which offer little control (albeit I was able to make a quick script to control them better).Īce's code I believe is better organised and makes modding a bit easier (though I can't be sure, it certainly is the more popular). Regions have more flexibility in terms of encounters, and are more commonly used in interaction with scripts. VX on the other hand requires third-party control over tilesets if you want more than 5, which gets messy.

Ace also allows for unlimited styles of maps by giving different tileset options per map. I will start with VX-Ace's pros.īetter system for organising tilesets.

Overall I think I prefer VX over VX Ace (this'll probably make the devs sad but hey). This has probably been discussed before, but I think it's an interesting topic, and users' opinions are likely to change over the years, so without further adieu. Now I know not all of you have used both, and some who have used both may not realise just how different they are! You're all welcome to join in with whatever input you have. So, I thought I'd start a discussion on what functions/features we like about both of these RPG Maker versions.

Rpg maker vx ace window light