Cardioid: Sunday kind of LÖVE 1K Challenge

Show off your games, demos and other (playable) creations.
User avatar
ivan
Party member
Posts: 1911
Joined: Fri Mar 07, 2008 1:39 pm
Contact:

Re: Cardioid: Sunday kind of LÖVE 1K Challenge

Post by ivan »

Good one zorg.
This last one by grump is amazing.
grump
Party member
Posts: 947
Joined: Sat Jul 22, 2017 7:43 pm

Re: Cardioid: Sunday kind of LÖVE 1K Challenge

Post by grump »

zorg wrote: Sat Dec 28, 2019 9:43 pm (atm, mine are the smallest in both cases, whether or not we take the fact that the OP specified a "cardioid animation". :3)
Alright, let's see how far we can bend the rules.

Animated: 63 60 bytes

Code: Select all

function love.draw()love.graphics.print("<3",os.time()%9)end
Not animated: 48 46 bytes

Code: Select all

function love.draw()love.graphics.print"<3"end
And my magnum opus in 9 bytes:

Code: Select all

print"<3"
Last edited by grump on Mon Dec 30, 2019 12:31 pm, edited 2 times in total.
monolifed
Party member
Posts: 188
Joined: Sat Feb 06, 2016 9:42 pm

Re: Cardioid: Sunday kind of LÖVE 1K Challenge

Post by monolifed »

Sorry for not stating the size of mine, it is 283 bytes with animation

Edit: now 252 bytes
main.lua

Code: Select all

a={0,15,10,5,-5,0,0,15}b={0,15,7,15,7,5,0,5}c={}e=0
l=love
z=l.graphics
l.draw=function()z.translate(400,-200)e=.02+e%2
f=e*(2-e)for i=1,8 do
c[i]=50*(f*a[i]+(1-f)*b[i])g=(-1)^i c[17-i+g]=g*c[i]end
z.polygon("fill",l.math.newBezierCurve(c):render())end

here is the final form (printed in error message):

Code: Select all

"<3"
gerip03
Prole
Posts: 1
Joined: Wed Jan 08, 2020 7:49 am

Re: Cardioid: Sunday kind of LÖVE 1K Challenge

Post by gerip03 »

raidho36 wrote: Sat Dec 28, 2019 5:39 am Last time I did this challenge I cheated too, but I used a binary string instead of a base64 encoded string. It allowed me to implement tic-tac-toe with pixel graphics, different colors, score tracking, play against a human and a 2 level AI (no minimax though). Try your luck compressing it into a binary string. Be aware that C++ doesn't likes null characters, so you'll have to screw around with raw text until you get the right compression; automated tools do this but it takes a fair bit of time. You can also improve compression ratio by screwing around with order of text and whatnot. Also, putting the string in a variable instead of passing it directly into the function is a bunch of extra bytes.
Same with me
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 38 guests