Talk:Hint nodes

I'm in the process of re-writing this with the help of the source code and I just stumbled on this snippet:

// TF2 Hints
HINT_BUG_PATROL_POINT = 800,

Interesting... --TomEdwards 05:08, 5 Aug 2005 (PDT)

Bug, like a bug from Starship Troopers? --King2500 05:31, 5 Aug 2005 (PDT)

Just finished combing the source code and from the looks of it, TF2 might actually take place in the HL2 universe. If that's true 'bug' may mean Antlion.

I've got a huge forum thread written up with all of the information I've found, but I'm not too sure Valve would be happy if I posted it! --TomEdwards 06:14, 5 Aug 2005 (PDT)

Ah, go on... --Cargo Cult 06:59, 5 Aug 2005 (PDT)

Do it yourself, search within the SDK source files for 'tf2'. ;-) --TomEdwards 07:03, 5 Aug 2005 (PDT)

OK, I talked to Jay and got the go ahead. It's here. --TomEdwards 02:28, 10 Aug 2005 (PDT)

Of course, after 2 years, the thread has been removed, and TF2 has been released. --Andreasen 08:02, 24 Oct 2007 (PDT)

info_node_climb?

What about the info_node_climb entity? It has all the properties of a hint node. I'm not completely sure, but unless someone who has an understanding of it says otherwaise, I'm thinking it should be included in the list of hint nodes. --Andreasen 08:21, 4 Apr 2006 (PDT)

Yeah that certainly looks like another hybrid nodegraph & hint node, along with info_node_hint & info_node_air_hint. --Beeswax 13:15, 2 Mar 2008 (PST)

CSS

Does CSS use this for the bots, or does the bot nav graph override it? Thelonesoldier 22:58, 4 Feb 2007 (PST)

No, Css uses it's own bot system; though hostages uses the good ol' info_node. But I'm unsure whenever they uses info_node_hint. --Sortie 06:16, 5 Feb 2007 (PST)

Bots do not need any entities everytihng generated autmoatically, but hostages do need node pathing--Angry Beaver 10:03, 5 Feb 2007 (PST)

Sure about that? --TomEdwards 10:32, 5 Feb 2007 (PST)

That confirms what I said bots uses NAV and NPCs use AIN, when I said "Generated Automatically" I meant by running the commands mentioned there. Most of that article is on tweaking the automatic generation. --Angry Beaver 13:33, 6 Feb 2007 (PST)

Mixing discussion pages

I don't understand why, but Talk:info_hint used to redirect here, so if you see anything on this page that is about the info_hint entity only, please move it there to avoid confusion. What's more weird is that history says I'm the one who did the redirect. --Andreasen 06:13, 24 Oct 2007 (PDT)

I've done the opposite Andreasen ;-). Rather than leaving info_hint out in the cold, I've brought it in because it shares much of the functionality explained so well in this article. I did consider going even further in refactoring this page:

• move the Hint Type table to its own page, possibly as a template : Hint Types ?

• move (create) the Hint Group section to it's own page/template : Hint Groups ?

• move (create) most of the useful information to a new hub/overview page : Hint System ?

• reduce this page to a list of all 4 true (hybrid) hint nodes ?

Beeswax 16:48, 2 Mar 2008 (PST)

Hint types are missing

A number of hint types are missing from the list. (Just compare it with the list at info_hint.) Is there some reason behind this, or can the missing types be filled in without complaints? --Andreasen 06:27, 24 Oct 2007 (PDT)

Crouch Cover Low

If Crouch Cover Medium is for covers of 100 units, how high covers are Crouch Cover Low for? --Andreasen 09:00, 24 Oct 2007 (PDT)

Convergeant Evolution ?

It would appear that Valve are moving toward a set of node/hint hybrid entities? For example, by setting the hint-type to 0 (None) on an info_node_hint or info_node_air_hint we achieve the same effect as an info_node or info_air_node respectively. By creating an "Omit from Nodegraph" flag for HintNode entities, the info_hint would not be necessary either. That would leave us with :

• info_node_hint
• info_node_climb
• info_node_air_hint
• info_node_link
• info_node_link_controller

which leaves more room for an info_node_swim_hint ;-) --Beeswax 16:37, 2 Mar 2008 (PST)