Cardioid: Sunday kind of LÖVE 1K Challenge

[ivan]

Good one zorg.
This last one by grump is amazing.

[grump]

(atm, mine are the smallest in both cases, whether or not we take the fact that the OP specified a "cardioid animation". )

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"

[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]

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