User:Daeval: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
Line 17: Line 17:
I'm looking to make a kind of reference article for each aspect of TF2 mapping.  When I got here, there were a few all-inclusive tutorials, which were great.  However, they are difficult to use if you only need specific information, and are even harder to add to in a logical manner.  In the wiki spirit, I'm in the process of creating more standardized, 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.
I'm looking to make a kind of reference article for each aspect of TF2 mapping.  When I got here, there were a few all-inclusive tutorials, which were great.  However, they are difficult to use if you only need specific information, and are even harder to add to in a logical manner.  In the wiki spirit, I'm in the process of creating more standardized, 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.


Update: I've moved the things I had out of my userspace and into the public domain.  Links can be found on the main [[Team_Fortress_2_Level_Creation]] page.  Other users need to be able to add their own information, etc.  That's how a wiki grows, after all.
Update: I've moved the things I had out of my userspace and into the public domain.  Links can be found on the main [[Team Fortress 2 Level Creation]] page.  Other users need to be able to add their own information, etc.  That's how a wiki grows, after all.
</div>
</div>



Revision as of 03:48, 4 January 2008

LEAVE A NEW MESSAGE

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.

Works in Progress..

I'm looking to make a kind of reference article for each aspect of TF2 mapping. When I got here, there were a few all-inclusive tutorials, which were great. However, they are difficult to use if you only need specific information, and are even harder to add to in a logical manner. In the wiki spirit, I'm in the process of creating more standardized, 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.

Update: I've moved the things I had out of my userspace and into the public domain. Links can be found on the main Team Fortress 2 Level Creation page. Other users need to be able to add their own information, etc. That's how a wiki grows, after all.

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 let me know!

  • MultiCTF
A bug currently prevents multiple-flag CTF from working. A player can pick up multiple item_teamflags, 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_capturezones 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_teamflags had a "return this flag" Input.
  • Flag Timeout
Similarly, item_teamflags could have a timeout property, indicating the amount of time before a dropped flag returns.