Before The Details
Hey, y’all! This event is something I’ve wanted to do for a long while and I’m glad I’m finally able to go ahead with it. The ultimate goal here is to help people get builds they want that aren’t already easy to find, by setting it up as a competition. The 3-team prize hopefully encourages more participation and peoples’ best efforts.
If anyone finds an issue with any aspect of the event, feel free to bring it up with a staff member, though I’d encourage talking to Amelium (me) directly given I’m the primary host of this event. We’ll do our best to make this event run as smoothly as it can, but given it is a first time thing, I won’t be surprised if things are a little bumpy along the way.
I wish everyone the best of luck and remember that whether or not you win, you are still helping people get the builds they want and your effort is much appreciated 
Most sections below are collapsed to avoid them initially burying one another. Below this one, there are 6 top-level sections (the ones with the biggest titles).
Frequently Asked Questions
Click to toggle FAQ
How many people can be on my team? Anywhere from 1 to 3, so solos are fine.
What is the competition about? Read the “Basic Event Details” section for a brief overview, but really you need to read everything to get a full picture of how things will work.
What’s the prize? Details on that are in the “About Teams” section.
What metrics matter for the submissions? Only that it meets the requirements listed in the request and it isn’t unreasonable (excessively large/slow/etc).
I’ll add more questions and answers as needed.
The Bounty Board (The requests you need to build)
Click to toggle Bounty Board
Remember to include the request number when submitting so we’re aware of which request you’re submitting for. To start things off, there are a few simple/trivial requests prepared in advance, rather than just starting with a blank board.
1 - Submitted by Waffle (Wueffi)
4 inputs, 2 outputs
Out-A: when 2-3 inputs are on
Out-B: when 4 inputs are on
2 - Submitted by Amelium
10 inputs, 1 output
Output is on when a prime number of inputs are on
3 - Submitted by _zebek
Circuit that determines which of the N inputs was pressed first, resettable, infinitely expandable
4 - Submitted by ChocoFlufe
small vertical bit selector, ie test if bit x is on in number y
x is a bit selector for y, that bit is passed as the output
y is 8 bits
5 - Submitted by Amelium
A shift register which stores hex (signal strength) and should turn on an output when the 3rd slot is divisible by the 4th but not the 2nd
6 - Submitted by Amelium
A hex (signal strength) logic unit which performs the typical bitwise operations (OR, NOR, AND, NAND, XOR, XNOR)
Inputs should be 4 hex digits, arithmetic is not requested
7 - Submitted by Amelium
A 2 bit ALU which performs these operations: multiplication, division, nand, imply, and nimply
2 bit inputs, 4 bit output
8 - Submitted by Amelium
An 8 bit input and output where, if a composite number is input, output the corresponding prime number and vise versa
The “corresponding” number is simply that the nth prime corresponds to the nth composite
2 ↔ 4, 3 ↔ 6, 5 ↔ 8, 7 ↔ 9, 11 ↔ 10, etc
The input and output only need to go up to 8 bits, so if the corresponding output would be more than 8 bits, the output doesn’t have to be at all accurate to the true value
9 - Submitted by Mixelmaniac7
Make a 4 bit LRU algorithm (pseudo or true) with 4 inputs and an extra button, when the button is pressed it will output which of the inputs was pressed the least recently. The pseudo can be off by 1 value (so that the 2nd least used could also be chosen, but try to get it accurate as possible) and size under 512 blocks in volume
10 - Submitted by SM0LDER
Collatz machine that takes in a 32 bit value
20 ticks per iteration at most, output data should be each value in the sequence, and it must stop at 1
11 - Submitted by Amelium
2 tall 4 bit alu, the bottom block is all a solid block, so only the top block is available for logic and such
should have standard alu ops (add, sub, or, nor, and, nand, xor, xnor)
12 - Submitted by _zebek
Horizontal CCA
8-bit CCA with horizontal inputs and outputs
max delay of input → output = 5t (dont care about COUT)
2 wide stackable per bit
8 blocks tall maximum
13 - Submitted by _zebek
Sum with conditional multiplier
You have three 3-bit inputs: A, B, C
If A, B, C are unique → output A+B+C
If two inputs are equal → output 2x(A+B)+C or 2x(A+C)+B or 2x(B+C)+A; depending which inputs are equal
If all inputs are equal → output 3x(A+B+C)
Maximum delay of 32 ticks.
14 - Submitted by _zebek
Note block reverb
The goal is to fire a sequence of at least 10 note block notes each 1 GAME tick apart after player uses the input.
The input can be anything player is able to interact with but max delay between input and first note is 2 REDSTONE ticks.
Each note of the sequence should be able to be any pitch (instrument doesn’t matter).
It should also be toggleable, meaning there is a switch that enables or disables all noteblocks.
It should be 2 wide or 2 tall (up to you) stackable.
15 - Submitted by _zebek
Matrix determinant
Calculate determinant of a 4x4 matrix. Matrix entries are at minimum 4-bit, two’s complement values.
16 - Submitted by Waffle (Wueffi)
5x5 Game of life Cell (5x5 meaning 5x5 Lamps with a 1 block border inbetween each cell), should be 20rt per Cycle at most.
Basic Event Details
Submit builds based on a list of requests from the community to earn points
Anyone can request a build, competing or not
Teams can have 1 to 3 members
Each member on the top 3 teams will be able to claim a steam gift card between $5 and $25 (corresponding to their placement) (alternate prizes may be available, but are not likely)
Event Rules
Click to toggle Event Rules
This being a unique and new event, there is potential for rule-changes. If these occur they will likely be low-impact, but regardless we will make an effort to inform all participants. We encourage everyone to make an effort to check for changes themselves, but with any luck we won’t have anything significant.
These are the rules which apply more generally to ORE events, rather than this particular one:
- You CANNOT use a build copied from another team
- There is a gray area with common builds. With very popular designs, it likely won’t be an issue, but we encourage not intentionally finding out the hard way.
- You CANNOT use a build made prior to the event
- This applies to builds which make up most or all of a final submission, not smaller components (A CCA made before the event would be perfectly fine to use if the submission was a CPU)
- Attempting to exploit loopholes or oversights in the rules is NOT allowed
- If you’re concerned about this, we encourage talking to staff to clear things up, though you’re likely fine if you aren’t aiming to make things unfair
- Staff CANNOT win
- A team with a staff member on it cannot win and cannot impact the ability of other teams to win. (In this particular event, that means staff submissions will not impact the final score of the corresponding requests)
And, as always, ORE rules still apply. As with the last listed rule, we can’t catch everything, but you’re always encouraged to talk to staff to clear things up.
About Teams
Click to toggle Team Info
Your team can have anywhere from 1 to 3 people on it. The prizes are as follows:
| Overall Placement | Prize (in Steam Gift Cards) |
|---|---|
| 1st | $25 per Member |
| 2nd | $10 per Member |
| 3rd | $5 per Member |
The details about how placement is determined is available in the section on Fulfilling a Bounty Board Request
Ties
Ties will be broken by determining who submitted their final build first. If two players tied for 2nd, the person who loses the tie would be in 3rd. If three players were tied for 2nd, the fastest team would get 2nd, next fastest 3rd, and slowest would get 4th (no prize).
Alternate Prizes
In certain cases we are open to considering alternatives, but this is both unlikely and discouraged, primarily being reserved for cases where the individual cannot receive a steam gift card and has an alternative we consider reasonable. No, we will not give the cash directly.
Competition Server
While this particular event doesn’t require the use of the competition plots, we still require teams to be created on the competition server. This system already keeps track of teams during events, so there’s no reason to avoid making use of it. We also recommend using the competition plots, but this is not required.
Unchanging Teams
After a team is created, there is no changing it. If you have any reservations about teaming with someone, we suggest resolving that before creating your team, rather than finding out during the event that you’d like to change things. (Having to “untangle” teams is always a mess and it’s hard to determine who should get credit for what.)
Adding to the Bounty Board (making a request)
Click to toggle Info on Adding to the Bounty Board
Requests should be posted in the #June 2025 thread in the Discord server. If your request hasn’t been added for a few hours, you are free to ping Amelium ONE TIME. If that doesn’t work, just send a DM.
Anyone is free to make a request, competitor or not, though if you are competing YOU ARE NOT ALLOWED TO MAKE A SUBMISSION FOR YOUR OWN REQUEST
There are a few rules for what is allowed of a request:
- Must not be a frequent/common build (i.e. 8 Bit CCA)
- Must have a legitimate purpose (Often something useful within a larger context, like an ALU) (It can be weird, just not obviously useless)
- Should be reasonable to build within the competition timeframe (A bit less than a month, accounting for there likely being many other builds)
- Easy to verify if it works (Remember, we will likely have to check a handful of these for each team)
Just to cover our bases, we do reserve the ability to remove or deny requests we deem against the spirit of the event. We probably will cut off anyone with more than a few requests to give everyone a fair chance, so if you’ve got a lot of ideas, it’s best to prioritize your favorites.
Fulfilling a Bounty Board Request (submitting a build)
Click to toggle Info on Submitting a Build
Below are details on teams submitting their builds for a request.
How to Submit
Since this event focuses on many individual builds rather than a singular build, we felt it best to take submissions individually as well. This allows for us to verify early submissions so there are less to worry about later on.
Submissions will be done through the ORE Discord Server, if for any reason you can’t/don’t have a Discord account, you’ll need to have a teammate who can or someone outside of your team that you trust to submit for you. Staff are an option, but we do encourage you to find a solution yourself (to avoid staff having to submit for many teams).
Submissions will be done specifically in the #bb-submissions thread in the #events channel. The format of a submission is as follows:
Team Member:
Request being filled:
(Attach schematic file to message)
Team Member
Simply write the username of one member of the submitting team. If submitting for your own team, simply write your own username. This is mainly to help in the case of someone submitting for someone who cannot submit themselves.
Request being filled
The number corresponding to the request being filled.
Schematic File
Getting the schematic file through ORE does require a Discord account, but so does submitting a build during this event. Using these commands also requires Builder rank.
ORE allows players to create (and then send) a schematic by doing the following:
- Select a build and
//copyit //savethe build with the desired name- Download the build from ORE’s Schemati
- Follow the above instructions for where/how to submit on Discord
If any schematic is invalid when uploaded to ORE, the submission will not be considered valid.
How Bounty Points Work
Requests are worth points based on the number of submissions made for that request. All requests start worth 20 points, but this goes down by 5 points for every valid submission more than 1. Below is a chart showcasing the number of points a request is worth.
| Number of Teams | Points per Team |
|---|---|
| 1 | 20 |
| 2 | 15 |
| 3 | 10 |
| 4+ | 5 |
It is worth noting that being first, last, or anything in between does not impact the amount of points you get from a submission. The points are determined by the FINAL number of points each request has, NOT the amount when you submit. As long as the build passes verification, you’re good!
Submission Verification
A few staff members will be reviewing the submissions to see if they work. This will be done during the course of the event (and likely after submissions close depending on the backlog). If your build is marked as invalid, you are free to resubmit, though of course we encourage you to try being as certain as possible that your build passes to avoid wasting time.
Lastly
Remember to leave a like on the post! If we hit 1 million likes I’ll finally do a fae reveal! That’ll be where I reveal the name and address of the fae that cursed me.