1. Hey there Guest,

    The game servers have moved to semi-dedicated hardware and IPs have changed. Please see front page server widget for up-to-date game server information.

How do I disable/enable info_player_teamspawn(s)?

Discussion in 'Mapping Questions & Discussion' started by squ1rrel, Jun 20, 2017.

  1. squ1rrel

    squ1rrel L4: Comfortable Member

    Messages:
    158
    Positive Ratings:
    72
    I want Blu to respawn in the forward spawn after they cap A but struggling to figure out how.

    I tried adding outputs on the trigger_capture_area such as: OnCapTeam2, <name of info_player_teamspawn>, Enable/Disable but when testing, I respawned in the original spawn instead of the foward spawn. Am I doing something wrong?
     
  2. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    did you disable the original spawn? that's what usually causes this bug.
     
  3. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    alternatively are you spawns individually named? that can also cause it.
     
  4. squ1rrel

    squ1rrel L4: Comfortable Member

    Messages:
    158
    Positive Ratings:
    72
    The output should have disabled the original info_player_teamspawns and enabled the new one. The original spawns all have the same name. I had the forward spawn as set to start 'disabled' but the output should enable it right? Should the output even be on the trigger_capture_area and do I have to disable the func_respawnroom for the actual spawn points to work too?
     
  5. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    okay, a good forward naming convention is, base, for1 and for2
    so: blu_spawn_base_01 - 12 -> blu_spawn_for1_01 - 12 -> blu_spawn_for2_01 - 12
    the number at the end is there for issues in load order,
    blu_spawn_base // on capture: point X // disable
    blu_spawn_for1 // on capture: point X // enable

    that is the simplest way to break it down. it sounds like tf2 is getting confused on what is happening.

    now onto func_respawn, only disable it for red team if blu takes a nearby room that wasn't used by red., but in reality func_respawnroom is default to general enabled. so you don't need to worry about it.
     
  6. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    has this helped?
     
  7. squ1rrel

    squ1rrel L4: Comfortable Member

    Messages:
    158
    Positive Ratings:
    72
    Just trying to make sense of this (forgive me, I am terrible at logic stuff).
    So what is the "blu_spawn_base_01 - 12 -> blu_spawn_for1_01 - 12 -> blu_spawn_for2_01 - 12" referring to? Are these the names for something? + where/what do I do about the number 12?
    Also, is "blu_spawn_base // on capture: point X // disable" meant to be the output for the trigger_capture_area?

    ps sorry for the late reply and my logic inadequacy
     
  8. squ1rrel

    squ1rrel L4: Comfortable Member

    Messages:
    158
    Positive Ratings:
    72
    After further troubleshooting, it may have been human error that meant the logic wasn't working. Re-did the logic and it now works! The spawns disable and enable properly now.
     
  9. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    okay, for clarity the 01-12 was for how many players are on the team. 24v24 vs 32v32. and I'm glad you got it working!
     
  10. worMatty

    aa worMatty Repacking Evangelist

    Messages:
    1,072
    Positive Ratings:
    836
    Enabling and disabling spawn points is unreliable. Instead, associate spawn points with the ownership of a particular control point entity. You do this by editing the properties of the team_control_point. If you have any 5CP prefabs like the ones distributed with the Source SDK content or ABS's mapping resource pack, have a look at the entities in those to see how it's done.
     
  11. squ1rrel

    squ1rrel L4: Comfortable Member

    Messages:
    158
    Positive Ratings:
    72
    Out of interest, why is it unreliable and I did attempt to use the associated spawn point thing but I didn't understand how to properly do it. Would you care to explain how to use the associated spawnpoint in terms of all the logic etc?
     
  12. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    that was the third thing I forgot.
     
  13. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    cause naming conventions can be tedious and buggy
     
    • Thanks Thanks x 1
    • Respectfully Disagree Respectfully Disagree x 1
  14. worMatty

    aa worMatty Repacking Evangelist

    Messages:
    1,072
    Positive Ratings:
    836
    I played around with it some time ago and found I was still spawning at the original spawn points after I'd disabled them. I don't know why it happens but I think it's caused by the way the game handles spawning.

    I must apologise. The keyvalue for spawn point and CP association is actually in the spawn point's properties. See this example screenshot:

    [​IMG]

    You have to fill in the name of the CP that causes players to spawn in a new place when captured. For example, in a 5CP map, you would associate your first forward spawn points with the mid CP.

    I recommend ABS' mapping resource pack. It has a game mode library VMF that you can study to help you understand how to configure your spawn points and CPs.
     
  15. Muddy

    aa Muddy Muddy

    Messages:
    2,396
    Positive Ratings:
    4,249
    Contrarily, I've never had an issue with manually enabling/disabling spawnpoints, but associating spawn points with control points has never worked properly for me.
     
  16. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    you know, I think theres a million ways to fix an issue, that everyone has their own solution. I use naming conventions to make sure they work proper, but for non dispute points, I use point enable/disable. depends on mode.
     
  17. worMatty

    aa worMatty Repacking Evangelist

    Messages:
    1,072
    Positive Ratings:
    836
    There aren't a million ways to fix a problem. There's usually only one or two.

    I don't understand what relevance 'naming conventions' have to this problem.
     
  18. MoonFox

    MoonFox L10: Glamorous Member

    Messages:
    737
    Positive Ratings:
    72
    not sure either, but that's my solution to the problems of spawn bugs. you know what, I'm going to stop saying things... cause at this point its solved and I'm lacking func_logic.
     
    • Funny Funny x 1