next »

[eigenbom]

another animation test: ____________

[eigenbom]

[cactus]

Love the style in this.

[Ashkin]

I just want you to know that the player's unending and almost maniacal grin, even (especially?) when he's holding a weapon of mass destruction, unnerves me to no end.

[eigenbom]

@cactus cheers! and i loved psychosomnium btw

@ashkin haha, yeh i noticed/felt that too. i figure it will offer a nice mood to the game, initially you just think he is happy, but then the grin never falters even when he (you) are killing things, so you might end up really fearing this small clump of pixels..

[xoorath]

Work that strut! Daaaayyyyyyuuuummm gurl!

[BadgerManufactureInc]

This looks very good. I'm excited about playing a demo.

Are you using a tilemap engine?  If so, I'd be interested to hear how you are doing the collisions.

[eigenbom]

@xoorath aw yeh!

@barnaby Cheers! The world is split into a grid, each cell has a 32-bit coordinate, so at a walking rate of 8 blocks a second, it will take about 17 years to get from one side of the world to the other. As for the collisions, the method I'm using has not really been tested on large numbers of entities, but seems to work ok.

Each object in the world gets an integer width w and height h (e.g., 1x3 for moonman), and a collision width and height (.9x2.8 for moonman). the collision width and height are less than the actual width and height so moonman can fall in unit width holes, fit nicely into a cave of height 3, etc.

Sensors are placed on an entity at the junctions of their geometry, so moonman has 8 sensors, 4 on each side. Which sensors are used depends on the direction the entity is going. So when falling straight down only the two bottom sensors are user.

In an update step, the entity's position is updated, and each appropriate sensor is traced through the world using this algorithm. The tracing splits the sensor up into segments, each of which are tested against the cells in turn for collision. If the cells contain a full block or an empty block then the check is trivial. If the cell contains a slope then a little more code magic is required.

That's the general idea, but its a little more complicated. For instance, if the sensors are just points, then some funny stuff can happen, like getting caught on the side of a cliff as you fall. So instead, I include the two adjacent edges to the sensor when checking the collision.

A few random notes:

• When landing on a slope the bottom-side sensors are ignored, and a bottom-center sensor is used instead.
• Entities have an onGround flag, and the physics and collisions are done differently based on this.
• The raycasting can be simplified if you cap the velocity of entities to one tile per frame - but i haven't done this.

Some more refs:
http://info.sonicretro.org/Sonic_Physics_Guide
http://www.gamedev.net/topic/509143-how-to-go-about-platformer-physics/

[Pemanent]

Yeah agreed on the characters smile. Reminds me of No Country for Old Men

[eigenbom]

and just to burn that association into your minds ...

[Belimoth]

and just to burn that association into your minds ...

Needs a themesong.

[Pemanent]

  I'm not going to sleep tonight.


anyways. back to the game. I'm really intrigued so far!

[eigenbom]

Exploring syntax for custom object creation in moonman. Somewhat following the design of the mod system in dungeon siege (url). I'm interested if this script is readable for those who aren't familiar with Lua or scripting in general.

Also, a Q for any mods reading, are we able to get syntax highlighting enabled for the code tags for Lua?

Pastebin higlighted version

Code: (Lua)

-- A prototype of custom sword creation in moonman.
-- BP 14.10.2011

local custom_sword_sprite_id
local custom_sword_id

-- this function creates a template for the new sword
local function custom_sword()
return {
name = "custom sword",
inherits = core_entities.sword,
-- set the default attributes
attributes = {
damage = 10,
speed = 2,
sprite = custom_sword_sprite_id
},
-- this sword kills outright for enemies
-- not wearing armour
onHit = function(self,enemy)
if (not enemy.armor) then
send_message(core_messages.kill, {target=enemy})
return true -- handled
else
return false -- run normal sword onHit
end
end,
-- 5% of swords spawned are practically useless against armoured enemies
onSpawn = function(self)
if (random()<.05) then
self.damage = 1
end
end
}
end

-- the recipe indicates what amount of
-- each item goes where in the 5x5 crafting matrix
-- in this case: its just a vertical line in the center
local recipe = {
craft.coord(2,0) = {core_entities.steel,2},
craft.coord(2,1) = {core_entities.steel,2},
craft.coord(2,2) = {core_entities.steel,2},
craft.coord(2,3) = {core_entities.ebony,2},
craft.coord(2,4) = {core_entities.ebony,2}
}

-- finally, the onLoad function is called at setup
-- and registers the new sprite, sword type, and recipe
-- for building the sword
function onLoad()
custom_sword_sprite_id = register_sprite("custom_sword_sprite_id", "sprites/mysword.sprite")
custom_sword_id = register_entity("custom_sword", custom_sword())
register_recipe(custom_sword_id, recipe)
end

[xoorath]

Also, a Q for any mods reading, are we able to get syntax highlighting enabled for the code tags for Lua?

Is there syntax highlighting for any language?

[eigenbom]

@xoorath not sure, but there should be!

Update: Alrighty, I'm now getting back to the game after a few hectic days graduating and partying. Today I just played with the mockup a little, tweaking the colours a bit and adding some subtle texturing and lighting. I think the mockup is starting to approach something I would be happy with visually.