⚠ READ FIRST! Commission Rules, Guidelines, & Expectations
Rules
- Be mindful of this server's #rules-and-guidelines as well as the League's Code of Conduct
- Only one (1) thread per commission.
- All threads in this channel should be a commission or bounty.
- Select all of the tags that apply to your thread.
- Do not "bump" a commission thread unless it has been auto-archived (happens after 7 days of inactivity).
- Follow the commission template (click see more)
- Mark completed commissions as "closed"
- Indicate your interest in a commission in the thread before sending a PM to the person making the request.
Feel free to ask questions or discuss the rules and guidelines in this thread.
1 Reply
Commission Guidelines
:system: Systems
Systems are one of the most common commission types, but also the least common to be fulfilled. A full system can take hundreds of hours to compete. Most existing systems are passion projects written by fans of the system. It's possible to commission a system, but be prepared for it to be a significant investment of both time and money. Finding a developer who plays or wants to play the system in question usually helps.
:module: Modules
Modules are generally much simpler than systems, but they can vary pretty wildly. Some modules can be completed in just a couple of hours, while others may take dozens.
:macro: Macros
A macro is a small piece of code that can be pasted into the Foundry macro editor. A macro performs a single task, or runs through a complicated process automatically. Most macros are pretty short, and should only take a few hours to write. If a macro needs multiple options, a user interface, or very substantial code it may be better to create a module instead.
:contentmodule: Adventures & Content
Some modules don't add features and functionality, but rather add new content for GMs to use - this includes compendium packs of Actors and Items, pre-walled and lit maps, and full Adventures. These commissions may be posted here, but they generally fall outside of the scope of what most users of this server do. If you are interested in content creation or content conversion, you may find more takers in another server.
⬆️ Updates
In some cases, you may want an existing macro, module, or system updated with new features or to function in a new version of Foundry. If the original author has stopped providing updates, and the license on their code allows it, you can hire someone to pick up where they left off.
Commission Template
Thread title: (either the name of the system, a name or simple description of a module, or a short description of a macro)
Thread content:
Pricing Guides
Most developers will charge by the hour. Some will give an up-front quote, but many will not be able to estimate the total hours expected for the project, especially if the project isn't similar to something they have worked on before. Some developers here are already professionals, some are not.
Typical Hourly Rates: Expect rates in the range of $30-$80/hr. Some developers, especially experienced ones, may charge even more.
:macro: Macro: Usually less than 5 hours.
:module: Module: 10 - 50+ hours.
:system: System: Usually well over 100 hours.
Commissions Vs. Bounties
Most posts are commissions. This means you want to hire someone to do work for you, and you should expect a rate similar to the market rate for the particular service, and the exact rate will be negotiated between you and the commission taker. Some posts on the other hand, can be bounties: You are making an up-front offer of a specific amount for a very specific need. Bounties can generally be accepted by anyone who implements the desired feature - be it a brand new module, or an updated to an existing one.
What to Expect
Commissioning a Project
After you have posted your commission thread, you may receive responses from users interested in the project. Often times these will be follow up questions or advice, or someone might offer to work on it. Not every post will attract attention, simpler proposals will generally garner more interest while complex ones like full systems are a much larger challenge and therefore less appealing unless someone is already interesting in playing with that system.
We recommend that initial contact between prospective developers and clients takes place here in your thread in order to keep everyone in the loop - including others that might want to pitch in. This also helps protect you from scams or fraud, as it's easier for other users to point out suspicious behavior when discussions are public (and therefore less likely anyone will try something).
Hiring a Developer
While some small macros end up being completed quickly and with an informal agreement on payment, understand that commissioning someone to work on a project is very much like hiring for a job. The more complicated (and expensive) the job is, the more you should consider who you are working with. It is perfectly reasonable to ask for examples of prior work, a Github profile with a history of contributions or a personal website with example projects serve as a developer's "portfolio." In some cases, particularly for large systems or when intellectual property is involved, it may even make sense to request a resume. You don't have to just send money to the first person that offers to help and hope they do a good job.
Prices & Timelines
Make sure to read the pricing guide above. One of the most common issues we run into with commissions are mismatched expectations regarding cost and development time. Software development is typically more expensive than most people realize, and unless you are hiring a large team it can take quite a while. Also understand that even the best devs are rarely good at estimating how long a project will really take, there are usually a lot of unknowns that make it almost impossible to guess unless it's something they have done before.
Also consider that most developers in this community do commissions as a hobby, and still work a full time job 40 hours a week. Even a project estimated at 10 hours might take two weeks to complete because they can only dedicate an hour a day or can only work on it on weekends. It's good to communicate expectations in this regard before starting a project.
Taking a Commission
When you see a commission that you are interested in, be sure to introduce yourself in the commission thread so that the poster and other developers know you are hoping to work on it. Make sure to ask for any additional information you feel like you might need including requirements, time restraints, budget limits, etc. Also make sure you are able to fulfil the requirements of the project, if you are uncertain make sure you let the commissioner know what parts you might have trouble with and make sure they are okay with your level of experience.
Taking on Clients
Taking on a client can be much like interviewing for a job. It is often less formal, but expect to be asked for some examples of your prior work. It is also perfectly reasonable to vet clients, just as you might research a company before applying for a job, get to know who you are working for. On large projects, you may want to see examples of other projects this client has commissioned. It is also important to verify that the client has the right to any intellectual property that might be involved, and that there are no legal issues that might stand in the way of the project.
Know What You Are Worth
Software development is a skill that take a lot of learning, practice, and dedication. Don't sell yourself short, consider the pricing guidelines above and give a fair estimate. Most projects take longer than you will expect, so keep that in mind. Make sure to let the client know not only how many hours you expect the project to take, but how many hours you are able to work on it in a given time period. If you are only abele to work weekends, make sure they know!
Avoiding Scams & Fraud
Unfortunately not everyone posts in this forum in good faith. Sometimes people are inexperienced or naive, and other times people are out to take advantage of others. The League is not able to police every discussion individually, and discussions in DMs or other servers are beyond our reach. We also have very limited power in terms of dealing with individuals that violate our rules and the trust of others. We can and will issue bans if someone is found to be committing fraud via our server, but that is the extent of our real power. If you believe someone has committed fraud, do not hesitate to reach out to us, but also make sure to reach out to Discord and any other parties that might be involved.
Take a look at who you are working with. Does the developer or client have a good track record that you can see? Are they an active user on this server or the Foundry VTT server? It's pretty easy to find messages from a particular user on a server with the search box, take a look at some of their history. If they seem to be entirely new to the community, that's often not a good sign and you should be more cautious when dealing with them. Also consider how they interact with others, are they helpful? Rude? Knowledgeable? Disrespectful? Don't agree to do business with someone if they don't have a great track record.
As a Commissioner
First and foremost, try to communicate primarily in the open. Naturally this process will often lead to the exchange of private information, and that should be kept private. However much of the discussion regarding the scope, requirements, and even price estimation can be had publicly. This helps prevent people from taking advantage, and allows other users to see what to expect from the process.
Unrealistic Promises
This is a big red flag. Consider the pricing guidelines above before posting a commission. If you are given an estimate that's significantly lower than those guidelines, it might be a good idea to question the authenticity. Some developers will inevitably undervalue themselves, but they too should be looking at the guidelines above. If someone promises a very quick turn-around they had better have a long list of contributions on their Github proving that they are up to the task. A novice might charge a lot less than a pro, and that's okay if you are happy to work with someone that's still learning and needs experience. But if someone claims to be an expert but don't charge like one, it's a little suspicious.
As a Developer
Taking on a commission can be a risk, it's much harder to take back work that has been done than it is for someone to claw back a PayPal transaction. For more complex projects, make sure you trust that the client can afford to pay for the project and avoid delivering anything they can use without payment. If it's a $10k system you are building, and the client isn't a known corporation or doesn't have a successful Kickstarter campaign, you should probably be asking yourself (and them) where that money is going to come from. Some people have deep pockets, but most people spending that much do so because there is a return on investment for them. If you don't see how this person is going to make any money off of the work, they probably aren't going to have enough to pay you.
Unrealistic Promises
Keep in mind the pricing guidelines. If someone offers way more than a project is worth, they may be trying to trick you. Don't let a big number cloud your judgment.
Expectations, Scope, & Requirements
If it's not clear what the client wants, or they keep changing the requirements or increasing the scope, this is a bad sign. It might not mean it's a scam, they might just not be a good client, but in some cases people will use scope creep to get more work done without paying for it. Others might make unreasonable demands then refuse to pay on the grounds that you failed to meet their expectations. Be sure to set a firm set of requirements for a project, a clear list of items that need to be completed and the price that is to be paid for that list of items.