Talk:Ladders: Difference between revisions
(Seeking confirmation about future changes.) |
|||
| Line 11: | Line 11: | ||
~P-bait. | ~P-bait. | ||
---- | |||
I posted this on the VERC forums, but as nobody replied to it, I'm about to do this myself: | |||
"Under "ladders" it sais: "Along with the volume of movement, the ladder also needs "dismount" points (See Fig. 1d). These points are defined using the info_ladderdismount or func_ladderendpoint entity." | |||
...but this must be wrong, because info_ladder_dismount (which is the correct entity name) sais that it is only meant to be used when multiple ladders are too close to eachother, and func_ladderendpoint sais it is obsolete and is there only because of backwards compatability. If you're not using multiple ladders close to eachother, you shouldn't need any other entities than the func_usableladder. | |||
Someone should verify this and update the wiki so making simple ladders isn't as confusing." | |||
If someone has any objections to changing this, let me know. This is my first attempt at editing any wiki and I've barely made a functional ladder myself. If the information about info_ladder_dismount or func_ladderendpoint is wrong, I might just be messing things up, but ladders do work without these entities. (You just have to separate the func_useableladder from any others brushes.) | |||
Revision as of 06:45, 27 January 2006
...Should we strike the CS:S ladder tutorial done by SixThree or is the note I added at the end of it good enough? As is I find it may be somewhat confusing. --wisemx 18:19, 5 Jul 2005 (PDT)
- It seems fine to me. However, articles should not have signatures ("By SixThree") on them. This discourages other users from making changes to the article. If someone is really curious about the author(s) of an article, they can look in the article history. In the same vein, instead of your note at then end about toolsnodraw, you should either a) change the article directly, or b) if you don't have time to make all the changes or are not sure the change is correct, add a note in the Talk page so someone else can make the change. There should not be discussion in the actual page unless it is a stub (unreleased) article. --JeffLane 18:48, 5 Jul 2005 (PDT)
Noted Jeff, thanks ;-) --wisemx 04:55, 6 Jul 2005 (PDT)
Func_latterendpoint
I realized you can use Func_ladderendpoint in the same way was info_ladderdismount
~P-bait.
I posted this on the VERC forums, but as nobody replied to it, I'm about to do this myself:
"Under "ladders" it sais: "Along with the volume of movement, the ladder also needs "dismount" points (See Fig. 1d). These points are defined using the info_ladderdismount or func_ladderendpoint entity."
...but this must be wrong, because info_ladder_dismount (which is the correct entity name) sais that it is only meant to be used when multiple ladders are too close to eachother, and func_ladderendpoint sais it is obsolete and is there only because of backwards compatability. If you're not using multiple ladders close to eachother, you shouldn't need any other entities than the func_usableladder.
Someone should verify this and update the wiki so making simple ladders isn't as confusing."
If someone has any objections to changing this, let me know. This is my first attempt at editing any wiki and I've barely made a functional ladder myself. If the information about info_ladder_dismount or func_ladderendpoint is wrong, I might just be messing things up, but ladders do work without these entities. (You just have to separate the func_useableladder from any others brushes.)