-
Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.
If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.
- The Lone Wolf Development Team
Warhammer 40,000 RPG Expansion
- Thread starter RavenX
- Start date
The documentation is incomplete. And that's not going to change anytime soon, sadly. I wish I could give you the code I have worked on but it is not licensed and I don't share unfinished source code. Knowing how GW is about their products, I am not likely to release this code without a license or GW releasing an OGL for their products (which as of yet, has not happened).
The best advice I can give you is to make a new game system, name it, and put it in a folder of your naming choice and then get starting whipping it up from scratch. I'd also advise you not to share what you do with others as GW is one of the more troublesome companies when it comes to their IPs. What you do for "Personal Use" is one thing, and you can get away with a lot under the Fair Use policies of copyrighted material, but if you do share your files, you may be crossing a line into what GW considers piracy. So be careful.
Last edited:
Thank you for the reply RavenX.
Indeed, licensing can be a big cockblock for personal/community content, especially if the company is shitty at managing its IP.
Still, there should be OK to have a skeleton file or something for 40k ruleset that does not contain data. After all Fantasy Grounds and Roll20.net have those community created resources for years.
I will keep playing with this stuff over the next weeks, but for now this endeavor with partial and old documentation and lack of collaboration with anyone looks more and more as second job.
Indeed, licensing can be a big cockblock for personal/community content, especially if the company is shitty at managing its IP.
Still, there should be OK to have a skeleton file or something for 40k ruleset that does not contain data. After all Fantasy Grounds and Roll20.net have those community created resources for years.
I will keep playing with this stuff over the next weeks, but for now this endeavor with partial and old documentation and lack of collaboration with anyone looks more and more as second job.
I added the data as I went along in coding. And I don't like giving out unfinished code projects to people. I have not worked on this one in particular in a few years now. I know an empty structure file "might" be ok, but knowing GW I'm not willing to take that risk on sharing. Companies like Onyx Path usually don't give a damn, but GW has sued people for less and I am not willing to be added to that list over a code project I intended for my personal use. When I created that file I had no intention of sharing it and I am not planning on doing so. Sorry.
I understand you completely, no problem. 
I would have done the same if I had copyrighted data in my files.
The poll and the thread led me to believe there is possibility to collaborate or to catch up quickly instead of (struggling to) re-invent the wheel, but it is a minor setback. I think uncovering how this product works is the main challenge, not data entry or setting up a skeleton afterwards.
I would have done the same if I had copyrighted data in my files. The poll and the thread led me to believe there is possibility to collaborate or to catch up quickly instead of (struggling to) re-invent the wheel, but it is a minor setback. I think uncovering how this product works is the main challenge, not data entry or setting up a skeleton afterwards.
Last edited:
I understand you completely, no problem.
The poll and the thread led me to believe there is possibility to collaborate or to catch up quickly instead of (struggling to) re-invent the wheel, but it is a minor setback. I think uncovering how this product works is the main challenge, not data entry or setting up a skeleton afterwards.
Unfortunately, no. I originally planned on expanding it when I thought it was almost done. When GW ended the product line I had no motivation to finish it. I chose it because it looked like an easy to accomplish system, but that advances system proved very complicated to figure out. This one is not likely to ever see the light of day from me. Its a dead project as of now. Not to mention hand typing all the data from the books really was not enjoyable.