Support

Get help signing in, find comfortable settings for your screen, or contact us.

Choose the method you used below. When you are ready to try again, return to Sign in.

Google sign-in

No Google window? Check whether it opened behind your browser. If your browser blocked it, allow pop-ups for this MUTP site, then choose Continue with Google again.
Closed the window or chose the wrong account? Try again, select the Google account you want to use for MUTP, and finish any verification prompts in Google's window.
Cannot sign in to Google itself? Follow Google's account recovery guidance. For a work or school account, your administrator may need to help with sign-in restrictions.

If Google sign-in finishes but MUTP still will not open, contact support with the error you see.

Email sign-in links

No email? Check the address you entered, then look in Spam or Junk and any folders used by mail filters. If you find the message there, mark it as not spam. Allow a few minutes for delivery before requesting another link.
Opening the link? Use the most recent message. For the simplest return, open it in the same browser and device where you requested it. If it opens elsewhere and asks for your email, enter the exact address used to request the link.
Link expired, already used, or still failing? Return to Sign in, check your email address, and choose Email a sign-in link to request a fresh link. If delivery or sign-in keeps failing, contact support.

Contact support

For MUTP help, project or privacy questions, email support@molesunderthepitch.org.

Tell us what you were trying to do, what happened, and which browser and device you used. For sign-in trouble, include the method you chose and any error wording.

Please do not send game credentials, account details, or other sensitive information, including passwords, verification codes or sign-in links. This project cannot provide support for FUMBBL accounts or services.

Recommended viewing sizes

We design live coaching for desktop and laptop computers first, with landscape tablet support. Phones are best suited to the website, replays and spectating. Direct coaching on a phone is best effort.

These sizes describe the available browser content area in CSS pixels, after display scaling and browser zoom. They are guidance, not access restrictions.

Desktop coaching & spectating: 1920 × 900 CSS pixels; Our primary desktop reference is 1920 × 1080 in full screen at 100% display scale and browser zoom.
Smaller laptops & landscape tablets: 1366 × 768 CSS pixels; A smaller viewing target for live play. Check the available space on your device; panel resolution alone does not determine this.
Replay viewing: 1024 × 600 CSS pixels; Allow normal page scrolling. On phones, use landscape for replay and spectating; compact controls can still overlap.

Layout fit is different from comfortable play

Our conservative tested fit references are 1350 × 300 CSS pixels for live coaching/spectating and 980 × 320 for replay with page scrolling. These reference pairs fit the controls in the scenarios measured. They are not universal overlap-free guarantees or useful playing-size recommendations: fitting controls does not establish usability.

Smaller layouts still need improvements to resource wrapping, camera/menu placement, the scoreboard, expanded panels and replay dugout buttons. These are tracked in the compact-layout follow-up.

Display scaling & browser zoom

A high-resolution screen can provide much less layout space when scaling is enabled. For example, a 1920 × 1080 screen at 150% display scale provides at most 1280 × 720 CSS pixels at 100% browser zoom, before browser bars and the taskbar take their share.

Start with 100% browser zoom and a display scale that keeps text comfortable. Full screen can reclaim space. Reducing scaling makes controls physically smaller, so it is not always an improvement.

OS / display scaling 100%

Choose your display scale to calculate the physical-pixel content area needed at 100% browser zoom. This does not change your device or the game.

At 100% display scaling, the physical-pixel content area matches the CSS target.

Desktop recommendation 1920 × 900 CSS px: 1920 × 900 physical px
Laptop / tablet recommendation 1366 × 768 CSS px: 1366 × 768 physical px
Replay recommendation 1024 × 600 CSS px: 1024 × 600 physical px
Live layout-fit reference 1350 × 300 CSS px: 1350 × 300 physical px
Replay layout-fit reference 980 × 320 CSS px: 980 × 320 physical px

Allow extra screen space for browser bars and the taskbar. These results describe the content area, not a guaranteed minimum monitor resolution. The CSS target stays the same at every scale.

Browser zoom applies an additional factor: at 125% zoom, multiply the calculated dimensions by 1.25 again. Tablets and phones also apply their own logical display scale; their advertised panel pixels are not CSS pixels, and their display settings may not use these percentage steps.

Mouse, keyboard & touch

Mouse and keyboard: the preferred setup for desktop coaching. Use a mouse or trackpad for pitch and menu controls, and a keyboard for chat and text entry. Keyboard support does not imply that every match action can be completed without a pointer.

Touch screens: supported for tapping pitch and menu controls, with landscape tablets the intended touch-coaching format. Leave room for controls as well as the pitch. An on-screen keyboard reduces the available viewing area while typing.

Phones: use the website, watch a replay or spectate when a larger screen is unavailable. Viewing needs fewer interactions than coaching, but small screens can still crowd controls. Rotate to landscape when watching a match.

Planning for animated matches

These are project estimates for future animated players, pitch and stadium, not tested minimums or a frame-rate guarantee. Try your existing device before considering an upgrade.

Desktop & laptop: Estimated starting point: a modern mainstream four-core processor, 8 GB RAM and hardware-accelerated integrated graphics. We recommend 16 GB RAM and a recent integrated GPU for more headroom. A dedicated graphics card is not part of this estimate.
iPad, in landscape: Estimated starting point: iPad 10th generation (2022, A14) or iPad A16 (2025).; For more headroom: M1 or later iPad Air/Pro, starting with Air 5th generation (2022), Pro 11-inch 3rd generation (2021), or Pro 12.9-inch 5th generation (2021).
Galaxy Tab, in landscape: Estimated starting point: flagship Tab S8, S8+ or S8 Ultra (2022) with at least 8 GB RAM.; For more headroom: flagship Tab S9, S9+ or S9 Ultra (2023) with at least 8 GB RAM. FE and A models need separate evaluation; a newer model name alone does not establish equivalent graphics performance.

Hardware capability and viewing space are separate: these tablet examples may provide less than the recommended live-play CSS viewport at their default scale. Larger displays usually offer more room for controls.

Keep your browser and operating system updated. Our support policy includes Windows and Linux desktops and Android tablets. Apple guidance is provisional: we have not physically validated iPads or Macs. Browser emulation checks layout and behavior, not device GPU or thermal performance.