Below is a cleaned-up version of your script with the most common fixes applied. The main issues in the snippet you posted are:

1. Typo in the function name: use func _process(delta): or func _physics_process(delta):.
2. Typo in “normalized”: it was spelled nornalized().
3. Godot version considerations:
   • In Godot 4, CharacterBody2D has its own built-in velocity property and typically uses move_and_slide().
   • In Godot 3, you’d use KinematicBody2D with a manually defined velocity and call move_and_slide(velocity * delta) inside _physics_process.

Below is an example corrected for Godot 4. If you are still using Godot 3, see the notes at the bottom for how to adapt it.

gdscript
extends CharacterBody2D

var max_speed = 100

func _ready():
    # You can initialize things here if needed
    pass

func _physics_process(delta):
    var direction = get_direction_to_player()
    
    # Scale the direction to max_speed
    velocity = max_speed * direction

    # Move using Godot 4's CharacterBody2D API
    velocity = move_and_slide()

func get_direction_to_player() -> Vector2:
    # Finds the first node in the group "player"
    var player = get_tree().get_first_node_in_group("player") as Node2D
    if player != null:
        # Use 'normalized()' (with a 'd')
        return (player.global_position - global_position).normalized()
    return Vector2.ZERO

If you’re on Godot 3

• Replace CharacterBody2D with KinematicBody2D.
• You’ll often write:

  gdscript
  func _physics_process(delta):
      var direction = get_direction_to_player()
      velocity = max_speed * direction
      velocity = move_and_slide(velocity * delta)

• Keep the spelling fixes (normalized(), _physics_process or _process) as shown above.

Common pitfalls and clarifications

1. Choosing _process(delta) vs _physics_process(delta)

   • Use _process(delta) for purely visual/logic updates.
   • Use _physics_process(delta) if you are dealing with physics-related movement every frame (this ensures it runs in sync with the physics step).

2. Using groups:

   • Make sure your player node is actually added to the group "player" via the Godot editor (or via add_to_group("player") in code). Otherwise, get_tree().get_first_node_in_group("player") will be null.

3. Movement details:

   • In Godot 4, move_and_slide() uses the velocity property of CharacterBody2D automatically. You can optionally add parameters like “up direction” if you need advanced features such as floor detection or gravity.
   • In Godot 3, move_and_slide(velocity * delta, Vector2.UP) is more common for 2D platformers (with gravity).

With these corrections, your script should properly chase the Player node in your scene.