Send a note about SledRider.app
Use the email link above or write to [email protected] from your usual mail app. You can use this address to report a problem with a page, question something in a guide, or ask about a picture. Put the part you need help with in the subject. A subject like “Up Arrow scrolls the controls page” gives us a place to start as soon as we open your message.
Include the address of the page where you saw the issue. Several pages offer the same game, with different articles and pictures around it. If the problem is in an article, a heading or the opening words of a sentence will locate it. If it's in the game, tell us what was on the screen just before it happened. A couple of plain sentences are enough to begin. You can send an email even if you aren't sure what caused the problem.
If the game stops while loading
Describe the last thing you could see. The mountain illustration with the website's play button, a loading message inside the player, and the game's title above a snowy ledge are three different points in the launch. A report that says the illustration stayed on screen after you pressed Play gives us a different starting point from one that says the download reached a particular percentage and stayed there.
Tell us which browser you were using and whether you were on a phone, tablet or computer. Include the exact loading message if there's one. For example, you might write that the home page opened in Chrome on a laptop, the game showed a progress number, and the same number was still visible two minutes later. Give the actual number and time you saw. You can send a useful report from the device you have, even if you can't try another one.
On a managed device, the message may come from your school or workplace. If a policy notice appears, quote the part that identifies the restriction and say whether you could still read the guide around it. The person who manages that network can answer questions about local access. A school name or student identifier is unnecessary for a site report.
If a steering key or jump seems wrong
Describe the input and the result as a pair. For example, did pressing Up Arrow move the entire web page, leave the tutorial on the screen, or leave the sled on the ground during a run? Mention whether you had already clicked the instruction below the three wooden arrows. The answers tell us whether to check keyboard focus on the website, the start of the tutorial or the game's response on the slope.
For a touch report, name the control or area you touched and say which way the device was turned. If the problem happens in fullscreen, mention whether the same button worked before you expanded the player. A short sequence such as opening the game, entering fullscreen, tapping a control and seeing the page move is much easier to follow than a list of everything you tried. Write it in the order it happened.
If something changes after a run
For questions about a result, copy the labels as well as the numbers. The end screen separates score, best score, meters and gifts. In one of our short runs the distance read eleven meters while the score read zero. If you tell us which entry looked unexpected and what you thought it represented, we can check the explanation in the guide against the panel you saw.
For a shop or mission question, identify the particular sled or task. The gift balance at the top, the price of a selected sled and the reward for a mission are all quantities of gifts with different meanings. Include the amount before and after the action if you saw both. This site publishes the player and its guides. It has no account controls for changing the balance shown inside the game. Keep passwords and sign-in information out of your message.
Report a page or accessibility issue
A broken navigation link, a missing picture or text hidden behind the player can all be reported without starting a run. Give the page address and the label of the link or control you used. If a link took you somewhere unexpected, include the destination that opened. If an image is missing, quote the nearest caption so we can find the exact placement even when the same picture appears on another page.
For a keyboard or screen reader issue, say what you were trying to reach and where you ended up. An example would be tabbing from the play button, using a control, and losing track of which element has focus afterward. If a zoomed page cuts off a button, include the browser zoom level when you know it. You can describe the problem in words. A screenshot is optional, especially for issues involving speech output or the order of keyboard focus.
Suggest a guide correction
Send the page address, the passage you want us to check and the wording or behavior that you see in the game. A price correction is easiest to check when it names the model. A change to a control is easiest to check when it identifies the input and the device. If a screenshot in the article is out of date, point to something visible that has changed, such as the text on a menu button.
Strategy suggestions are welcome too. Explain the part of the slope, the move you used and the goal it helped you reach. A route that worked well for collecting a gift can be a poor choice on a distance attempt. Naming that tradeoff lets another rider decide when your advice applies. You don't need to beat a record to point out confusing wording or a better way to demonstrate a beginner's move.
Ask about a picture, credit or rights issue
Identify the item by its page, position and caption. For example, the large mountain illustration visible before launch and the tutorial screenshot farther down a guide are separate images. If your concern involves something shown inside the running game, mention which menu or part of the course contains it. These details help us find the material when we look at the page from a different screen size.
If you're asking for a credit change, include the credit currently displayed and the name or link you want us to check. For a rights concern, describe your connection to the material, provide a reference to the original when available, and state the action you're requesting. A public reference or a small crop that identifies the item is usually enough to explain the question. Keep your initial message focused on the relevant image or text.
What to put in a follow-up
Reply to your original email if you discover another detail. Include what changed between attempts. Perhaps the page opened correctly in a regular tab but looked different after rotating a phone, or perhaps the tutorial worked after you clicked inside the player. Reporting that change narrows the issue even if you still don't know its cause.
If you attach a screenshot, crop it to the player or the part of the article in question. The most helpful picture leaves the relevant label and a little surrounding context visible. Browser tabs, inbox notifications, account names and school or workplace identifiers can stay outside the crop. Before sending, check that the page address, the action you took and what appeared next are clear to someone who wasn't there to see it happen.
