I play a LOT of EotE/AoR/F&D. 3 years, 2 sessions a month.

But I also really enjoy WFRP3e, for a different style of game.

I sure would love to have an all-in-one digital resource like OggDude's suite of tools, but for Warhammer.

How pie-in-the-sky is that dream? Is this something I could do as hacks to OggDude's system or as custom data? Or would this require a dedicated programmer? (I am a dangerously inexperienced programmer.) How many hours are we talking here? Dozens, or hundreds?

Thanks for your thoughts, FFG Hivemind.

53 minutes ago, BrickSteelhead said:

I play a LOT of EotE/AoR/F&D. 3 years, 2 sessions a month.

But I also really enjoy WFRP3e, for a different style of game.

I sure would love to have an all-in-one digital resource like OggDude's suite of tools, but for Warhammer.

How pie-in-the-sky is that dream? Is this something I could do as hacks to OggDude's system or as custom data? Or would this require a dedicated programmer? (I am a dangerously inexperienced programmer.) How many hours are we talking here? Dozens, or hundreds?

Thanks for your thoughts, FFG Hivemind.

Oggy isn't handing out source code. And you're probably talking thousands of hours. Everyone is a novice programmer initially and the only way to get good is by programming something complex.

Keep in mind that this is coming someone who's strongest programming language is c÷÷ (so you know how not biased this statement is), you want to program this in Java or MAYBE python, but probably java. It's really important to have a good AUTOMATED test suite, and in Java every class can have it's own main function which is great for unit testing. I'm not to familiar with jenkins or junit, but you want to be using them (i use cmake/ctest for c++ and have a guy at work I rely on for build/test support infrastructure). The first code you write is going to be crap/don't be afraid of large reactors to improve your architecture/maintainability (I've been programming since 1994 and I usually refactor libraries with O(5000) lines multiple times, most reactors reduce the total number of lines of codes, although you may be refactoring to support the addition of new functionality that you would have to "hack" in). Your test suite there is to protect against reintroducing bugs. You should be afraid of "hacking" stuff in though, that makes maintenance a lot harder later on. If you go with java, you'll likely want to use eclipse as your development environment and JavaFx as your gui toolkit/framework. Oh and you'll probably be better served using JSON for data files instead of xml but maybe not because JavaFx has some fxml stuff that plays really nice with xml and you might choose to learn xml instead of xml and JSON, but JSON is generally considered a more logically structured way to store data.