Submit a rules or table problem
Use this page when something at the table slows play, causes confusion, or needs a Chummer fix.
Request intake
Send one concrete table problem to Chummer.
Where to go next
Submit a table problem here through the guided request path. Use Help for setup or account issues.
Use this page when something at the table slows play, causes confusion, or needs a Chummer fix.
Stay here to submit a request. Open the roadmap when you want to understand where this work may go later.
Use Participate for general product feedback. Use this page for a specific table or rules pain point.
The public request form works without an account. Sign in only if you want saved requests.
If the problem is install repair, account recovery, or a normal bug report, Help is the right place.
Requests
These numbers show what people are sending in.
0 request(s) are currently in line.
0 request(s) are likely to need follow-up.
0 request(s) may be useful beyond one table.
0 request(s) look like core ruleset work.
demand detail · disabled
Workflow
Chummer keeps the request tied to this page.
Public discovery can invite a table into the intake, but it never becomes support, backlog, or rules status.
Structured intake can collect limited table pain and scope without turning raw copyrighted rules text into tool status. The limited next step contract exists, but this host has not configured the external adapter yet.
Adaptive follow-up can sharpen a demand packet, but the interview stays signal only until Hub normalizes it back into Chummer-owned packets and decisions. The limited next step contract exists, but this host has not configured the external adapter yet.
Survey ranking can validate demand shape, but it never becomes the priority decision or standard roadmap status by itself. The limited next step contract exists, but this host has not configured the external adapter yet.
Human follow-up can be scheduled when consent is explicit, but booking never becomes support-case, campaign, or product-decision status. Follow-up stays off until the reporter explicitly allows the next stage.
Review-board routing appears only after Hub has normalized a Chummer packet. shared board and next step never become rules status.
Decision stays empty until a normalized packet exists. Public signal and interviews cannot become the decision by themselves.
Closeout does not exist yet. It is only created after packet review and a Chummer decision, not from public votes or survey noise.
The next step stays clear.
The next step stays clear.
The next step stays clear.
The next step stays clear.
The next step stays clear.
The next step stays clear.
Request
Tell Chummer what is breaking trust or pace at the table.
Helpful questions
These prompts sharpen the need without becoming decisions by themselves.
Possible outcomes
Requests stay understandable before anything changes.
The request stays clear before anything changes.
Chummer uses saved outcomes here. Raw notes and vendor summaries stay out of the public result.
Chummer uses saved outcomes here. Raw notes and vendor summaries stay out of the public result.
Chummer uses saved outcomes here. Raw notes and vendor summaries stay out of the public result.
Saved requests
Sign in if you want saved requests beyond this page.
No saved requests are visible yet.