• 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

Hero Lab Community Repository for Shadowrun 5th?

I've a couple days off so I'm going to start working on this.
Got some Spike Troll Gangers, Night Hunters, and Tamanous organ leggers to post.

How does everyone feel about posting both the Hero Lab .por file and a PDF or stat block of the character?

It would make the site useful to any GM that way.
 
Cascade Ork Pirates

Cascade Ork Smuggler/Pirates.
These boy are far from their mountain homes, but their Corsair Panther can get them places where other ships would attract too much attention.
Lead by a Brawling Adept Captain, plus a Pistol Adept First Mate, a Rigger Pilot and a Shaman plus more mountain boys for muscle, anything not nailed down is fair game.



https://github.com/runnerblank/Community-Hero-Lab---Shadowrun-5th
 
Last edited:
how do i upload files?

I'm getting this from github right now:

Uploads are disabled.
File uploads require push access to this repository.
 
The usual process is to fork the original repository to your own github account, commit and push the changes there (in a new git branch), then create a pull request to let the owner of the source repository know that there is something new to merge. Effectively, you upload it to your own area, then tell the owner where to get it. With some wrapper stuff, that makes the 'tell' and 'get' a few clicks.

The alternative is to have the owner authorize you to have shared administrator access to the original repo. Normally only pre setup teams use that. The first way is more secure, allowing anyone to request a change to a repository, without giving the whole world access to mess things up.
 
mMerlin said:
The usual process is to fork the original repository to your own github account, commit and push the changes there (in a new git branch), then create a pull request to let the owner of the source repository know that there is something new to merge. Effectively, you upload it to your own area, then tell the owner where to get it. With some wrapper stuff, that makes the 'tell' and 'get' a few clicks.

The alternative is to have the owner authorize you to have shared administrator access to the original repo. Normally only pre setup teams use that. The first way is more secure, allowing anyone to request a change to a repository, without giving the whole world access to mess things up.
Click to expand...

I'd like to do it the first way.
 
adzling said:
ugh.

is there a reason to use github over something simpler like dropbox?
Click to expand...
Sure. It also automatically supports revision control and history, provides a wiki where extra usage information can be added over time, provides a place to ask questions and report problems. All for free.

Oh, it also provides a common place to go get the latest version of anything collected there. Other than the 'free', dropbox does not do any of that.

Is that enough reasons?
 
Lets see if the moderator lets me respond to you this time without censorship..

for me, not really.

These are character files not programs that need versions tracked.

In this instance imho simpler = better
 
You must log in or register to reply here.
Back
Top