In order to tell you if your hardware is working properly, we need to know what its purpose is. Also tell us if you are worried or want to improve or fix something.
When you share your homebrew, tell us:
- What does it have to accomplish, or what are your goals?
- If it is an object or a class, what level of power you will achieve, if such a concept applies to your game.
- If you are sharing a monster, challenge or obstacle, indicate who is supposed to be challenged by this challenge, which could mean briefing us briefly about the player's characters if you are a GM. (Do not hesitate to be specific to your situation.)
If you want to include comments, but still want to review your material, then post a new follow-up question with the updates. Please wait a few days first so you can get multiple sources of feedback on this version and have time to think about it. Follow-ups should be substantial.
To post a good follow-up:
- Say What question you follow. Link to this one.
- Say what changes have been made since the last version.
- Always make sure it's an independent question specifying what you want and why you still want a review.
As a rule of thumb, do not revise your question with the answers back, unless it is simply to correct a typo or clarify things that already exist in your homebrew. This includes adding these revisions to your message. Instead, request a follow-up later.
The problem here is that revising your question makes the answers obsolete, which requires cleaning and creating damage. We would prefer to keep the advice present for future visitors.
If possible, test your theoretical material yourself to see how it works in practice. For example, if you are preparing a D & D monster, you can start a short battle using your player characters to see how they could get away with it. This can give you things to do immediately before you ask us the question, but it can also give you some trouble to raise when you ask us about the material.