WolfWiki - User contributions [en]

User talk:Fretn

2005-11-16T14:02:38Z

Fretn:

The fifth egg does not work in recent versions so i left it out. Something happens when you do the things to make it happen, but it stays like its value is 0. I Hope, that does not reveal too much ;) --[[User:Deus|Deus]] 05:46, 16 November 2005 (PST)

it's an extra level of difficulty if they want to find the real (working) one :p

Easter egg

2005-11-16T11:14:50Z

Fretn: /* Egg 5 */

==Huh?==
According to various rumours, there seem to be some easter eggs in [[ETPro]].
In the last months there occured single hints for them, which are collected here.
If you found one (or more) don't spoil them by posting it here.

==Egg 1==
Hint 1:<br>http://etpro.poohunter.de/img/eggs/easteregg1.gif
*This easter egg isn't a rumour any longer. It was abused by few players excessively.
Therefor it can be disabled by a serverside cvar.

==Egg 2==
Hint 1:<br>http://etpro.poohunter.de/img/eggs/easteregg2.1.png<br>
Hint 2:<br>http://etpro.poohunter.de/img/eggs/easteregg2.2.jpg

==Egg 3==
*Hint 1: Move like the leet and the leet will be with you ...
*Hint 2: OMFG U R 2 [[31337]] 4 THIS GAEM!1!!1

==Egg 4==
*Hint 1: rain is on fire ...

==Egg 5==
* there was about to be a 5th egg, but the rumours about this are too weak to mention it.
there is a fifth egg, but I'm not sure if it still works in the latest etpro versions, one cookie for he who finds it

User:=FF=im2good4u

2005-11-15T11:12:54Z

Fretn: /* ETPro/Lua libraries, modules and examples */

<table witdh=100% height=100>
<tr><td width=400 align=center valign=center>http://news.bbc.co.uk/olmedia/1750000/images/_1752807_wolfen-activi150.jpg</td><td width=100% align=left valign=center>
== Contact ==
* '''Clan Homepage'''
** ''[http://www.ffclan.net www.ffclan.net]''
* '''Email'''
** ''Hidden
* '''[[IRC]]'''
**''#etpro'' - [[ETPro]] channel on freenode<br>[[irc://irc.freenode.net:6667/etpro]]
**''#etpro'' - [[ETPro]] support channel on quakenet<br>[[irc://irc.quakenet.org:6667/etpro]]
**''#=FF=Clan'' - [[=FF=Clan]] Clan channel on quakenet<br>[[irc://irc.quakenet.org:6667/=FF=Clan]]
</td></tr></table>
==ETPro/Lua libraries, modules and examples==
;Follow the link to the source code for more detailed information about each item.
*[http://home.zonnet.nl/westhof99/lua/advPrint.lua advPrint.lua] A simple et.Printf function that doesnt give an error while printing the value of an a nil variable. NOT YET FINISHED

*[http://home.zonnet.nl/westhof99/lua/DebugLib.lua DebugLib.lua] A lua library that provides a special debug console print. You can choose to use timing if you like and you can set the fuction / subfunctions it shows while printing. and when you want to remove all debug you can do that by modifying one line instead of to remove all debug 1 by 1. NOT YET FINISHED

*[http://home.zonnet.nl/westhof99/lua/ETProStuffPlug.lua ETProStuffPlug.lua] 1 lua mod that hold many handy functions for admis and players. NOT YET FINISHED

Target location

2005-11-07T21:33:16Z

Fretn: /* Loc_show */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that you are currently "in"

====Loc_move====
:Moves the target_location that you are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that you are currently "in" to <message>

====Loc_show====
:Shows the target_location that you are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure you use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:33:01Z

Fretn: /* Loc_rename <message> */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that you are currently "in"

====Loc_move====
:Moves the target_location that you are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that you are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure you use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:32:51Z

Fretn: /* Loc_move */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that you are currently "in"

====Loc_move====
:Moves the target_location that you are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that u are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure you use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:32:37Z

Fretn: /* Loc_del */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that you are currently "in"

====Loc_move====
:Moves the target_location that u are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that u are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure you use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:31:44Z

Fretn: /* Viewing locations */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that u are currently "in"

====Loc_move====
:Moves the target_location that u are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that u are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure you use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:31:29Z

Fretn: /* Viewing locations */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that u are currently "in"

====Loc_move====
:Moves the target_location that u are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that u are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map you are willing to see your progress. This can be done using a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure u use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

Target location

2005-11-07T21:30:44Z

Fretn: /* Vieuwing locations */

== For Maps In Production ==

A ''target_location'' is a non-brush entity that allows a mapper to specify the name of a certain area to be displayed instead of map coordinates in both the fireteam box and the location displayed when you chat, unless it is set to use coordinates on the client side.

Note that using these will throw an error into the console for every one you have if use in etmain, or as of now, shrub and etpub. The map will still run, though. To use them, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.

===Target_location entity===
<pre>
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8)
Set "message" to the name of this location.

The message can contain colorcodes, default color is ^3(yellow)

Closest target_location in sight used for the location, if none
in site, closest in distance, within PVS
*/
</pre>

This will allow you to place a target_location into your map inside of GTK Radiant. It will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place target_locations so you can always see one, any more are a waste of resources.

== For Completed Maps ==

Note: This method is less efficient engine-wise than using actual target_locations.

target_location on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3

When adding target_locations ro a map u will have acces to the following commands:

===Loc_commands===
====loc_add <message>====
:Add a new target_location at your current position whit name <message>

====Loc_del====
:Deletes the target_location that u are currently "in"

====Loc_move====
:Moves the target_location that u are currently "in" to your current position

====Loc_rename <message>====
:Renames the target_location that u are currently "in" to <message>

====Loc_show====
:Shows the target_location that u are currently "in" as text in console

====Loc_save====
:Saves all target_locations to a file (maps/$MAPNAME_loc_override.dat)

====Loc_load====
:Reloads all target_locations from a file (maps/$MAPNAME_loc_override.dat)

==Viewing locations==

While adding locations to your map u are willing to see your progress. This can be done useing a cvar.

<pre>
b_debuglocations - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents.
add the following together:
1 - Draw a bubble sprite at each location marker. The nearest location is drawn in green, with all the others being drawn in red.
2 - Add a dynamic light at each location marker. The nearest location is lit in red, with all the others being lit in green.
4 - Draw floating text at each location marker containing the location's name. The nearest location is colored green instead of white.
8 - Send updates to other players when a location is added, deleted, or renamed. This function is designed to allow several people to work on adding locations to a level simultaneously.
16 - Accept updates to locations from other players who are using b_debuglocations 8.
default: 0 valid values: 0-31
</pre>

NOTE: while using b_debuglocations make sure u use loc_save a lot, this is becase of engine limits the client can crash while drawing to many sprites

User:Fretn

2005-11-03T10:11:59Z

Fretn:

I am fretn without caps !