all the components that you use in Overture are either default components, or they are custom components that you yourself created. The only exception is RegisterPlus. This has a downside of not being able to restore this component if you change it, without knowing how it works beforehand.
It may be not appropriate as a progression-required level, but it could be an offshoot right after completing overture, where you are asked to recreate that component with correct behavior; it could also be a good opportunity to teach how to work with component memory probes.
#Add a level for RegisterPlus
ivory helm
frozen lichen
Maybe it should actually be required: it is also a good place to explain switched outputs
ivory helm
the first time you encounter switched outputs is in saving bytes iirc
frozen lichen
Yeah, but I would say that explaining them in the context of component factory again is a good idea
ivory helm
ah, ok, that's fair
frozen lichen
Semi-alternative idea: have this as an example for custom levels
I.e. custom levels as component verification
umbral sapphire
I think (optional) extra levels in general would be a good idea, cos the learning curve is quite steep. (for me, but I think I'm not alone)
fair mountain
I.e. custom levels as component verification
could you explain this?
frozen lichen
When custom levels get implemented, the same system can be used to create verification suites for custom components
fair mountain
so basically you have to solve your level to upload it?
ivory helm
so basically you have to solve your level to upload it?
no, it's not about that
imagine that you made a custom counter for your own use, but you want to make sure it's working. you could create a custom level that you never upload, that would test that custom counter, and then put your circuit there and test it
fair mountain
ah ok