**Contact Jasvel about rules, bugs and app questions** > Find out how to contact Jasvel about rules corrections, scoreboard bugs and app questions, and learn what evidence makes a report useful. Source: https://jasvel.org/contact/ [Home](https://jasvel.org/) # How can I contact Jasvel? Use the published Jasvel contact email for rules corrections, scoreboard reports and questions about the offline app. Updated 11 August 2026 · [Merey Tleugazin](https://jasvel.org/about/) ## How can I contact Jasvel? Jasvel accepts written enquiries by email. The published contact address is the correct route for questions about the app, reports about scoreboard behaviour and carefully supported corrections to the rules reference. A clear subject helps identify the purpose of your message before the full report is read. Suitable subjects include “Rules correction”, “Scoreboard bug” and “Question about the app”. Choose the subject that best describes the main point, then keep the message focused on that point. Email gives you room to provide the evidence needed for a proper review. A rules question may require a quotation from a source. A scoreboard report may require the actions that produced the displayed total. An app question may require the wording or screen that caused difficulty. Written details are more useful than a brief statement that something seems wrong. Jasvel does not provide a phone line, chat service or support portal. Send the complete report by email rather than dividing the information between different channels. One record lets the publisher assess the matter and ask for clarification if the original message leaves an essential detail unresolved. Before writing, check the [About Jasvel](https://jasvel.org/about/) page and the [Jasvel app](https://jasvel.org/jasvel-app/) information. The reference pages may already explain the term, calculation or feature that prompted your question. A quick check can also show if the matter concerns a rule, a regional convention, a display problem or a request for a product change. Keep the message relevant to Jasvel. Unrelated card-game disputes, unsupported claims about local practice and general feature requests do not provide the same basis for review as a documented correction or a reproducible fault. A useful message explains the point that needs attention without adding private information that the publisher does not need. A rules report normally needs the rule, its source and the variant concerned. A technical report normally needs the screen, the actions taken and the result shown. An app question normally needs the instruction or feature that caused uncertainty. These details allow Vast Flow, LLP, the publisher of Jasvel, to understand the matter and decide what can be checked. The contact email is intended for written correspondence. Sending a message does not promise an immediate response, a telephone call or an ongoing private discussion. Write one complete report where possible, keep supporting evidence together and allow time for review. For example, a useful first paragraph could say that a scoreboard total appears incorrect after a particular game form and card combination. A second paragraph could list the actions taken and quote the rule used to calculate the expected result. That format gives the reader a clear claim, a sequence to examine and a reason for the report. ## What should I include in a Jasvel rules correction? A useful rules correction identifies the exact claim, cites the supporting source and explains the difference in plain English. Name the page or passage concerned so the wording can be examined without guessing which rule you mean. Jass has regional variations, so identify the form and convention that support your correction. Schieber is a form of Jass in which players choose the game arrangement in a defined exchange; state that form if it matters to the report. Obenabe, the ascending card order used in one game form, and Undenufe, the descending card order used in another, should not be treated as interchangeable conventions. A correction should say which practice the source describes. Use Swiss German terms of art accurately. Weis means a declared scoring combination. Stöck refers to the relevant combination involving the king and queen of the trump suit. Puur is the Swiss German name for the trump jack, while Nell is the Swiss German name for the trump nine. If a correction concerns one of these terms, identify the cards and the game form rather than relying on a general statement about scoring. A strong report can follow this structure: - **Page or subject:** identify the relevant passage or rule. - **Current wording:** quote the sentence that needs review. - **Proposed correction:** state the replacement or addition. - **Source:** name the publication and relevant passage. - **Variant:** identify the Jass form, region or local convention. - **Reason:** explain how the current wording could mislead a reader. A recognised rulebook, club publication, official regional guide or reliable specialist reference may support a correction. Include the title and the relevant passage. A public link can help locate the source, but a quotation or page reference remains useful if the source is difficult to access. Personal habit should not be presented as a universal rule without evidence that the practice has that scope. If authorities disagree, describe the disagreement rather than selecting one convention without qualification. The appropriate revision may need to explain several accepted practices. Regional rules deserve precise boundaries: name the variant, state the setting and distinguish established practice from an individual table preference. The [card values reference](https://jasvel.org/rules/card-values/) can help you identify the cards involved before sending a report. Include card names, trump status, the selected game form and the relevant declared combination if those details affect the point. A report that says “the scoring is wrong” gives no clear path to checking the claim; a report that identifies the cards, source and convention can be assessed carefully. A scan or photograph may support the written citation when a source uses a specialised layout. Remove unrelated personal information and explain what the image shows. If the source is in Swiss German, include the original wording with a short English explanation rather than relying on an uncertain translation. For example, a correction could quote a sentence about the order of cards, identify Obenabe or Undenufe as the relevant convention, and cite the regional source that supports the wording. A separate paragraph could explain that another region uses a different order. That approach preserves the distinction instead of turning one regional rule into a universal claim. ## How should I report a Jasvel scoreboard bug? A useful scoreboard bug report explains the actions taken, the result expected and the result displayed. Include the game form, the cards or score involved and the point at which the total stopped matching the rule. Begin with the screen where the problem appeared. Describe the selection made, the entry recorded, the trick or declaration involved and the result shown afterwards. If the fault follows a particular card combination, name those cards. If the report concerns trump, Obenabe or Undenufe, explain the selected form because the scoring logic may depend on that choice. A report can include these details: - **Device:** describe the device used to run the app. - **App state:** identify the screen or feature open when the problem appeared. - **Steps:** list the actions that led to the unexpected result. - **Expected result:** explain the total or behaviour that should have appeared. - **Displayed result:** record the total or behaviour that appeared instead. - **Repeatability:** say if the same sequence produces the same result again. Write the steps in the order they happened. For example, explain the selected game form, the cards entered, the declaration recorded and the score displayed after saving the result. A report that jumps straight to the final total may hide the choice that caused the difference. A short sequence of observable actions gives the publisher a better route to checking the fault. A screenshot can support the report, but a screenshot alone rarely shows the full cause. Add a written explanation of the selections and actions. Remove names, notifications and unrelated personal information before attaching an image. Include only material that helps identify the display or reproduce the behaviour. A scoreboard difference is not automatically a software fault. Jass rules can vary by regional convention and game form. A declared Weis, the card combination recognised for scoring, may follow a different convention from the one expected by the reporter. Stöck, Puur and Nell can also matter when the report concerns trump cards or a declared combination. Explain the rule used for the expected result and identify the source if the point is disputed. If sources disagree, name the sources and state which convention the app was expected to follow. The publisher can then distinguish a calculation problem from a difference in rules coverage or wording. The [Jasvel app information](https://jasvel.org/jasvel-app/) page provides product context and may help you describe the feature involved without assuming that every display difference has the same cause. Keep the original sequence available after sending the report. If the problem disappears, record what changed before trying a different sequence. A changed game form, card selection, declaration or saved score may explain why a result cannot be reproduced. Specific evidence gives the report value beyond the first review and helps separate a repeatable fault from an entry mistake. For example, write: “I selected Schieber, entered the listed cards, recorded the declaration and saved the score. The screen then showed a different total from the total produced by the cited rule.” Follow that account with the device, the exact selections and a screenshot if one helps. The report then separates observation from interpretation. ## How long does Jasvel take to reply? Jasvel reply times vary because the reference and app are maintained without a dedicated support department. A complete report is easier to assess, but an email does not guarantee an immediate answer. A rules correction may require comparison between regional sources before the publisher can decide how to revise the wording. The review may need to establish the relevant game form, distinguish a local practice from a broader convention and explain the difference clearly for readers outside Switzerland. A scoreboard report may require the reported sequence to be checked before a calculation fault can be confirmed. Allow a reasonable period for review before sending a follow-up. Repeated emails can separate the evidence across several threads and make the original report harder to track. If new information becomes available, reply to the original message and keep the subject unchanged where possible. Mark the added source, reproduction step or observation clearly so the new material can be assessed alongside the first report. A reply may ask for further information, explain that a report remains under review or point to an existing reference page. Such a response does not necessarily mean that the message was dismissed. Some changes require decisions about scope, terminology and regional coverage before a public page can be revised. A careful answer may also explain why more than one accepted practice needs to appear. The publisher cannot promise a personal response to every message. A report without a source, reproducible sequence or relevant context may not support a useful answer. Clear writing still helps the publisher decide what can be checked, even if the final response needs to be brief. For privacy matters, read the [privacy information](https://jasvel.org/privacy/) before writing. Use the contact email for a specific question or report rather than sending confidential material that the publisher has not requested. Attach only the files that support the message and explain what each file demonstrates. Do not include passwords, payment details or unrelated personal information. A term question should quote the sentence that caused difficulty. A score question should identify the calculation or rule behind the expected result. A correction should provide its source and name the variant. These distinctions help the publisher review messages efficiently and keep the Jasvel reference accurate for readers who know different regional traditions. A well-prepared email needs no specialist format. It needs a clear purpose, enough context and evidence that matches the claim. The publisher can then decide if the matter concerns a wording change, a regional rule, a display issue or an explanation already covered by the reference. For example, a follow-up can add one missing source or clarify one card selection without repeating the entire report. Keep the new information in the original thread and identify the change at the start of the message. A concise update is easier to connect with the earlier evidence than a separate message with a new subject. [support@jasvel.org](mailto:support@jasvel.org) The short answer Send Jasvel a clear email using the published contact address. Include the relevant source, game form, actions and displayed result so the report can be reviewed properly. ## Questions ### Where can I find the Jasvel contact address? Use the contact email published on the Jasvel contact page. The page gives the appropriate written route for app questions, scoreboard reports and supported rules corrections. ### Can I send a correction based only on personal experience? You can describe personal experience, but the publisher needs a reliable source before treating the practice as a documented correction. Identify the regional convention or Jass form and explain its scope. ### Should I name the game form in a rules report? Yes. Name the game form whenever the rule depends on the form being played. Regional terms and conventions can differ, so the game form helps prevent a local practice from being stated too broadly. ### What makes a scoreboard report reproducible? A reproducible report records the screen, selections, cards or declarations, saved entries and displayed result in sequence. Explain the expected result as well, using the rule or source behind that expectation. ### Can I attach a screenshot to my message? Yes, a screenshot can show the displayed state. Add written steps and remove unrelated personal information, because an image alone may not show which selections produced the result. ### What should I do if a regional source conflicts with another source? Name both sources and describe the regional setting for each one. State the convention you expected Jasvel to represent so the publisher can explain the difference rather than treating one source as universal. ## A real Schieber table, in your pocket Both decks, every contract, the full written score with Weis and Stöck, and a computer partner that never sees your cards. It plays without a connection, without an account and without advertising. [What the app does](https://jasvel.org/jasvel-app/) App Store · Coming soon Google Play · Coming soon Coming soon to the App Store and Google Play ## Read next - [About](https://jasvel.org/about/) Jasvel documents its sources, names regional rules and tests shared values so readers can trace each Jass result from rule to score. --- HTML version: https://jasvel.org/contact/ Structured data for this site: https://jasvel.org/api/v1/openapi.json · https://jasvel.org/llms.txt Free to quote and reuse with a link back to the source URL above (CC BY 4.0).