GMPlatformerTemplate

GameMaker template comprised of good code (shaun spalding tutorials) and my code

READ THIS

OKAY IMMA SAY THIS NOW YOU NEED INPUT 5 FOR THIS TO BUILD. THERE ARE TOO MANY FILES FOR GITHUB COMMITS SO UHH L

Get it here + documentation

IF YOU DONT KNOW HOW TO IMPORT IT JUST UHH DRAG IN OVER THE WINDOW

AND THEN FIND __input_config_profiles_and_default_bindings (Input > Configuration) AND REPLACE THAT FILE WITH THIS:

//Input defines the default profiles as a macro called 
//This macro is parsed when Input boots up and provides the baseline bindings for your game
//
//  Please edit this macro to meet the needs of your game!
//
//The root struct called INPUT_DEFAULT_PROFILES contains the names of each default profile
//Default profiles then contain the names of verbs. Each verb should be given a binding that is
//appropriate for the profile. You can create bindings by calling one of the input_binding_*()
//functions, such as input_binding_key() for keyboard keys and input_binding_mouse() for
//mouse buttons

INPUT_DEFAULT_PROFILES = {
    
    keyboard_and_mouse:
    {
        left:  [input_binding_key(vk_left),  input_binding_key("A")],
        right: [input_binding_key(vk_right), input_binding_key("D")],
		    down: [input_binding_key(vk_down), input_binding_key("S")],
        
        accept:  [input_binding_key(vk_enter), input_binding_key("Z")],
        cancel:  [input_binding_key(vk_shift), input_binding_key("X")],
        action:  [input_binding_key(vk_enter), input_binding_key("Z")],
		
		    jump:  [input_binding_key(vk_space), input_binding_key("W"), input_binding_key(vk_up)],
        
        pause: input_binding_key(vk_escape),
    },
    
    gamepad:
    {
        up:    [input_binding_gamepad_axis(gp_axislv, true),  input_binding_gamepad_button(gp_padu)],
        down:  [input_binding_gamepad_axis(gp_axislv, false), input_binding_gamepad_button(gp_padd)],
        left:  [input_binding_gamepad_axis(gp_axislh, true),  input_binding_gamepad_button(gp_padl)],
        right: [input_binding_gamepad_axis(gp_axislh, false), input_binding_gamepad_button(gp_padr)],
        
        accept:  input_binding_gamepad_button(gp_face1),
        cancel:  input_binding_gamepad_button(gp_face2),
        action:  input_binding_gamepad_button(gp_face3),
        
        pause: input_binding_gamepad_button(gp_start),
    },
    
};

//Names of the default profiles to use when automatically assigning profiles based on the source that a
//player is currently using. Default profiles for sources that you don't intend to use in your game do
//not need to be defined
#macro INPUT_AUTO_PROFILE_FOR_KEYBOARD     "keyboard_and_mouse"
#macro INPUT_AUTO_PROFILE_FOR_MOUSE        "keyboard_and_mouse"
#macro INPUT_AUTO_PROFILE_FOR_GAMEPAD      "gamepad"
#macro INPUT_AUTO_PROFILE_FOR_MIXED        "mixed"
#macro INPUT_AUTO_PROFILE_FOR_MULTIDEVICE  "multidevice"

//Toggles whether INPUT_KEYBOARD and INPUT_MOUSE should be considered a single source at all times
//For most PC games you'll want to tie the keyboard and mouse together but occasionally having them
//separated out is useful
#macro INPUT_ASSIGN_KEYBOARD_AND_MOUSE_TOGETHER  true

//Whether to allow default profiles (see below) to contain different verbs. Normally every profile
//should contain a reference to every verb, but for complex games this is inconvenient
#macro INPUT_ALLOW_ASSYMMETRIC_DEFAULT_PROFILES  true

Also find the macro INPUT_MAX_ALTERNATE_BINDINGS in __input_config_general and set it to 3 instead of 2