EventScripts Each Tag has the option to have Tag Event Scripts on it. When you edit a Tag, you can navigate to the Tag Events screen to see a list of all of the Tag scripts.
|Login • Register|
A Nice Match to play 5 vs 5
Version: 1.2 +ES
Version: By Nicolas
Author : Exploit-Configs
haddz ' 97
Version: 1.1 Faltan Cosas
Double Domination is an Unreal Tournament game mode where the main objective is to capture 2 points and hold them for a specific amount of time. The mode can be played on every map, features announcers (4 UT announcers included) and custom HUD info.
Simple adverts/rules for your server. Easy to configurate and comes with different colors. You can also add your own colors.
Assassination is an old Counter-Strike gamemode where the main objective is to escort the 'VIP' to the escape zone. Terrorists have to prevent this by assassinating the VIP. Works on every map!
Hitmarkers + Hitsounds similar to Quake 3 / CoD. You can use different files to distinguish between normal hits and headshots (built-in hitmarkers are white for normal hits and red for headshots). Every player can set their own preferences and save them.
Tracks how long any map on your server has been played and how often.
Advertise on player disconnect.
This is my server model that I use for LAN gaming and TESTING. ENJOY!!!
This addon gives players the ability to throw their knifes a specific amount of time. Damage done by the knife, sound, rotation of the blade, its color and other settings can easily be configured.
This addon gives players the ability to give a feedback on the server (or maps/admins/etc.). The messages are then stored in a text file on your server (with player, steamid and the time sent)
This addon shows the damage done to a player and (if enabled) their name in one or more of the 4 specified areas.
This addon lets you display adverts in the top-left area. Choose a seperate color for each advert out of a big color palette. Adverts can even be added through the console as well as deleted.
This addon drops a healthkit whenever a player dies at the death location. By touching it the healthkit disappears and gives this player a specified amount of health.
This addon lets any player join to spectators through one of the chosen chat commands. If specified the spectator will not be able to join back until the specified time has passed. This remaining time can be displayed in different areas.
NoTouch has different 'hooks' that can be used to attach custom program code at certain events. This is about advanced customization scenarios and not used in day-to-day operation. You may define your own scripts or copy/paste commands that you got from third parties or Ncomputing support. While absolutely no Linux know-how is necessary in regular NoTouch operation, this is the way to go to the Linux OS level and fully use its power. Most likely, if you install 3rd party applications on your own you will find these event scripts handy as well.
Boot-up event scripts
The boot-up event scripts are found in 'All' and then 'Event scripts'. It is so rarely used that there is no top-level link in the local configuration application, that's why you need to click on 'All' first. In NoTouch Center however, these parameters are merged into the 'Administration' tab.
Eventscriptsexamples07.zip - 2011-04-03 10:40:13; Build Archives. EventScripts 2.1 Branch. EventScripts v2.1.1 Beta Release. This version has been updated for Counter-Strike: Source, L4D, L4D2, and OrangeBox. Read the Release Notes. System Plugin v0.5. Mattie's System Plugin is a Source add-on that exposes a system command that lets you run operating system executables from your Valve console. New EventScripts Classic engine (ESC alpha) is now the default engine for L4D and L4D2; Adding version resource for Windows DLLs - you can now check the DLL for its version instead of needing to load it; Added support for auto-setting the IP variable to workaround the Valve 'wait' problem, set eventscriptssetipcmdline to 0 in eventscripts.
The parameters are structured according to the point they are executed in the boot process:
- Startup 0 - before hotplug service. This executed at the earlierst possible moment. Devices, neither internal nor peripherals, are yet initialized.
- Startup 1 - before network initialization. Right before starting to initialize the network, but after initializing devices and loading drivers.
- Startup 2 - with networking. At this point the system should be on the network and have an IP address.
- Startup 3 - after local services. This is run when local services such as the SSH service (if activated), the NTP service (if activated), the administration tool etc are running.
- Startup 4 - at GUI/X11 start. This command is special because it will block the NoTouch execution - it is executed during the GUI subsystem (X11 server) start.
Note - if not explicitly mentioned, commands will not block execution. That makes sure the system will boot up, but it may lead to race conditions (i.e. you believing your command should do something but in fact a NoTouch-internal routine could be faster and disturb your command).
Connection-specific event scripts
You can also define scripts or commands that are executed on connection-specific events, such as starting a connection. Please see Connection#customization hooks for more information.
X Server event scripts
To put custom code into the execution of the X server (=the low-level GUI subsystem), please see X11#Customization hooks. Pdf converter master.
Network-related event scripts
To run custom code based on network interface up/down events, please see Interface configuration#Event scripts.