Challenge - Feb

[AlexHedley]

🎮 twinBASIC Monthly Challenge #2 - February

Create a Game

Build any game you like using twinBASIC.

This can be a simple card game, arcade game, puzzle, or something more experimental. Creativity is encouraged - there is no “right” genre or style.

📦 Submission Rules

• Built using twinBASIC
• Full source code must be provided, but licence choice is unrestricted
• Submission must be a single .twinproj file (external image and music resource files allowed if necessary)
• Produces a single Windows EXE
• Runs on Windows 10 and later
• Game may be windowed or fullscreen
• Music is optional
• ❌ Not a direct or near-direct port of an existing VB6 game

🎵 Bonus Points

• Inclusion of music or sound effects
• Inclusion of controller support (e.g. XInput)
• Use of GDI+ package ⁠GDI+ Package
• Use of OpenGL ⁠twinBASIC + WinDevLib OpenGL De…
• Clever or efficient rendering techniques
• Use of newer twinBASIC features (e.g. delegates, generics)
• Clean architecture and well-documented code
• Polished UI, UX, or game feel
• Interesting technical tricks (collision detection, AI, etc.)

🎁 Prize

£100 twinBASIC account credit

• Non-transferable
• No cash alternative
• Can only be used towards future twinBASIC licences

🏆 Judging

Entries will be judged across multiple categories, including:

• Originality and creativity
• Technical execution
• Performance
• Visual presentation
• Code quality and structure
• Overall polish and fun factor

Bonus points may be awarded at the discretion of the twinBASIC team.

Winner selected at the sole discretion of the twinBASIC team within 7 days after the entry deadline.

⏰ Deadline

Entries must be received by:

🗓️ 1st March — 12:00 PM (GMT)

Submissions will be locked after the deadline.

🔗: https://discord.com/channels/927638153546829845/1467429513456783498

[KubaO]

Please only include a related set of changes per PR. This PR is about a challenge. There should be one added file only.

In the future, please rebase the change branch to twinbasic/documentation/main, or fast-forward merge it, instead of creating a merge commit. Merge commits don't belong in PRs at all.

There are spurious merges in this PR. You can and should submit checks.yml as a separate PR.

I highly advise using SmartGit if you haven't before. It make it very clear whether the PR is clean. Yours looked as follows:

Here's how I expect it to look:

Please open another PR where this single-file change will stand on its own, and is based on the upstream head (i.e. twinbasic/documentation/main)

I could submit your change myself, but I want you to have credit for it.

[AlexHedley]

Re did: #59