{"author_name":"yangamedev","cat":"MiniLD","comments":[],"epoch":1374542220,"likes":2,"metadata":{"p_key":"42343","p_author":"yangamedev","p_authorkey":"20928","p_urlkey":"77967","p_title":"Day 0: Revving the Engine","p_cat":"MiniLD","p_event":"LD26","p_time":"1374542220","p_likes":"2","p_comments":"0","p_status":"UPD5","us_key":"20928","us_name":"yangamedev","us_username":"yangamedev","event_start":"1366934400","event_key":"16","event_name":"LD26"},"text":"

Great seeing all the activity! To fully enjoy this post, open this in a new tab so we can enjoy it together. It’s time for a premature victory lap. Volume warning!<\/p>\n

http:\/\/www.youtube.com\/watch?v=GcTStCOKXGI#t=27s<\/a><\/p>\n

While we sort out what kind of game we want to make, I’m free to explore the tech before I’m crushed by the weight of demands. RTS is terrific for multiplayer re: input, you’re sending commands instead of keyboard input. And not to mention\u00a0no collision<\/strong> gargle. So I’d be remiss if I didn’t take a shot.<\/p>\n

I gambled<\/span>\u00a0on Player.IO as I’m not into hosting a Haxe remoting server and I figure Flash-only-networking for this compo is ok. Yesterday I didn’t know if I could get Player.IO working in Haxe. Today I know!<\/span><\/p>\n

\"shipit\"<\/a><\/p>\n

 <\/p>\n

I long for the day when I’m free to send bullet data across the network every 16 milliseconds. But alas, I’ll spend some time bringing down the 130+kb\/s transfer. \u00a0<\/span><\/p>\n

BTW\u00a0<\/span>The bullets on the other clients are stalled because they don’t know they’ve been told to fire — I can send prefabs across the network but not commands like “go here, this fast” just yet. RPC’s to the rescue!<\/p>\n

Finally, here’s the game code so far, all in one file: CTF.hx:<\/strong>\u00a0http:\/\/pastebin.com\/MD6fdZGe<\/a><\/p>\n

CTF<\/strong> is the class that defines and spawns prefabs like with Unity. It does this by creating Actors<\/strong> (GameObjects), and adding shared Behaviours<\/strong> between them. Once defined, we’re free to spawn them however we like, mixing and matching behaviours as needed for gameplay.<\/span><\/p>\n

You can see it inherits the\u00a0Engine<\/strong>\u00a0class,\u00a0I don’t want to even call it an\u00a0engine<\/strong>, as that implies a huge turkey that you have to stuff in your mouth all at once (UDK, Unity, etc.). With a\u00a0framework<\/strong>, I’m free to nibble or scarf as I choose. Having this class makes creating new games all the quicker because the boilerplate is solved up front, but can be modified per game with overrides to add new components or just replaced completely, see?:\u00a0http:\/\/pastebin.com\/Wz3eh23f<\/a>.<\/p>\n

My strategy this compo: keep the tech clean, funnel in art, stumble over game ideas by accident, be able to punch out a game in 60 seconds …<\/del><\/span>if…<\/del>\u00a0<\/del><\/del>when<\/em> the inevitable Swordfish-hacking-scenario erupts. [IMAGE CENSORED]<\/span><\/p>\n

Stay ready people!<\/p>","time":"July 22nd, 2013 8:17 pm","title":"Day 0: Revving the Engine"}