LF2 GM Progress Thread

[Bamboori]

well the problem is that game maker seems to create a new textuure for each imported sprite. It may not be that much of an advantage, but the loading screen will check which external sources are needed and then load them into the memory, and after a fight those sprites will be cleared from memory.

i guess :P

[Bamboori]

so this is the first design of the .ini files that will contain the dc:
template.ini

Code:

[header]
type=0
included=true
locked=false
random=false

name = Template
head = template_face
file = template_sprites

walking_speed = 4
walking_speedz = 2
running_speed = 8
running_speedz = 1.25
heavy_walking_speed = 3
heavy_walking_speedz = 1.5
heavy_running_speed = 5
heavy_running_speedz = 0.75
jump_height = -17.3
jump_distance = 8
jump_distancez = 3
dash_height = -12
dash_distance = 15
dash_distancez = 3.75
rowing_height = -3
rowing_distance = 5

defense=1
armour_hp=0
armour_level=1
armour_recharge_rate=1
armour_kind=0
armour_sound=0
hit_sound=snd_001
weight=1

[0]
pic=0
state=0
wait=3
centerx=39
centery=79

wp_x=33
wp_y=45
wp_act=21

bdy_count=1

bdy1_x=21
bdy1_y=18
bdy1_w=43
bdy1_h=62

[1]
pic=1
centerx=38
wp_y=47

[2]
pic=2
wp_x=32
wp_y=45

[3]
pic=3
next=0
wp_y=44

since the next tag is the current frame number+1 by default, and all tags that are not changed are copied from the previous frames, the amount of needed tags decreases drastically in follow-up frames.

i dont recommend you to code any characters yet, though.
i still need to plan out a lot of tags and how they will work.

now for some explanation:
included defines whether the image data gets loaded from the internal memory (only for standard characters) or from an external source.
on that note, im not sure yet whether ill include the standard sounds in the .exe or not. ill have to fiddle a little with that to find out whats the best.
locked defines whether the character is selectable by default. this can be changed through events in the game, probably even throughout moves from characters.
random defines whether or not the character will be put into the pool for random selection.

now for the interesting tags

defense is similar to the battle mode defense. the actual damage a character gets from an itr is itr_damage divided by defense.
armour_hp is the maximum hp of the armour.
armour_level is the defense value to be used when the armour is active.
armour_recharge_rate is the rate per frame how much hp the armour regenerates.
armour_kind defines the kind of armour. 0 means no armour, 1 means light armour (no fire/ice protection), 2 means strong armour (protection from fire/ice)
armour_sound is the sound played when the armour is hit.
hit_sound is the sound played when the character is hit. im not sure whether ill leave this tag in since originally there are quite a few sounds that can possibly be played (blood effect, normal hit, strong hit). maybe ill add a tag for each of these sounds, in that case though ill put in some defaults (same goes for armour btw).
weight defines the weight of the character. lf2 has a gravity force of 1.7, so the weight x 1.7 is the force pulling the character down if in air.

btw: im trying my best to document every aspect of the game, for training and for easier understanding of how to make content for the game

[A-Man]

weight defines the weight of the character. lf2 has a gravity force of 1.7, so the weight x 1.7 is the force pulling the character down if in air.

But the gravitational acceleration has got nothing to do with an object's mass; all objects, irrespective of their masses/weights, should fall at the same rate/acceleration.
That is better renamed "inertia" or something like that if you don't want stuff to sound too scientific. That can be the character's resistance to the change in velocity; ie: a character with more inertia fly less high when knocked and vice versa.

Edit: Also don't you think it would be better if you make the armor frame specific? Maybe add these tags to the bdy frame component.

[Bamboori]

oh woops, forgot to post that here

and for each frame you can specify if the armour is present or not (also possible combined with condition, so that means you can make a put-on-armour move for a char)
i think the bdefend being the value decreasing the armour hp makes the most sense. what do you think?

so inertia instead of weight? sure thing! i think though this will suffice for weight related coding, ie a heavy character like mark or monk would have less inertia than rudolf or jan.