![]() |
Junior Member
Join Date: Sep 2014
Posts: 17
|
Quote:
|
|
![]() |
![]() |
Junior Member
Join Date: Apr 2013
Location: Mena, Arkansas
Posts: 26
|
Quote:
|
|
![]() |
![]() |
Senior Member
Join Date: Sep 2017
Posts: 572
|
Maybe? I’d give it a shot. Make a backup copy of the file and try it.
Found an issue with or have a suggestion for the 5e Community Pack? Please post it here at our GitHub. Feel free to stop by the Lone Wolf Development Subreddit, for discussion of any and all LWD products and community efforts! |
![]() |
![]() |
Senior Member
Join Date: Sep 2017
Posts: 572
|
Also items, charms, and monsters for Candlekeep are about 30% completed. Unless anyone has objections, I might go for a smaller release for 3.2, with Candlekeep, Waterdeep, and just a few other little things.
Found an issue with or have a suggestion for the 5e Community Pack? Please post it here at our GitHub. Feel free to stop by the Lone Wolf Development Subreddit, for discussion of any and all LWD products and community efforts! |
![]() |
![]() |
Senior Member
Join Date: May 2016
Posts: 608
|
Quote:
COM_5ePack_Private_MH5e - All.user COM_5ePack_5EFeats - Feats.user The actual error is not with the source in the loadmods, it's with parent sources that don't exist - Source '5CMHo5E' - Reference to non-existent parent source 'pKoboPress' Source '5e5EFeats' - Reference to non-existent parent source 'pFTPK' Since that seems to indicate Kobold Press and TPK Games sources, I'm going to guess that maybe Lonewolf changed the source ids that the file refers to in one of their updates for paid material. I would suggest just commenting the lines out in the community file. |
|
![]() |
![]() |
Senior Member
Join Date: Sep 2017
Posts: 572
|
Dumb question but...how do we comment them out? I know how to do that in the eval script code but not the base file code.
Found an issue with or have a suggestion for the 5e Community Pack? Please post it here at our GitHub. Feel free to stop by the Lone Wolf Development Subreddit, for discussion of any and all LWD products and community efforts! |
![]() |
![]() |
Senior Member
Join Date: May 2016
Posts: 608
|
Same way, start a line with
<!-- move down and end the comment with a --> You have to edit the file in a text editor rather than through the normal editor. If you're interested in old versions you can find the old releases by looking to the right of the code tab on github. There should be a Releases section that has the current version listed and then a number of releases below. If you click on the number of releases you get taken to a screen with the historical releases - after each is an Asset dropdown where you can download an old release version. In the notes for version 1.8 on Feb 12, 2017 you can see the following: Quote:
|
|
![]() |
![]() |
Junior Member
Join Date: Sep 2014
Posts: 17
|
I've been submitting issues on the Github and I'm starting to feel bad about adding to the workload. How difficult would it be for me to contribute fixes to description text on things? I feel like this is something I should be capable of doing, and I'd rather help out and fix it myself than keep requesting fixes. I also wouldn't mind helping out with the rewrites for new content.
|
![]() |
![]() |
Senior Member
Join Date: Sep 2017
Posts: 572
|
Quote:
Found an issue with or have a suggestion for the 5e Community Pack? Please post it here at our GitHub. Feel free to stop by the Lone Wolf Development Subreddit, for discussion of any and all LWD products and community efforts! |
|
![]() |
![]() |
Junior Member
Join Date: Sep 2014
Posts: 17
|
Okay, I can do everything in that guide until the last step without the permissions, someone else just has to merge my pull requests. This is enough to allow me to make basic changes to description text and fix typos and such. It's not much but at least I can handle the small stuff without creating issues for other people to work on.
|
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|