Skip to content
TheChatArchiveThe Chat Archive
Qwenqwq-32b· Alibaba (Qwen)Hugging Face LMArena Human Preference 140K

is the humanoid a parent of humanoidrootpart or just in the same model?

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Kimikimi-k2-0711-preview’s answer.
  1. User

    is the humanoid a parent of humanoidrootpart or just in the same model?

  2. Qwen Assistant

    Great question! In Roblox, the Humanoid and HumanoidRootPart are siblings within the same model, not parent/child. Here's how it works:


    Model Hierarchy Explained

    A properly structured enemy model should look like this in the Explorer:

    [Enemy Model]
    ├── Humanoid (script-controlled character logic)
    ├── HumanoidRootPart (the part that defines the model's position and movement)
    ├── [Optional parts like Arms, Torso, etc.]
    

    Key Points:

    1. Humanoid is a child of the model, not the parent of HumanoidRootPart.
    2. HumanoidRootPart must be the PrimaryPart of the model.
      • This tells Roblox where to position the model when it’s cloned or moved.
      • To set it: Select the model → go to its Properties → set PrimaryPart to HumanoidRootPart.

    Why This Matters

    • If your Humanoid or HumanoidRootPart are nested inside another part (e.g., under a "Torso" part), your enemy might not spawn correctly or move properly.
    • The Humanoid needs to be a direct child of the model to control the character’s movement and health.

    How to Fix/Verify in Roblox Studio

    1. Open your enemy model in the Explorer (in ReplicatedStorage/Enemies).
    2. Ensure the hierarchy looks like this:
      [Enemy Model]
      ├── Humanoid
      └── HumanoidRootPart
          └── [Optional other parts like "Head", "Torso", etc.]
      
    3. Set PrimaryPart:
      • Select the model (not the HumanoidRootPart).
      • In the Properties window, scroll to PrimaryPart → click the dropdown → select HumanoidRootPart.

    Common Mistakes

    • Nested Parts:
      If your model has a structure like:

      [Enemy Model]
          └── Torso
              ├── Humanoid
              └── HumanoidRootPart
      

      This is incorrect. The Humanoid and HumanoidRootPart need to be direct children of the model, not nested inside another part.

    • Missing Humanoid:
      If your model lacks a Humanoid, enemies won’t move, take damage, or die properly. Add one via Insert Object → Humanoid.


    Example of a Properly Structured Enemy Model

    Here’s what a basic enemy model might look like in the Explorer:

    [Zombie]
    ├── Humanoid
    │   └── (Properties like MaxHealth, WalkSpeed, etc.)
    ├── HumanoidRootPart
    │   └── (Position, size, transparency, etc.)
    ├── Torso
    ├── Head
    └── [Arms, Legs, etc.]
    

    Quick Checklist for Your Models

    1. Does the model have a Humanoid and HumanoidRootPart?
    2. Are both Humanoid and HumanoidRootPart direct children of the model (not nested inside another part)?
    3. Is PrimaryPart set to HumanoidRootPart?
    4. Does the HumanoidRootPart have a reasonable size/position (so enemies spawn correctly)?

    If your models aren’t structured this way, your enemies might not spawn, move, or behave as expected. Fix the hierarchy first, and your scripts should work smoothly! Let me know if you need help troubleshooting. 😊

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