
I've been contemplating this particular tidbit in the COMPO-Rules, and browsing old discussions about the subject.
( Here's a thread from 2 years ago, and a more recent discussion from yesterday.)
I find that a lot of the time it's quite ambiguous how extensive base-code you're allowed to use.
The reason I'm bringing this up, is that a week ago I produced a little physics/platformer-test as a warm-up project, and yesterday I developed it a bit further.

I'm planning to possibly use some parts of it as base-code in the COMPO.
(Specifically a text-prompter and some physics-behaviours)
I thought I'd share it outright just in case.
It's a .MFA-document (Clickteam Fusion), but I also included a playable .EXE and a browser-build on itch.io if someone without the development-software wants to give it a spin.
There's also a crude screenshot of the code included.

The Password is : uddermaul47 :wink: :key:
Would I be eligible to participate in the COMPO with some of the code as a starting point, given I highlight the parts I started out with in my submission?
(After going through the earlier discussions about this subject, I'm pretty sure I'm good to go. But thought I'd still ask just to be sure!)
And obviously I wouldn't be using any sound/graphical assets, level-design etc. that are included in this "DEMO".
Aaaand here's a mandatory list of some of the tools I usually utilize:
OS: Ubuntu-Studio 18.04
Programming: Clickteam Fusion 2.5 (Using WINE !)
Graphics: GIMP, guvcview, ffmpeg, ImageMagick, Kdenlive, Toonloop
Audio: Audacity, sfxr, amsynth, Qsynth, Qtractor, CALF - Studio Gear, SooperLooper, Loopify
Cheers!