I can, but I assure you it's a huge mess, as every project I do I might say. Here you go anyway. Run prgmWRMSETUP once to generate the required appvar. Compile whole program as app. The relevant part of the code is in prgmWORMMOVE.

Attached both text and axiom version of BITMAP4.

EDIT : by the way, compile prgmWORMSRC, and you'll need one map - attached it.

Update,

Following the new rules (no going out of the map by left or right), most bugs have been eliminated. Also, worms now die if they fall under the map, and both worms and projectiles are now free to fly above the map with no collision error or memory corruption

I guess that's a release then. I lowered the number of teams to 2 for now, because it makes more sense to have 2 teams of 3 worms than 3 teams of 2.

Yay update! \o/
I should take another 84, just for playing on it.

Oh, well I guess you just have to throw it to Wabbitsign

I'll do that, but you need to wait some time.

Great, it works now thanks! And this is great! It would be nice if you could hold [sto] or [ + ] rather than press and release to move it, but i like the idea of using all those keys to select an angle. It'd be nice too if turning the other direction flipped your angle rather than resetting it to 90º. It'd also be nice if there were a button you could hold to view more of the map, for example pressing and holding [XTØn] and then being able to move the camera freely with the arrow keys. Letting go of the button would slide the camera back to it's normal position around the character.

Also, [Mode] seems to leave artifacts behind when you move the worm, though i assume that's either a debugging thing or something not finished yet since it's not mentioned in the readme

Anyway, great work, Matrefeytontias

Yep, i didn't even notice that they'd changed my +. About the keys, i figured that you'd made it that way on purpose, but i thought it'd be nice to have a slight delay (like when holding the arrows down with _GetKey) before moving the angle again as i like to just use the two buttons when i'm already relatively close

Well that's because the 83+ has fat pixels one thing I also thought of was drawing the hypothetic bullet's trajectory if it was shot, but then I thought it would be too easy (and it's not Worms's way to do, too).

The problem is that to have different aiming lines for each angles you need a very long line. And that's not possible because it would quickly get clipped off the screen by Axe's line routine. A solution I found is saying "haha, that takes a bit of getting used to" and letting it that way

Also yeah, there are 64 angles per quadrant, but only 128 are accessible anyway (you can't fire under yourself).

Oh oops I meant 64 possible angles at all so yeah, 32 per quadrant (you move by a minimum of 2° between 0 and 128 °). Extending the line doesn't seem to be the good solution, and I can't see how a custom line routine would do better than Axe's one given that the size of pixels really is the limitation.