Friends of the NoLimits Community, we would like to invite you to join NLC’s Third official Three Blind Mice in NoLimits 2! This reboot of the NL1 competition was a smash hit with a record turnout of over 36 participants (12 total teams of 3) in 2021 and nearly double in 2023 with 60 total participants (20 total teams).
If you’re not familiar, the format is simple. You are randomly assigned into a group of 3 - 1 track builder, 1 supporter, and 1 themer - with each person given 3 weeks to do their part before passing it along to the next. (This is 1 additional week per role from the previous 2 weeks, a new change with this edition of the competition)
The project AND its team are kept entirely secret until the livestream reveal at the end. Following the livestream, the 3rd participant is able to upload onto the exchange.
In this entry form (check back 1/4) enter your username, email, and list your preference of the desired role from 1st to 3rd, with 1st being your top choice. If you have no problem doing any of the 3, please elect “No Preference.”
You may also elect “substitute”, in case we can’t secure a spot for you on a team, and a participant has to back out midway through. You can not be a substitute and also have a role on another team; names will be entered on a first come first serve basis. Please note, by being a substitute you are committing to any of the 3 roles.
All names will be entered into a randomizer and you will be notified of your role after the deadline to enter (info on that down below). We will need your email to share your file to the rest of your team!
Rules and Scopes of Work: What can each role do?
Each role is responsible for performing tasks that are relevant to their role.
TRACK
The Track Builder develops a single, floating, colorless roller coaster layout with no name. Their responsibilities/restrictions include:
Selects coaster style, car, and train count
NO RMC/WOODEN RIDES ALLOWED
Designs full layout, maintenance layout, block timing, etc.
CAN use block scripts
CAN use Type Settings for any piece of track
Can NOT use Style Settings for any piece of track
Can NOT use Supports, Terrain, or Scenery Tab
Can NOT select colors, coaster name
Can NOT add supports, scenery
Can NOT add any wording, or description to Coaster Properties or Park Settings window
Can NOT show any portion of the ride, in progress or complete, to ANYONE other than myself for questions/troubleshooting.
Can NOT build multiple coasters, including hidden ones. Only 1 “Freeze-able” coaster will be accepted with the name “3BM 2025 Coaster”
The coaster can operate in continuous OR shuttle mode.
Dueling/Racing Coasters can be 1 mobius track or multiple tracks within the same “Freeze-able” coaster
Uploads unencrypted NL2 Package to submission form provided to them upon role assignment
IF THE RECEIVED FILE IS DEEMED UNREASONABLE FOR SUPPORTER TO TACKLE IN 3 WEEKS, TRACK IS SUBJECT TO REJECTION, AND TEAM WILL BE DISQUALIFIED
SUPPORTS
The Supporter will be supporting the colorless roller coaster provided, defining the relationship between the track and the ground/any surface that supports it. Their responsibilities/restrictions include:
Add supports to coaster that connect to the ground
Can NOT modify Track Layout Geometry or Functional Ride Timing, Operational Mode, or Physics … WITH EXCEPTION of using the “Move” and “Rotate” functions ONLY (No “Mirror”) to reposition the layout in world-space as a whole unit.
CAN modify coaster Style settings and separators ONLY , adjusting spine type, crosstie spacing, and tunnels
CAN hide station roofs in the event of close track encounters
CAN make floating supports as long as they are purposeful, structural, and communicates to the Environment/Themer they intent to connect to a surface other than the ground
CAN “stylize” supports (ie “themed” supports) as long as they are structural and connect the track to the ground/surface
Can NOT create 3D objects to “ground” supports, that is Environment/Themer’s Responsibility
Can NOT use the Scenery Tab or change the Environment
MAY use a Clearance Envelope object while building as long as it’s removed before submission
CAN hide Transfer Track Supports to make custom ones, if applicable
CAN use the Terrain Tab to modify and (optionally) paint the terrain
Can NOT modify coaster track or settings, or support colors
Can NOT show any portion of the ride, in progress or complete, to anyone.
Uploads unencrypted NL2 package to submission form provided to them upon role assignment
ENVIRONMENT
The Environment/Themer will be determining the theme and appearance for the roller coaster provided, giving the project a name, its colors, and the environment for the ride experience. Their responsibilities include:
Selects colors, name of coaster
CAN use Scenery Tab to add or create scenery of all types. This includes (but is not limited to) foliage, lights, 3D objects, custom trains, custom track, scripted sequences, etc.
CAN create custom environment (.nl2env)
CAN use Terrain Tab to modify terrain AS LONG as it DOES NOT modify the supports’ relationship between the track and the ground
CAN create custom trains, custom track, and .nlsco scripts
Can NOT modify Track Layout Geometry or Functional Ride Timing, Operational Mode, or Physics
CAN modify coaster style settings and separators, use caution as this may impact supports with different spine settings
CAN modify transport/brake visibility pending the desire to add custom track hardware and infrastructure (eg custom stators, brake fins, sensors, etc.)
Can ONLY modify station and storage settings to SHOW/HIDE building structures, or modify transport/brake style and visibility (ex: tires, LIMs, etc)
CAN add additional coasters for utilitarian purposes only or background (eg, other coasters in a “park”)
CAN edit Park Settings with Project name and Optional Description (NO MENTION OF USERNAME)
MUST provide a desired “Splash Screen” in Park Properties
Can NOT show any portion of the ride, in progress or complete, to anyone, even after submission.
Must upload the completed project as an unencrypted NL2 Package to the submission form provided
MUST NOT BE UPLOADED OR SHARED IN PROGRESS OR TOTATILITY UNTIL CONCLUSION OF LIVE STREAM REVEAL
ALL ROLES:
ARE NOT PERMITTED TO DISCLOSE THEIR ROLE on discord, forums, or to peers AT ANY TIME during the active competition
ARE NOT PERMITTED TO DISCLOSE THEIR ROLE UNTIL AFTER the livestream reveal
ARE NOT PERMITTED to go beyond their scope of work
ARE NOT PERMITTED TO REVEAL ANY PORTION
If an entrant fails to perform the above tasks, their team’s entry is at risk for disqualification.
JUDGING:
The projects will be assessed in 4 categories:
Individual Performance of Track Builder
Individual Performance of Supporter
Individual Performance of Themer
Combined Performance, Project “Cohesion”
The projects will be assessed by a combination of judges who are aware of the team personnel, and others who will be “blind” and not know the team pairings until the livestream reveal.
Current Confirmed Judges:
A113
Amalia
Pear
Keltan
Joseph
Schedule and Deliverables:
Sat, Jan 4 @ 11:00 AM Eastern Standard Time (EST): Entry Form Open Wed Jan 8 @ 9:00 PM (EST): Entry Form Deadline Sun, Jan 12 @ 11:00 AM (EST): Roles Assigned via Email. Track Builders may begin when notified; other entrants please standby Sat, Feb 1 by 8:59:59 PM (EST): Track File Submission Deadline. Files are processed and then distributed to supporters, who may begin when files are received. Distribution times may vary, dependent on when files are received. Sat, Feb 22 by 8:59:59 PM (EST): Support File Submission Deadline. Files are processed and then distributed to environment/themers, who may begin when files are received. Distribution times may vary, dependent on when files are received. Sun, March 15 by 8:59:59 PM (EST): Environment File Submission Deadline, Project Complete! Files are processed and then distributed to judges for review. Judges will be blind; in other words, not know who is on each team until…
TBD: Livestream announcement showing the top finishers and revealing team members for each project. Environment/Themers permitted to upload their teams’ ride onto exchange with fellow team names after livestream concludes.
NL2 Three Blind Mice #3 - 2025
Hosted by A113
Intro
Friends of the NoLimits Community, we would like to invite you to join NLC’s Third official Three Blind Mice in NoLimits 2! This reboot of the NL1 competition was a smash hit with a record turnout of over 36 participants (12 total teams of 3) in 2021 and nearly double in 2023 with 60 total participants (20 total teams).
If you’re not familiar, the format is simple. You are randomly assigned into a group of 3 - 1 track builder, 1 supporter, and 1 themer - with each person given 3 weeks to do their part before passing it along to the next. (This is 1 additional week per role from the previous 2 weeks, a new change with this edition of the competition)
The project AND its team are kept entirely secret until the livestream reveal at the end. Following the livestream, the 3rd participant is able to upload onto the exchange.
You can check out the previous livestreams below:
3BM 2021
https://www.youtube.com/watch?v=BNBiVkgtcz0
3BM2 2023
https://www.youtube.com/watch?v=i-Ks4wvELKc
Team Selection
In this entry form (check back 1/4) enter your username, email, and list your preference of the desired role from 1st to 3rd, with 1st being your top choice. If you have no problem doing any of the 3, please elect “No Preference.”
You may also elect “substitute”, in case we can’t secure a spot for you on a team, and a participant has to back out midway through. You can not be a substitute and also have a role on another team; names will be entered on a first come first serve basis. Please note, by being a substitute you are committing to any of the 3 roles.
All names will be entered into a randomizer and you will be notified of your role after the deadline to enter (info on that down below). We will need your email to share your file to the rest of your team!
Rules and Scopes of Work: What can each role do?
Each role is responsible for performing tasks that are relevant to their role.
TRACK
The Track Builder develops a single, floating, colorless roller coaster layout with no name. Their responsibilities/restrictions include:
Selects coaster style, car, and train count
NO RMC/WOODEN RIDES ALLOWED
Designs full layout, maintenance layout, block timing, etc.
CAN use block scripts
CAN use Type Settings for any piece of track
Can NOT use Style Settings for any piece of track
Can NOT use Supports, Terrain, or Scenery Tab
Can NOT select colors, coaster name
Can NOT add supports, scenery
Can NOT add any wording, or description to Coaster Properties or Park Settings window
Can NOT show any portion of the ride, in progress or complete, to ANYONE other than myself for questions/troubleshooting.
Can NOT build multiple coasters, including hidden ones. Only 1 “Freeze-able” coaster will be accepted with the name “3BM 2025 Coaster”
The coaster can operate in continuous OR shuttle mode.
Dueling/Racing Coasters can be 1 mobius track or multiple tracks within the same “Freeze-able” coaster
Uploads unencrypted NL2 Package to submission form provided to them upon role assignment
IF THE RECEIVED FILE IS DEEMED UNREASONABLE FOR SUPPORTER TO TACKLE IN 3 WEEKS, TRACK IS SUBJECT TO REJECTION, AND TEAM WILL BE DISQUALIFIED
SUPPORTS
The Supporter will be supporting the colorless roller coaster provided, defining the relationship between the track and the ground/any surface that supports it. Their responsibilities/restrictions include:
Add supports to coaster that connect to the ground
Can NOT modify Track Layout Geometry or Functional Ride Timing, Operational Mode, or Physics … WITH EXCEPTION of using the “Move” and “Rotate” functions ONLY (No “Mirror”) to reposition the layout in world-space as a whole unit.
CAN modify coaster Style settings and separators ONLY , adjusting spine type, crosstie spacing, and tunnels
CAN hide station roofs in the event of close track encounters
CAN make floating supports as long as they are purposeful, structural, and communicates to the Environment/Themer they intent to connect to a surface other than the ground
CAN “stylize” supports (ie “themed” supports) as long as they are structural and connect the track to the ground/surface
Can NOT create 3D objects to “ground” supports, that is Environment/Themer’s Responsibility
Can NOT use the Scenery Tab or change the Environment
MAY use a Clearance Envelope object while building as long as it’s removed before submission
CAN hide Transfer Track Supports to make custom ones, if applicable
CAN use the Terrain Tab to modify and (optionally) paint the terrain
Can NOT modify coaster track or settings, or support colors
Can NOT show any portion of the ride, in progress or complete, to anyone.
Uploads unencrypted NL2 package to submission form provided to them upon role assignment
ENVIRONMENT
The Environment/Themer will be determining the theme and appearance for the roller coaster provided, giving the project a name, its colors, and the environment for the ride experience. Their responsibilities include:
Selects colors, name of coaster
CAN use Scenery Tab to add or create scenery of all types. This includes (but is not limited to) foliage, lights, 3D objects, custom trains, custom track, scripted sequences, etc.
CAN create custom environment (.nl2env)
CAN use Terrain Tab to modify terrain AS LONG as it DOES NOT modify the supports’ relationship between the track and the ground
CAN create custom trains, custom track, and .nlsco scripts
Can NOT modify Track Layout Geometry or Functional Ride Timing, Operational Mode, or Physics
CAN modify coaster style settings and separators, use caution as this may impact supports with different spine settings
CAN modify transport/brake visibility pending the desire to add custom track hardware and infrastructure (eg custom stators, brake fins, sensors, etc.)
Can ONLY modify station and storage settings to SHOW/HIDE building structures, or modify transport/brake style and visibility (ex: tires, LIMs, etc)
CAN add additional coasters for utilitarian purposes only or background (eg, other coasters in a “park”)
CAN edit Park Settings with Project name and Optional Description (NO MENTION OF USERNAME)
MUST provide a desired “Splash Screen” in Park Properties
Can NOT show any portion of the ride, in progress or complete, to anyone, even after submission.
Must upload the completed project as an unencrypted NL2 Package to the submission form provided
MUST NOT BE UPLOADED OR SHARED IN PROGRESS OR TOTATILITY UNTIL CONCLUSION OF LIVE STREAM REVEAL
ALL ROLES:
ARE NOT PERMITTED TO DISCLOSE THEIR ROLE on discord, forums, or to peers AT ANY TIME during the active competition
ARE NOT PERMITTED TO DISCLOSE THEIR ROLE UNTIL AFTER the livestream reveal
ARE NOT PERMITTED to go beyond their scope of work
ARE NOT PERMITTED TO REVEAL ANY PORTION
If an entrant fails to perform the above tasks, their team’s entry is at risk for disqualification.
JUDGING:
The projects will be assessed in 4 categories:
Individual Performance of Track Builder
Individual Performance of Supporter
Individual Performance of Themer
Combined Performance, Project “Cohesion”
The projects will be assessed by a combination of judges who are aware of the team personnel, and others who will be “blind” and not know the team pairings until the livestream reveal.
Current Confirmed Judges:
A113
Amalia
Pear
Keltan
Joseph
Schedule and Deliverables:
Sat, Jan 4 @ 11:00 AM Eastern Standard Time (EST): Entry Form Open
Wed Jan 8 @ 9:00 PM (EST): Entry Form Deadline
Sun, Jan 12 @ 11:00 AM (EST): Roles Assigned via Email. Track Builders may begin when notified; other entrants please standby
Sat, Feb 1 by 8:59:59 PM (EST): Track File Submission Deadline. Files are processed and then distributed to supporters, who may begin when files are received. Distribution times may vary, dependent on when files are received.
Sat, Feb 22 by 8:59:59 PM (EST): Support File Submission Deadline. Files are processed and then distributed to environment/themers, who may begin when files are received. Distribution times may vary, dependent on when files are received.
Sun, March 15 by 8:59:59 PM (EST): Environment File Submission Deadline, Project Complete! Files are processed and then distributed to judges for review. Judges will be blind; in other words, not know who is on each team until…
TBD: Livestream announcement showing the top finishers and revealing team members for each project. Environment/Themers permitted to upload their teams’ ride onto exchange with fellow team names after livestream concludes.