If, after well articulated research, you can reasonably suggest a lacunae in the originating system, and the querent doesn't explicitly forbid homebrew, you can answer with a "Your system doesn't support your request, but here is some homebrew I wrote, and here's how it played out in a game I ran."

That last bit is really important, by the way.

We require answers that are justified by good subjective and objective components (if any.) Discussing your homebrew in context in your experiences shows that you've tested your homebrew. Since your answer can stand alone without the homebrew, due your research into the system showing the absence of support, or the poor implementation of support, adding a "here's how I fixed this problem" is quite good.

We're not a good community for the testing or discussion of homebrew though.

As a note, if the querent explicitly requests potential homebrew, then you're on much safer ground, especially if you can point to similar imaginings and how they worked in other games.

If, after well articulated research, you can reasonably suggest there's something missing for what's being sought in the originating system, and the querent doesn't explicitly forbid homebrew, you can answer with a "Your system doesn't support your request, but here is some homebrew I wrote, and here's how it played out in a game I ran."

That last bit is really important, by the way.

We require answers that are justified by good subjective and objective components (if any.) Discussing your homebrew in context in your experiences shows that you've tested your homebrew. Since your answer can stand alone without the homebrew, due your research into the system showing the absence of support, or the poor implementation of support, adding a "here's how I fixed this problem" is quite good.

We're not a good community for the testing or discussion of homebrew though.

As a note, if the querent explicitly requests potential homebrew, then you're on much safer ground, especially if you can point to similar imaginings and how they worked in other games.

If, after well articulated research, you can reasonably suggest a lacunae in the originating system, and the querent doesn't explicitly forbid homebrew, you can answer with a "Your system doesn't support your request, but here is some homebrew I wrote, and here's how it played out in a game I ran."

That last bit is really important, by the way.

We require answers that are justified by good subjective and objective components (if any.) Discussing your homebrew in context in your experiences shows that you've tested your homebrew. Since your answer can stand alone without the homebrew, due your research into the system showing the absence of support, or the poor implementation of support, adding a "here's how I fixed this problem" is quite good.

We're not a good community for the testing or discussion of homebrew though.

If, after well articulated research, you can reasonably suggest a lacunae in the originating system, and the querent doesn't explicitly forbid homebrew, you can answer with a "Your system doesn't support your request, but here is some homebrew I wrote, and here's how it played out in a game I ran."

That last bit is really important, by the way.

We require answers that are justified by good subjective and objective components (if any.) Discussing your homebrew in context in your experiences shows that you've tested your homebrew. Since your answer can stand alone without the homebrew, due your research into the system showing the absence of support, or the poor implementation of support, adding a "here's how I fixed this problem" is quite good.

We're not a good community for the testing or discussion of homebrew though.

As a note, if the querent explicitly requests potential homebrew, then you're on much safer ground, especially if you can point to similar imaginings and how they worked in other games.