Both, I think. A lot of old things have changed and a lot of new things have been added (three races and a lot of mages is an impressive addition, and this is not all of it).

You can freely play Renaissance Mod with Warlock 2 right out of the gate. It does add a lot of new content, but it also balances a lot of imbalanced content in the base game and it fixes some minor bugs, too. And the AI is far more competent with the mod (so use a lower difficult setting to start).

I think you're likely to have the best game play experience beginning your foray into the world of Ardania with Renaissance Mod running, regardless of which game mode you play.

Good luck!

What about the issue? The array error? I use to love that game but this bug frustrated me. I couldnt enjoy this masterpiece.... They havent even fix it....what a shame...

Originally posted by thanogianno:

What about the issue? The array error? I use to love that game but this bug frustrated me. I couldnt enjoy this masterpiece.... They havent even fix it....what a shame...

There are a few stubborn bugs that persist and that I couldn't fix in the mod. A couple of them are array errors. There are two that can disrupt a game, and both are very rare:

1. The infamous perk bug. This crash happens when a player (human or AI) gets a new unit without any perks late in a game where there are more than 20 building perks available to that unit's class (like mage, fighter, cleric, etc.). There is a workaround -- you can destroy perk buildings as you use the perks up.

Again, this only effects late game play. I can tell you that I have only seen this bug trigger with recent versions of Renaissance Mod beyond 300 turns, and even then only once in a blue moon. If you keep tabs on what perk buildings you have for the most common classes -- mages, biters and fighters -- and destroy the ones you no longer need, you can avoid this bug. It's a bit of a pain, but it works.

And again, you're unlikely to see this bug show up at all in shorter games (< 250 turns).

2. Corrupted terrain. Very rarely the game world is generated with a few corrupted terrain tiles. Usually terrain corruption occurs in groups of 2-3 tiles. You won't even know they're corrupted until you (or an AI) tries to terraform them. Upon terraforming a corrupted tile, the game will crash.

If it's you doing the terraforming, you can continue your game by simply opting not to terraform the tile(s). But if it's an AI, your best bet is to go back a couple turns to an autosave, do your turn differently and hope the AI makes different choices. If they keep trying to terraform the bad terrain, your game will keep crashing. So this bug, when applied to an AI, can prove to be game-breaking and unavoidable.

Luckily, I've seen this bug happen only in perhaps 1 out of every 20 or 30 games, and half of those are salvageable.

Note that when you place a city in Renaissance Mod, depending on the race, your city placement may attempt to terraform the center tile. So city placement can also trigger this bug. If your game crashes as you build a new city, corrupted terrain is likely the culprit and you could instead place your city on a neighboring tile and usually be ok.

But of course it is not your fault. i am not accuse you. The opposite. I love this mod and i use to play it like a maniac. If it wasnt this array error i could play this game for the rest of my life....so much i love it,...And actually i dont think ths is mod's problem.....this is developers problem.....The company should fix this not you..

Its a "Free DLC" you should kickstart with it.