Template:List of item attributes

From Team Fortress Wiki
Revision as of 09:12, 20 March 2011 by WindBOT (talk | contribs) (Updated item attributes)
Jump to: navigation, search

List of Item Attributes/Header <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US">

<head profile="http://gmpg.org/xfn/11"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

<title> Bad Profile Name Errors 2: The Dominatening » The Hidden Log </title>

<link rel="stylesheet" href="http://agg.optf2.com/log/wp-content/themes/decoder/style.css" type="text/css" media="screen" />

<link rel="alternate" type="application/rss+xml" title="RSS Feed" href="http://agg.optf2.com/log/?feed=rss2" /> <link rel="pingback" href="http://agg.optf2.com/log/xmlrpc.php" />

<link rel="stylesheet" type="text/css" href="http://agg.optf2.com/log/wp-content/themes/decoder/lib/superfish.css" media="screen"> <script type="text/javascript" src="http://agg.optf2.com/log/wp-content/themes/decoder/lib/js/jquery-1.2.6.min.js"></script> <script type="text/javascript" src="http://agg.optf2.com/log/wp-content/themes/decoder/lib/js/superfish.js"></script> <script type="text/javascript" src="http://agg.optf2.com/log/wp-content/themes/decoder/lib/js/supersubs.js"></script>

<script type="text/javascript">

   $(document).ready(function(){ 
       $("ul.sf-menu").supersubs({ 
           minWidth:    12,   // minimum width of sub-menus in em units 
           maxWidth:    27,   // maximum width of sub-menus in em units 
           extraWidth:  1     // extra width can ensure lines don't sometimes turn over 
                              // due to slight rounding differences and font-family 
       }).superfish();
   });

</script>

<link rel="alternate" type="application/rss+xml" title="The Hidden Log » Bad Profile Name Errors 2: The Dominatening Comments Feed" href="http://agg.optf2.com/log/?feed=rss2&p=126" /> <script type='text/javascript' src='http://agg.optf2.com/log/wp-includes/js/l10n.js?ver=20101110'></script> <script type='text/javascript' src='http://agg.optf2.com/log/wp-includes/js/comment-reply.js?ver=20090102'></script> <link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://agg.optf2.com/log/xmlrpc.php?rsd" /> <link rel="wlwmanifest" type="application/wlwmanifest+xml" href="http://agg.optf2.com/log/wp-includes/wlwmanifest.xml" /> <link rel='index' title='The Hidden Log' href='http://agg.optf2.com/log' /> <link rel='start' title='Trying Out WP Again For a While' href='http://agg.optf2.com/log/?p=6' /> <link rel='prev' title='Big Update – Part 1' href='http://agg.optf2.com/log/?p=121' /> <link rel='next' title='Loadout Lists, Toolbar Move' href='http://agg.optf2.com/log/?p=131' /> <meta name="generator" content="WordPress 3.1" /> <link rel='canonical' href='http://agg.optf2.com/log/?p=126' />

</head>

<body>


<a href="http://agg.optf2.com/log/?p=126" rel="bookmark" title="Bad Profile Name Errors 2: The Dominatening">Bad Profile Name Errors 2: The Dominatening</a>

The <a title="Bad Profile Name Errors" href="http://agg.optf2.com/log/?p=115">last post</a> was getting too messy so I’ll start a fresh one here. I’ve finally tracked down the causes of those occasional bad profile name errors. OPTF2 is just too much for my host’s servers. Or at least that is what I choose to think since it appears that they are forcing OPTF2 to shut down during higher traffic periods.

What is really happening (and I do not know why I didn’t realize this before) is the host kills OPTF2′s process, a 500 (internal error) occurs, and the user gets redirected to a page called internal_error.html which is intended for use by website admins to show a custom error page, since OPTF2 by default assumes that any unrecognized path is a Steam ID it will try to search for a backpack named internal_error.html, and since this doesn’t exist it shows the “Profile not found” page.

Since this puts a bit of a dent in my plans for future updates and I am no longer confident that anything I can do will keep it running I have three choices:

  1. Pay an extra $100 or so for a VPS, where uptime is guaranteed
  2. Shutdown ALL extra features I’m running, including git tree hosting, this blog, the tracker, and so on. Which even then might not work.
  3. Shutdown OPTF2 entirely and call it a good run

Obviously 3 is out of the question. I’m not about to let down anyone. 2 may delay the problem for a while, until I push the planned features that will put even more of a strain on the server. 1 is the only realistic solution I see to this.

If you got here by attempting to view a backpack in OPTF2 you likely tried during a high traffic hour and ran into the problem above. I apologize for this and am working on a fix. For now try <a href="javascript:history.back()">going back</a> and refreshing a few times.


Saturday, March 5th, 2011 <a href="http://agg.optf2.com/log/?category_name=optf2" title="View all posts in optf2" rel="category">optf2</a>, <a href="http://agg.optf2.com/log/?category_name=projects" title="View all posts in Projects" rel="category">Projects</a>





Leave a Reply


<fieldset id="commentfieldset">

<a rel="nofollow" id="cancel-comment-reply-link" href="/log/?p=126#respond" style="display:none;">Cancel reply</a>

<form action="http://agg.optf2.com/log/wp-comments-post.php" method="post">


<label for="author">Name (required)</label> <input type="text" name="author" id="name" class="text" value="" size="22" tabindex="1" />

<label for="email">Mail (will not be published) (required)</label> <input type="text" name="email" id="email" class="text" value="" size="22" tabindex="2" />

<label for="url">Website</label> <input type="text" name="url" id="website" class="text" value="" size="22" tabindex="3" />


<label for="message">Message</label> <textarea name="comment" id="message" tabindex="4"></textarea>

<input name="submit" type="submit" class="button" tabindex="5" value="Submit" />

<input type='hidden' name='comment_post_ID' value='126' id='comment_post_ID' /> <input type='hidden' name='comment_parent' id='comment_parent' value='0' />

<input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="abbe401176" />

</form>

</fieldset>




<form method="get" action="http://agg.optf2.com/log/"> <input type="text" name="s" id="search" value="enter keyword..." onfocus="if (this.value == 'enter keyword...') {this.value = ;}" onblur="if (this.value == ) {this.value = 'enter keyword...';}" /><input type="submit" id="search-submit" class="submit" name="submit" value="Go" /> </form>



</body> </html> The following table describes the possible attributes of weapons and items as contained in the items_game.txt file. This is the list of item attributes as described to the user, so some attributes will be duplicated if they can both appear as positive or negative (such as a damage bonus/penalty) or if they have several different descriptions ("set_weapon_mode" is used to represent alternate versions of half a dozen different weapons).

This table lists:

  • ID: Internal ID reference of that attribute. Not used directly in this file, but mods may refer to this value.
  • Name: Internal name of this attribute.
  • Description: The text that appears for the user in the weapon's description. "%s1" is replaced with the value of the attribute.
  • Value Type: How the value of this attribute is formatted for display. Possible types are additive (flat value), percentage, additive percentage (for percentages that start from 0% instead of 100%, like chance to slow target) and inverted percentage (a positive "mult_postfiredelay" will be translated to a negative fire rate percentage)
  • Class: This is the attribute's name used by the rest of the items_game.txt document, as in when it defines each weapon's attributes.

List

See also