Talk:Client Command by Trigger proximity: Difference between revisions
Jump to navigation
Jump to search
TomEdwards (talk | contribs) No edit summary |
CrabbyData (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
<blockquote>Can someone make the image and the table play nice, please?</blockquote> | <blockquote>Can someone make the image and the table play nice, please?</blockquote> | ||
This will need someone with better Wiki knowledge than me to edit [[Template:Entity-kvalue-start]], making <code>clear:both</code> optional, but default. --[[user:TomEdwards|TomEdwards]] 11:24, 14 May 2006 (PDT) | This will need someone with better Wiki knowledge than me to edit [[Template:Entity-kvalue-start]], making <code>clear:both</code> optional, but default. --[[user:TomEdwards|TomEdwards]] 11:24, 14 May 2006 (PDT) | ||
:I added another image (they both are mine if you wondered). I cleaned it up by (dirty) HTML. I could get the properties right for the td's (table data), like valign, align etc. I think it is best to leave it like this, since I looks nice, and shouldn't be a problem... | |||
:I also added/altered the way of the trigger_proximity-position. The best is to put it on such a high place, that a normal jumping player can't touch it, and put the player spawn so, that it DOES touch it on it's spawn. The other way is to delete the trigger_proximity box by a ''logic_auto''. The last one is described in the tutorial. --[[User:CrabbyData|CrabbyData]] 12:34, 14 May 2006 (PDT) |
Revision as of 12:34, 14 May 2006
Can someone make the image and the table play nice, please?
This will need someone with better Wiki knowledge than me to edit Template:Entity-kvalue-start, making clear:both
optional, but default. --TomEdwards 11:24, 14 May 2006 (PDT)
- I added another image (they both are mine if you wondered). I cleaned it up by (dirty) HTML. I could get the properties right for the td's (table data), like valign, align etc. I think it is best to leave it like this, since I looks nice, and shouldn't be a problem...
- I also added/altered the way of the trigger_proximity-position. The best is to put it on such a high place, that a normal jumping player can't touch it, and put the player spawn so, that it DOES touch it on it's spawn. The other way is to delete the trigger_proximity box by a logic_auto. The last one is described in the tutorial. --CrabbyData 12:34, 14 May 2006 (PDT)