for(i=0; i<40; i+=1)
{
stepx[i] = x;
stepy[i] = y;
};
p1 = 0;
p2 = 8;
p3 = 16;
p4 = 24;
p5 = 32;p1 is the head, the other parts have a distance (in steps) from the head.if(keyboard_check(vk_left)) { x -= 1; }
else if(keyboard_check(vk_right)) { x += 1; };
if(keyboard_check(vk_up)) { y -= 1; }
else if(keyboard_check(vk_down)) { y += 1; };
if(x != xprevious or y != yprevious)
{
stepx[p1] = x;
stepy[p1] = y;
p1 = ((p1 + 1) mod 40);
p2 = ((p2 + 1) mod 40);
p3 = ((p3 + 1) mod 40);
p4 = ((p4 + 1) mod 40);
p5 = ((p5 + 1) mod 40);
};If the head doesn't move then nothing is stored.draw_sprite(sprmoldorm,0,stepx[p1],stepy[p1]);
draw_sprite(sprmoldorm,0,stepx[p2],stepy[p2]);
draw_sprite(sprmoldorm,0,stepx[p3],stepy[p3]);
draw_sprite(sprmoldorm,0,stepx[p4],stepy[p4]);
draw_sprite(sprmoldorm,0,stepx[p5],stepy[p5]);
objectID = collision_rectangle(x1,y1,x2,y2,Monster_Par,precision,notme);
while(objectID > 0)
{
if(objectID.stunned == false)
{
newStar = instance_create(x,y,objectStar);
newStar.FollowObject = objectID;
objectID.stunned = true;
};
instance_deactivate_object(objectID);
objectID = collision_rectangle(x1,y1,x2,y2,Monster_Par,precision,notme);
};
instance_activate_object(Monster_Par);This will also prevent the creation of multiple star objects, but you need to set the stunned variable in the creation code.x = FollowObject.x;
y = FollowObject.y;- Walls stop projectiles when Link is at higher level of ground.
- When I walk around with the lantern the flame has a delay as opposed to the lantern itself. I haven't played the original so I can't tell if this done deliberate. Looks a little weird seeing the flame outside of the lantern.
- The explosion of one bomb does not set of the explosion of another when they are next to each other.All of these things are just like in the original, but I should agree that all of them are weird.
- Is it correct that Link can't seem to walk through pebbels, that don't even look bigger than his feet?
- You can't activate certain items while moving, that you should be able to activate. Like the magic rod, shield, and boots.The item activation will be easy to fix, but the problem of get through walls will be more complicated.
- Damaging yourself with a bomb can get you through walls.
- The screen lost focus for a second at the start. Just once and not too noticable. Did you check the option to prevent this?Good eyes, it was caused by an old piece of code in the creation event, it's already fixed now, thanks.
You have a bug in which sprite to show when walking.I don't know yet how to fix this, because when I change something it bug other animations.
If you hold down left then press and hold up, then let go of left while pressing right while still holding up, Link's left facing sprite will stay.
I can post screenshots if needed. I had Link doing the moonwalk across the room.
Same applies to going right as well.
The items work fine i guess, but why don't the bombs destroy the bushes like the lamp does?
However Freki's approach to hardcode the frame determination with a selection structure is not something I would do either. This result in that you need to write duplicate code for a lot of situations that you can put in a more general and modular algorithm.
if(global.T_CONTROL == 1)
{
switch(action)
{
case "PULL":
if(frame mod 64 < 32)
{
linkPull();
}
else if(keyboard_check(global.button[BTN_ACTION]))
{
// code that checks if it should continue to pull or just stand and hold the object
}
else
{
action = "STAND";
sprite = spr_linkStand;
frame = 0;
linkStand();
};
break;
case "ANY_ACTION":
if(keyboard_check(global.button[BTN_ACTION]))
{
action = "PULL";
sprite = spr_linkPull;
frame = 0;
linkPull();
};
break;
};
};
So basically I'm just change the action, the sprite that will be used, reset the frame count and execute the script.This is what I would do for sprite animations if I had to build my engine from scratch. I would provide the algorithm with the following information:
* The sprites/frames to draw for the animation
* A list of durations for each frame. When my algorithm is cycle based than the durations are in the number of gamecycles, is my algorithm time based then the duration is the minimum number of milli(/nano)seconds.
* Indicator of the current frame.
/* PULL */
switch(frame mod 64)
{
case 0: image = 3 + face * 9; break;
case 16: image = 4 + face * 9; break;
case 24: image = 5 + face * 9; break;
case 32: image = 6 + face * 9; break;
case 48: image = 7 + face * 9; break;
case 56: image = 8 + face * 9; break;
};
frame += 1;
if(frame == 192)
{
frame = 0;
redface = 1;
};
Here is the error, 0 is the first session:Pretty sure that's not the problem.Code: [Select]if (mplay_session_find() > 0)
but your Nayru's Pearl seems to be better because the circles are together in the center
They're not supposed to be together in the center, but the sides are supposed to touch. So neither one is entirely accurate. I do think the pearls in the Minish Cap look better though, and why wouldn't they? They were made by the graphic artists from an official game.
(I know I'm responding to an old-ish post >.>)
