Skip to content
TheChatArchiveThe Chat Archive
Amazon Novaamazon.nova-pro-v1:0· AmazonHugging Face LMArena Human Preference 140K

Can you make a pathfinding system for a monster that goes is going from one node to the…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-235b-a22b-no-thinking’s answer.
  1. User

    Can you make a pathfinding system for a monster that goes is going from one node to the closest one without repeating the previous one and randomly leaving an ability in this case you can just leave it as a print statement in roblox studio?

  2. Amazon Nova Assistant

    Certainly! Below is a simplified example of a pathfinding system for a monster in Roblox Studio. This system will allow the monster to move from one node to the closest available node without repeating the previous one and randomly leave an ability (represented as a print statement).

    Here's a basic implementation:

    1. Setup the Nodes: Create a series of nodes (parts) in your Roblox workspace that the monster can move between.

    2. Script the Monster: Create a script to handle the pathfinding and ability leaving.

    Step 1: Setup Nodes

    Place several parts in your workspace and name them Node1, Node2, Node3, etc.

    Step 2: Script the Monster

    Create a Script inside the monster model or a separate Script in ServerScriptService.

    -- Monster Script
    local monster = script.Parent
    local nodes = workspace:GetChildren() -- Assuming all nodes are direct children of the workspace
    
    -- Filter to get only parts named "NodeX"
    local nodeList = {}
    for _, node in ipairs(nodes) do
        if node:IsA("Part") and node.Name:sub(1, 4) == "Node" then
            table.insert(nodeList, node)
        end
    end
    
    -- Function to find the closest node
    local function findClosestNode(currentNode)
        local closestNode = nil
        local closestDistance = math.huge
    
        for _, node in ipairs(nodeList) do
            if node ~= currentNode then
                local distance = (node.Position - currentNode.Position).magnitude
                if distance < closestDistance then
                    closestDistance = distance
                    closestNode = node
                end
            end
        end
    
        return closestNode
    end
    
    -- Function to move the monster to a node
    local function moveToNode(targetNode)
        local pathfindingService = game:GetService("PathfindingService")
        local path = pathfindingService:FindPathAsync(monster.PrimaryPart.Position, targetNode.Position)
    
        if path and path:GetWaypoints() then
            local waypoints = path:GetWaypoints()
            for _, waypoint in ipairs(waypoints) do
                monster:MoveTo(waypoint.Position)
                monster.MoveToFinished:Wait()
            end
        end
    end
    
    -- Main loop
    local currentNode = nil
    local previousNode = nil
    
    while true do
        if currentNode then
            previousNode = currentNode
        end
    
        currentNode = findClosestNode(currentNode)
    
        if currentNode then
            moveToNode(currentNode)
            
            -- Randomly leave an ability
            if math.random() < 0.3 then -- 30% chance to leave an ability
                print("Ability left at", currentNode.Position)
            end
        end
    
        wait(1) -- Adjust the wait time as needed
    end
    

    Explanation:

    1. Node Setup: The script collects all parts in the workspace named "NodeX" and stores them in nodeList.
    2. Closest Node Function: findClosestNode calculates the closest node to the current node, excluding the previous node.
    3. Move to Node Function: moveToNode uses Roblox’s PathfindingService to find a path to the target node and moves the monster along that path.
    4. Main Loop: The script continuously finds the closest node, moves the monster to it, and randomly prints an "Ability left" message with a 30% chance.

    Notes:

    • Ensure your monster has a PrimaryPart set for pathfinding to work correctly.
    • Adjust the wait time in the main loop to control the frequency of node changes.
    • You can expand this script to include more complex behaviors and interactions.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.