I made an attempt at the Trijam#263 . You can see it here.
This is what I had in my mind before I started.
There are still bugs with the rendering of the polygons, but you should be able to reset any problems with the "more meat!" button.

This was inspired by the story about the butcher by Chuang Tzu (4th century BCE)

How to play:

1) Click somewhere to position your knife
2) Click and hold to define the curve of your swing
3) Watch the "meat piece" fall
4) You can repeat steps 1-2-3 as much as you like
5) Click "more meat" to start over

Timesheet:

(not counted) brainstorm 02:13
(not counted) learning 01:42
(not counted) project setup 02:00
not counted 05:55
coding 07:00
graphic art 01:10
sound 00:25
actual development 08:35
Total 14:30


assets:

sound:
https://freesound.org/home/login/?next=/people/scriptique/sounds/50823/
https://freesound.org/people/jwsounddesign/sounds/611471/
https://www.fesliyanstudios.com/royalty-free-music/downloads-c/chinese-music/61
(my own)

graphics:
https://upload.wikimedia.org/wikipedia/commons/c/c9/Perkakas_dan_Peralatan_Masak_Rumah_Tangga.jpg
https://pixabay.com/illustrations/knife-carving-chef-kitchen-blade-951503/
https://opengameart.org/content/meat
https://vectorportal.com/vector/papyrus-roll-vector-image.ai/14511


Published 29 days ago
StatusReleased
PlatformsHTML5
Authorthiscris
Made withGodot
TagsTrijam

Comments

Log in with itch.io to leave a comment.

Looks good. Even more zenful now without the page refreshing. I'm curious about how you cut the polygons. Is that a builtin feature for the polygons in Godot? I use Godot but haven't done much in that vein.

There is a helper class called Geometry2D which contains many functions that interact with polygons and lines. I highly recommend to watch this video that describes them. After you draw a curve the game creates a polygon that starts from the bottom and ends with that curve, then an intersection is calculated.

The problem with the disappearing polygons is that after the clipping is done the vertices order sometimes gets messed up - the polygon is still there, but because the points are not ordered sequentially, some parts get inverted and then the whole thing becomes invisible.