I'm having trouble using minihud's crosshair in Ell's HUD.

I've already successfully integrated it into KNHUD as shown here:

http://i.imgur.com/afFm0c8.jpg?1

The HUD crosshair in question (goes in HudPlayerHealth.res):

 "PlayerStatusHealthHline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusHealthHline"
	"xpos"			"c-20"
	"ypos"			"c"
	"zpos"			"10"
	"wide"			"40"
	"tall"			"1"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lWhite"
  }
  "PlayerStatusHealthVline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusHealthVline"
	"xpos"			"c"
	"ypos"			"c-20"
	"zpos"			"10"
	"wide"			"1"
	"tall"			"40"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lWhite"
  }
  "PlayerStatusLowHealthHline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusLowHealthHline"
	"xpos"			"c-20"
	"ypos"			"c"
	"zpos"			"10"
	"wide"			"40"
	"tall"			"1"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lPink"
	"alpha"			"0"
  }
  "PlayerStatusLowHealthVline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusLowHealthVline"
	"xpos"			"c"
	"ypos"			"c-20"
	"zpos"			"10"
	"wide"			"1"
	"tall"			"40"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lPink"
	"alpha"			"0"
  }
  "PlayerStatusBuffHealthHline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusBuffHealthHline"
	"xpos"			"c-20"
	"ypos"			"c"
	"zpos"			"10"
	"wide"			"40"
	"tall"			"1"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lGreen"
	"alpha"			"0"
  }
  "PlayerStatusBuffHealthVline"
  {
	"controlName"	"ImagePanel"
	"fieldName"		"PlayerStatusBuffHealthVline"
	"xpos"			"c"
	"ypos"			"c-20"
	"zpos"			"10"
	"wide"			"1"
	"tall"			"40"
	"visible"		"1"
	"enabled"		"1"
	"fillcolor"		"lGreen"
	"alpha"			"0"
  }

Basically, it is 6 perpendicular lines, 2 for each health status (low, normal, buffed), which appear based on these lines in hudanimations.txt:

//Health Bonus Pulse
event HudHealthBonusPulse
{
	Animate PlayerStatusHealthHline		alpha		"0"				Linear 0.0 0.0
	Animate PlayerStatusBuffHealthHline	alpha		"255"			Linear 0.0 0.0
	Animate PlayerStatusHealthVline		alpha		"0"				Linear 0.0 0.0
	Animate PlayerStatusBuffHealthVline	alpha		"255"			Linear 0.0 0.0
}

event HudHealthBonusPulseStop
{
	Animate PlayerStatusHealthHline		alpha		"255"			Linear 0.0 0.001
	Animate PlayerStatusBuffHealthHline	alpha		"0"				Linear 0.0 0.001
	Animate PlayerStatusHealthVline		alpha		"255"			Linear 0.0 0.001
	Animate PlayerStatusBuffHealthVline	alpha		"0"				Linear 0.0 0.001
}

//===========================================

//Health Dying Pulse
event HudHealthDyingPulse
{
	Animate PlayerStatusHealthHline		alpha		"0"				Linear 0.0 0.0
	Animate PlayerStatusLowHealthHline	alpha		"255"			Linear 0.0 0.0
	Animate PlayerStatusHealthVline		alpha		"0"				Linear 0.0 0.0
	Animate PlayerStatusLowHealthVline	alpha		"255"			Linear 0.0 0.0
}

event HudHealthDyingPulseStop
{
	Animate PlayerStatusHealthHline		alpha		"255"			Linear 0.0 0.001
	Animate PlayerStatusLowHealthHline	alpha		"0"				Linear 0.0 0.001
	Animate PlayerStatusHealthVline		alpha		"255"			Linear 0.0 0.001
	Animate PlayerStatusLowHealthVline	alpha		"0"				Linear 0.0 0.001
}

When trying to use this with Ell's HUD, the lines do not appear anywhere on the screen. I have tried changing the zpos, xpos, wide and tall values, but nothing has worked.

I can get the lines to appear with the code posted above pasted into hudlayout.res; however, they do not change color based on health status (if we could work that out instead, then it'd be fine with me). This leads me to believe it's not the position values, but something else that I'm unaware of.

I've checked thoroughly for formatting and spelling mistakes.

Keep in mind that if you disguise as a class the enemy team doesn't have, all the weapons your disguise will have will be stock weapons; if any of the weapons are not stock or are renamed, the enemy team has that class out.

Pretty sure, anyway.

As Ben said, only a few would be considered cheating. The idea is that most scripts are not really useful because you would get better results/more control with manual skill (duck-jump, null-movement cancelling, etc.). There are a few things that you can't do nearly as fast/painlessly without binds and scripts such as crosshair/weapon slot customizations or loadout switchers, but none of these are going to improve your gameplay by substantial amounts.

Just do what you're comfortable with.

Please try to stay on the topic of the thread, or be more constructive as to which scripts he shouldn't use and why, even if it is all of them.

TF2mate is an easy way to make your own simple binds; particularly of note is the class & weapon slot customizer.

Null-cancelling movement script (prevents your character from not moving due to pressing opposing movement keys):

// Null-Cancelling Movement Script

bind w +mfwd
bind s +mback
bind a +mleft
bind d +mright

alias +mfwd "-back;+forward;alias checkfwd +forward"
alias +mback "-forward;+back;alias checkback +back"
alias +mleft "-moveright;+moveleft;alias checkleft +moveleft"
alias +mright "-moveleft;+moveright;alias checkright +moveright"
alias -mfwd "-forward;checkback;alias checkfwd none"
alias -mback "-back;checkfwd;alias checkback none"
alias -mleft "-moveleft;checkright;alias checkleft none"
alias -mright "-moveright;checkleft;alias checkright none"
alias checkfwd none
alias checkback none
alias checkleft none
alias checkright none
alias none ""

(Only practical on Scout, not necessarily beneficial; also not shown, but my version causes the crosshair to change colors whenever a wasd key is pressed)

Duck-jump script:

// Duck-Jump Script

alias +dj "+duck;+jump"
alias -dj "-jump;-duck"
bind mouse2 +dj

Viewmodel toggle script:

// Viewmodel Toggle

bind mouse3 viewtoggle
alias viewtoggle viewoff
alias viewon "r_drawviewmodel 1;alias viewtoggle viewoff"
alias viewoff "r_drawviewmodel 0;alias viewtoggle viewon"

Zoom script (decreases FOV like a miniature scope, and slightly lowers sensitivity):

// Zoom Script

bind r zoomtoggle
alias zoomtoggle zoomoff
alias zoomon "sensitivity [LOWER SENS HERE];fov_desired 75;alias zoomtoggle zoomoff"
alias zoomoff "sensitivity [NORMAL SENS HERE];fov_desired 90;alias zoomtoggle zoomon"

Autocall script (causes health crosses to flash above all teammates, regardless of current health):

// Autocall Script

alias autocall_initial "hud_medicautocallersthreshold "50""
alias autocall_temp "hud_medicautocallersthreshold "150""
alias +autocall_temp_hit "autocall_temp"
alias -autocall_temp_hit "autocall_initial"
bind e +autocall_temp_hit

Spawn change script (toggles between loadout A and loadout B; double-pressing the key allows you to quickly access the resupply and/or change spawns when applicable; this script in particular does not require a class change, and allows medics to keep their ubercharge percentage; that requires the same medigun in both loadouts A and B, with at least one item different between them):

// Spawn Change/Resupply Script

alias movespawn_first "load_itempreset 1;alias movespawn_third movespawn_second"
alias movespawn_second "load_itempreset 0;alias movespawn_third movespawn_first"
alias movespawn_third movespawn_first
bind f3 movespawn_third

Charge-Turning Script (involves an external program to emulate a controller).

For the most part, you implement these scripts just as you would pre-Steampipe; that is, they go in steamapps/common/Team Fortress 2/tf/custom/[whatever]/cfg, where there should be each class's config files in addition to some others. You can pick and choose what classes you want the scripts to apply to by pasting the scripts in their respective classes' .cfg files, but keep in mind that any binds in these .cfg files will be stored in tf/cfg/config.cfg and will carry over onto other classes unless the keys are rebinded/unbinded. For example, you probably don't want the duck-jump script to occupy your mouse2 on a class like Demoman, so you would paste the duck-jump script in cout.cfg and put bind mouse2 +attack2;spec_prev in your other class configs (although you might as well rebind duck-jump to space if you actually use it).

YMMV when using any scripts.

This is probably not really what you want, but this script lets you preserve uber % while changing spawns (technically also lets you change between two loadouts; if you press it twice it should give you a quick resup with the loadout you had previously, along with any spawn changing that would apply):

alias "movespawn_first" "load_itempreset 1; alias "movespawn_third" "movespawn_second""
alias "movespawn_second" "load_itempreset 0; alias "movespawn_third" "movespawn_first""
alias "movespawn_third" "movespawn_first"
bind "f2" "movespawn_third"

To preserve uber, you have to have the same medigun in loadout A and loadout B, with at least one of the other weapon slots different, and ’automatically respawn after loadout changes’ checked in advanced options.

(Taken from Phoenix's Medic.cfg)

You actually are able to bypass the warning. You have to click "Advanced", and then "Proceed at your own risk."

EDIT: ninja'd so hard.

Pretty much this. Cloak and Dagger/Dead Ringer/Ambassador are other viable options for spies, and that's about it.

Go to the Processes tab in the Task Manager, right click hl2.exe, Set Priority to High, if it's not already there.