How difficult would a fanmade modular open-source engine for MTW style campaign be?

[drone]

As an old school programmer, the campaign map, with it's turn based action, reads like an exercise in data structures. There is nothing in real-time, everything is menu-based apart from the music. AI decisions, troop movement, battle results, incomes, etc. are computed during the end-year phase. The first step would be writing file parsers to read in the data files like the startpos, unit and build prod, LUK map, etc. Then you would need the campaign start menu (chose campaign, faction, difficulty, era), fill in the province/faction data and start points. Most of the campaign game mechanics are fairly well known, so the end-turn calculator would be easy. The GUI, campaign map graphics, unit and building menus add more complexity (user input always does), but again nothing is real-time. The AI decisions for recruitment, building, troop movement, and diplomacy would be the most difficult task, which is usually why the AI stinks in most strategic video games.

The battle map, egads. I don't even want to think about that.

[Gaiseric]

You make it sound easy, although half of the stuff you just said went right over my head.

Of all the TW games I'd say that MTW AI is the most competent. I think a lot of that has to do with the style of campaign map used in MTW compared to the newer versions. Its probably easier to program the AI for the 2D map too. A 3D battle map will be very difficult to program the AI for. Hats off to CA. Up to ETW, battles were their forte. ETW however had a great strategic\campaign map. Someday someone will get the combination right, but they will have to be a computer wizz, borderline autistic, for the programming needed.

[caravel]

Personally I think any open source engine for STW/MTW should do away with the perspective plane and sprite scaling approach (the 3D appearance of the map and the scaling of the map pieces) and just go for a basic flat top down map with draggable pieces (yes something along the lines of what Garnier has developed or the paradox games). This should be fully playable without the battle map component, i.e. if the battle map is not present the option to fight the battle yourself is greyed out - autoresolve being the only option. The campaign map game need only run windowed, but apart from appearances it should function exactly like the STW/MTW campaign. The engine could still use the same MTW map textures, pieces and other graphics and sounds - so in essence kind of like a flattened MTW with no DirectDraw, running only in a window (I would put together a mock up if I had the game installed and if I wasn't at this moment at work).

The battlemap is a whole other project. That's the real "total war" and where most of the code probably is. There may be existing open source 3D engines that could be adapted to recreate it - all that would be needed would be the textures and models from MTW, which the player would need to buy. In these types of ports a lot of improvements are possible, such as 3D models on the battlefield instead of sprites.

[Gaiseric]

What would be really cool, but maybe not possible for a source edited game, would be to have a campaign map like you described above, with a similar number of large provinces like MTW has. Instead of battle taking place on that map, the game would zoom in and have each province hexed out, with appropriate terrain features. Armies will appear on the hexes of the province they are invading from and have to capture objectives, cross rivers, gain terrain advantages, and defeat enemy armies occupying the hexes. A battlemap similar to some of the SSI games that were released in the early 90's would be very cool and probably not as hard to develop as the 3d battlemap of TW games. It would be a great complement to those types of games.

I like games as you described above, but they always seem to end in a slugging match between the AI and the player. In these slugging matches the player has no control over what happens militarily, and is usually doomed to defeat if they have a smaller army. A zoomed in province map with hexes, or even something with thousands of provinces like Hearts of Iron, would give the player more tactical control. This might mean a lot more programming, but it is the direction I hope to see some of those games take.

[Vantek]

As an old school programmer, the campaign map, with it's turn based action, reads like an exercise in data structures. There is nothing in real-time, everything is menu-based apart from the music. AI decisions, troop movement, battle results, incomes, etc. are computed during the end-year phase. The first step would be writing file parsers to read in the data files like the startpos, unit and build prod, LUK map, etc. Then you would need the campaign start menu (chose campaign, faction, difficulty, era), fill in the province/faction data and start points. Most of the campaign game mechanics are fairly well known, so the end-turn calculator would be easy. The GUI, campaign map graphics, unit and building menus add more complexity (user input always does), but again nothing is real-time. The AI decisions for recruitment, building, troop movement, and diplomacy would be the most difficult task, which is usually why the AI stinks in most strategic video games.

The battle map, egads. I don't even want to think about that.

This is exactly what I feel is the case. Given that the campaign map portion of the game is honestly pretty damn easy to program, and actually really enjoyable by itself alone, without the battle map portion of the game... Isn't it strange that recreating it has never been even discussed, let alone created, considering how much amazing work MTW community has already proven to be capable of?

And once you already have the campaign map portion of the game fully recreated as an open source project... Recreating the battle map will start to look a lot less impossible. You could begin with something much more crude than the original MTW. At this point, I think the project would gain a ton of interest from fans who were perhaps fed up with certain bugs or design flaws or compatibility issues. This would attract more and more potential developers... And who knows, eventually there could be a battle map even better than the original.

Or, well. All of this would have been true if I had said it 5-8 years ago. Now it's just too late. Although as another favourite game of mine, Seven Kingdoms, reminds us, there is always hope... (cliffs: the game's source code was released to the fans >10 years after its release, and is now being worked on)

Personally I think any open source engine for STW/MTW should do away with the perspective plane and sprite scaling approach (the 3D appearance of the map and the scaling of the map pieces) and just go for a basic flat top down map with draggable pieces

I agree that it should start out with less fancy graphics with the intention of recreating the original later, once you already have something functional in place. But are you advocating a basic flat top-down map as the ultimate goal? If so, why?