Hello, everyone! Overkill here.

I was planning on arranging a Winter competition. There was a bit of discussion about it earlier, but there were some details that weren't entirely clear. Aaaaaaand I even made a bit of a typo in my original post, and this lead me to come up with a weird, yet interesting theme!

How about M!

The contest has only the following game content requirements:

• The game must feature the letter M somehow.
• The game must have at least three distinct areas (but you can have more!).

Everything else is up to you, and keep in mind, creativity is what makes these things fun, so don't be afraid to try something out of the ordinary.

Just because it's around Christmas does mean it needs to be about Winter (even though you could!). And if you don't think your game needs fighting or puzzles to be fun, feel free to come up with something different!

Once again, it's up to you, don't feel restricted.

Verge is the only engine you're allowed to use. But as of Verge 3.1, you have your choice of language, so those who can't stand VergeC can use Lua (and if you're especially OOP happy, the vx library) instead. This is an Hours of Verge contest, after all.

The contest starts next Sunday, December 21, 2008, 12:01 am EST, and ends on Wednesday, December 31, 2008, 11:59 pm EST. That's 10 days, 240 Hours of Verge.

Now get ready, and band together with your friends and fellow Vergers!

M-usic, you say?

That's cool, Syn. It's good to conserve the afore-entioned letter. We'll need it for this co_po, and although the reservoir is still full, I expect we'll have a shortage for the next few weeks after the connpetition. So buy up letter futures now and sell sell sell during the session! Double Ns and upside-down Ws are a good replacewent if you're unable to avoid the letter spoken of.

Now that's a fine idea!

I've got a Google Doc for ideas going.
I sent an invite to you, Syn.
Rockstar, it'd be great to have you on the team, so shoot me an email and I'll invite you too!

Can anyone point me towards a guide to using Lua for Verge? I'm used to calling all the functions in VergeC, but are all the function names the same if I'm using Lua? Is that what Overkill's vx library changes?

Also, Grue, you spelled pulverized wrong. >;) are a handsome sexy man with amazing god-like powers and I pray every night that I can be even the slightest bit more like you when I wake up.

Also I hear you like to abuse your administrative powers sometimes.

Quote:Originally posted by Code

[...]

Can anyone point me towards a guide to using Lua for Verge? I'm used to calling all the functions in VergeC, but are all the function names the same if I'm using Lua? Is that what Overkill's vx library changes?

[...]


I just made a topic about how to setup LuaVerge, should probably get you started on most of the stuff involved.

Anyway, as for vx: vx doesn't just change function names, it introduces an OOP system in Lua so stuff like Images and Entities have methods that directly act on them, instead of the lower-level procedural code which VC brings. And as a side-effect of the OOP, it also gets garbage collection so when an image variable falls out of use it'll auto-free the handles.

It also especially improves the input section of Verge, so that there's a Button class, which all keyboard keys, joystick buttons and mouse buttons use. So you can check them all in the same way.

local myButton = vx.key.Enter

while not myButton.pressed then

    vx.ShowPage()

end

And using this basic idea, it becomes really easy to write a custom input system that maps joystick buttons and keyboard buttons to a single action!

Oh! One good thing to note though: If you only want to use vx's system in tidbits of your game and use raw LuaVerge for the rest, you're free to do that. It plays nice, since whatever in LuaVerge is prefixed like "v3.thing" and whatever is in vx is prefixed like "vx.thing"

Come on ladies, step up. I'm coming out of verge retirement for this one!