CoDJumper.com

ekat wrote:thank you very much!
Works fine.. <3

Just a few questions for this script..
Is it possible to get hit indicator?
Is it possible to get a red crosshair?
Is it possible to take away the deagle after level 3 if the person dont have it before?
Are there more changes in radiant then the conncects between trigger and brushmodels?

 
// Place the following line as the first thing inside "main()"
precacheShader("damage_feedback");
 
// Put the following call after "//set up player" - line 144 in my script.
user thread hitmarker();
 
// Put the following lines inside "target_think" after the if statement - line 230
user playlocalsound("MP_hit_alert");
user.hud_damagefeedback.alpha = 1;
user.hud_damagefeedback fadeOverTime(1);
user.hud_damagefeedback.alpha = 0;
 
// Put this function at bottom of script
hitmarker()
{
        if(!isDefined(self.hud_damagefeedback))
        {
                self.hud_damagefeedback = newClientHudElem(self);
                self.hud_damagefeedback.horzAlign = "center";
                self.hud_damagefeedback.vertAlign = "middle";
                self.hud_damagefeedback.x = -12;
                self.hud_damagefeedback.y = -12;
                self.hud_damagefeedback.archived = true;
                self.hud_damagefeedback setShader("damage_feedback", 24, 48);
                self.hud_damagefeedback.alpha = 0;
        }
}

// Add the following after "// Set up player loadout" - line 159
user.lastWeapon = user getCurrentWeapon();
 
// Add this to FIRST if statement - Line 196
// This will remove the weapon on every eventuality fail/pass
user takeWeapon("deserteagle_mp");
user switchToWeapon(user.lastWeapon);

http://s14.directupload.net/images/130425/w9cs3xpj.jpg

Rezil wrote:You can connect any entity to any other entity, select the trigger, then select your brushmodel and press W. They should now be connected.

Rezil wrote:You'll have to use the clipping tool('X' key on your keyboard) to make your trigger look like that. Create the trigger using 1 brush, then clip it properly.

Rezil wrote:Personally I had a lot of trouble trying to make the trigger work when I made it out of multiple brushes.

Drofder2004 wrote:It is perfectly possible and incredibly easy to do.

Drofder2004 wrote:I have attached a map with a very slightly modified version of your script.

ekat wrote:

Drofder2004 wrote:I have attached a map with a very slightly modified version of your script.

What exactly is modified in this version of my map/script?

Drofder2004 wrote:Mostly adjustments were made to ignore parts of your script (secrets)

Drofder2004 wrote:but the main change was "randomint(target.size)" - this allows for more than 4 triggers

Drofder2004 wrote:and obviously my targets rotated instead of moved.

Drofder2004 wrote:Glad you got it working, however there is so much more you can do to improve this

KillerSam wrote:Civilian targets that look almost the same - but it's GG if you shoot one

KillerSam wrote:You could also make it so that you need to get a certain point score with a scoring system

Drofder2004 wrote:You can do various types of target and easily adapt it into the code with very little change.

One easy way of doing this:
For each different style of target, add a KEY:VALUE of "script_noteworthy" and a value of your choosing.
So, if you had a moving target:
Key: script_noteworthy
Value: moving_target

Now, in your code:

Code: Select all

switch(targets[currentTarget].script_noteworthy)
{
        case "right":
                targets[currentTarget] rotateyaw(90, 0.2);
                wait (2 / (user.target_level + 0.3));
                targets[currentTarget] rotateyaw(-90,0.1);
                break;
        case "left":
                targets[currentTarget] rotateyaw(-90, 0.2);
                wait (2 / (user.target_level + 0.3));
                targets[currentTarget] rotateyaw(90,0.1);
                break;
        case "down":
                targets[currentTarget] rotateroll(90, 0.2);
                wait (2 / (user.target_level + 0.3));
                targets[currentTarget] rotateroll(-90,0.1);
                break;
}
wait 1;

The example above uses 3 targets, 2 of the targets pop out from the walls and the third is standard.
You just add your own case and how it reacts. So different wait times, different actions (combine movement maybe?)

Drofder2004 wrote:Generally, mapping could also be improved - such as lighting, textures of target, fx, etc