User:Daeval: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
(Blanked the page)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="float:left; background:#FFFACD; padding: 3px; border:1px solid #FFD700; font-family: Tahoma; font-size: x-small; text-align:center">
[http://developer.valvesoftware.com/w/index.php?title=User_talk:Daeval&action=edit&section=new '''LEAVE A NEW MESSAGE''']
</div>{{clr}}


<div style='width: 100%; background:#4682B4; position: relative; top: -8px'>
<div style='position: relative; top: 8px; background:#CFDDF0; border:1px solid #191970; margin: 8px; padding: 8px'>
== Heya, I'm Daeval. == 
A long, long time ago in a galaxy far, far away, I was also Sir Jaster @Ni!. 
I haven't messed with Hammer much since it was called Worldcraft, but I've been starting up again with the release of Team Fortress 2.
</div>
<div style='position: relative; top: 8px; background:#CFDDF0; border:1px solid #191970; margin: 8px; padding: 8px'>
== Works in Progress.. ==
I'm in the process of teaching myself to map for TF2, and I'm creating some "how-to"s as I do it.
I'm looking to make a kind of reference article for each aspect of TF2 mapping, with demo maps that feature only what is talked about in that specific article.  All-inclusive tutorials like the ones here are great, but they are difficult to use if you only need specific information.  In the wiki spirit, I'd like to create standardized, more easily referenced chunks.  With any luck, this might also encourage people to try new things, new combinations - to push the limits of the parts we've been given, as was the spirit of the TF1 mapping community.
Up to now, I've only gotten as far as the tutorials here will take me.  I'm moving forward, but I will wait until I've made significant additions to put/modify links on the main TF2 mapping page.  Meanwhile, I'll add links here. 
I have a bunch as text files and images, I just have to translate them into wiki format.  Also have to find a place to host .vmfs, because I think those would be useful.
Just getting started:
* [[User:Daeval/TF2 How To Create Respawn Areas|How to Create Respawn Areas]]
* [[User:Daeval/TF2 How to Create Team-Specific Barriers|How to Create Team-Specific Barriers]]
* [[User:Daeval/TF2 How to Create Team-Specific Doors|How to Create Team-Specific Doors]]
* [[User:Daeval/TF2 How to Create Resupply Areas|How to Create Resupply Areas]]
* [[User:Daeval/TF2 How To Setup Capture The Flag|How to Setup Capture the Flag]]
</div>
<div style='position: relative; top: 8px; background:#CFDDF0; border:1px solid #191970; margin: 8px; padding: 8px'>
== TF2 Mapping - Feature Requests ==
In my exploration of TF2 mapping, I've come across a few barriers that I'd like to break through.  These are little things that aren't crucial, but would open up different mapping possibilities.  As far as I can tell, these require some (relatively minor) intervention from the developers at Valve.  However, if you know of an existing way to accomplish any of these, please [http://developer.valvesoftware.com/w/index.php?title=User_talk:Daeval&action=edit&section=new let me know]!
* MultiCTF
:A bug currently prevents multiple-flag CTF from working.  A player can pick up multiple [[item_teamflag]]s, but only one of them remains "active."  He will be unable to score with the others, and they will not drop to the ground, even after he dies.  From then on, he will respawn with any extra flags on his back, effectively removing them from the game.
:It seems like this could be solved by either:
::a) Not allowing a player to carry more than one flag.
::b) Allowing a player to return more than one flag at a time and to drop multiple flags upon death.
::c) An [[item_teamflag]] "group" property, such that flags with the same group cannot be carried together.  Similarly, [[func_capturezone]]s might be tied to a flag group.
:Any of these solutions would open up a whole new realm of possibilities for MultiCTF.
* Flag Return Input
: It would be nice if [[item_teamflag]]s had a "return this flag" Input.
* Flag Timeout
: Similarly, [[item_teamflag]]s could have a timeout property, indicating the amount of time before a dropped flag returns.
<!-- COMMENT
* Neutral Flag Skin
: Neutral [[item_teamflag]]s currently appear as the Red briefcase, making them impractical for use in combination with colored flags.  Ideally, neutral flags would have their own skin (black/silver/something).
: [[http://developer.valvesoftware.com/wiki/Image:Item_Flag_tf.JPG This image]] shows a neutral flag as black, but it is unclear how the uploader achieved this.  Can you set the skin to 0 for any?-->
</div>
{{clr}}</div>

Latest revision as of 14:30, 20 November 2013

Retrieved from "https://developer.valvesoftware.com/w/index.php?title=User:Daeval&oldid=177820"