GMLscripts.com

image_angle+=median(-5,angle_difference(point_direction(x,y,mouse_x,mouse_y),image_angle),5);
or
image_angle+=lengthdir_y(5, image_angle - point_direction(x,y,mouse_x,mouse_y));

Salut Nerval. I'm French too but not from France.

a cheap way, but not accurate is to cal d3d_set_fog(1,color,0,0) (fog on) then draw scaled up so it's larger, then call d3d_set_fog(0,color,0,0) (fog off) then draw_self over that.

works for sprites origins centered that dont have compex shshapes

Good stuff. subtract and divide can be derived from those too.

Quickly some things before My mind crashes from lack of proper sleep. sorry if some of it sounds weird. tired

You need to provide the mech/robot or tank template with the basic feature (hard point attachement and firering) and only provide an entry point for the code, like a blank DoStep(). and have strict access like you imply to components that are attached through a specific API same for the targets available in the game. because if people are allowed to play in the core stuff, like even do a instance_nearest and you have rules that they cant see though walls or know where the target is in certain circumstances....

Same for the path system you need to have that handled by an api. so that the contestant cant simply do a mp_path towards a target without following the rules.

here is what I would have as components

1)line sensors. (aka collision_line first). the line sensor finds detect all objects in the arena, walls, pickups, other robots, bullets, missiles, rockets and waypoints nodes at a range of 400, can rotate up to 15 degrees a second

2)cannon, fires a bullet every 5 seconds at a range of 200, 100 bullets, 10pt damage

3)missile, fires a missile every 10 seconds at a range of 400, 3 missiles, 25 pt damage, 10 health

4)rocket fires a 3 rockets every 5 second at a range of 300, 15 rockets, 10 pt damage each, 10 health

5)Anti missile (shaff) (6 on board)

6) Gun. 1 damage, 100 distance, unlimited, 4 bullets a second

The robot body
The body has 8 attachment points to attach components

The head has 4 attach points

Only the sensors can be used to navigate the field. or find objects to travel to or attack

Waypoints for the room are always 300 pixels apart and have a 32x32 sprite for sensor detection

Walls are 64x64 sprites

The AI can have a memory of up to 100 items?

Navigation and targeting can only be done through the sensors

I was making this a while back

http://host-a.net/u/icuurd12b42/PiinballTutorial.05.gmk . the flippers are a little nasty but the rest is pretty stable

I used point_line_distance with segment true. and the normal is point_direction(x0,y0,x,y). setting on the line is siply x,y = x0,y0+lenghtdir_x/y(ball_radius,normal) if point_distance(x0,y0,x,y) is smaller than radius of the ball

this will handle both sides of the line and the tips. and will work for convex shapes as the collision usually resolves itself naturally in a single pass when the ball is in contact with 2 lines during you iteration process (a process which you can delegate to GM's collision event system) for concave shapes, you need to iterate through the shape lines multiple times until their is no more conflict, AKA a line pushes the ball in another line, that other line pushe back the ball inside the first line... For this case the multiple pass probably need to move the ball gradually outside collision so each line can push the ball outside in concert.
x0,y0+lenghtdir_x/y(1/*ball_radius*/,normal)

Yep. I tried it after I read you post. I had just tried to used it before I posted. Nothing I have ran