hey again :) I do use macros now for constant values, but I believe I used them back then too for things like grid_width, etc. But in the example you gave I wouldn't have used macros for that. if the aim_look_ahead variable was supposed to change or be able to change, I really wouldnt make it a macro, same way you dont use a macro for default_player_move_speed uknow, cause it's just used in one object. macros are practical for things that will be used in more than one object like the view size if its not ajustable, the grid size as i said... if you have a value that wont change but is just used by an object, you should just have it as an instance variable. Now in GM 2 there are variable declarations outside the create event, which make it easy to change these kinda values without searching inside code.