kate
-
Posts
3,272 -
Joined
-
Days Won
196
Content Type
Profiles
Forums
Downloads
Gallery
Events
Posts posted by kate
-
-
sorry it is in FrenchWolfenstein: Enemy Territory, version multijoueur sortie en 2003, a été discrètement retiré à la vente sur le Steam allemand.
Malgré ses 19 printemps, Wolfenstein: Enemy Territory jouit encore d’une petite popularité. Fort de sa communauté fidèle, le spin-off multijoueur de Wolfenstein permet de se canarder sur fond de Seconde Guerre Mondiale. Avec la fermeture du launcher Bethesda, le soft a été rapatrié sur Steam. Mais son décor déplaît manifestement aux autorités allemandes.
Wolfenstein se fait bouter hors d’Allemagne
SteamDB signale que Wolfenstein: Enemy Territory ne peut pas être acheté en Allemagne. Aucune annonce officielle n’a commenté cette interdiction de vente. S’il semble toujours possible de l’obtenir gratuitement sur sa page, puisque c’est un free-to-play, il semble bien y avoir volonté (même maladroitement) d’y restreindre l’accès.
Cette histoire de censure n’est que le dernier épisode d’un long bras-de-fer entre l’aïeul du FPS et les autorités germaniques. En effet, les références au nazisme ont longtemps été interdites par la loi outre-Rhin. Une façon, sans doute, de conjurer un éventuel retour de cette idéologie nauséabonde. Cependant, cette loi n’épargne pas les contenus profondément anti-nazis comme Wolfenstein…
Ainsi, le reboot de 2014 Wolfenstein : The New Order a du raser la moustache d’Hitler et gommer toutes les swastikas pour accéder au marché allemand. Cependant, le dernier opus Wolfenstein: Youngblood, paru en 2019, a pu esquiver la case censure grâce à une nouvelle loi de 2018. Dans son cadre, les représentations du nazisme dans un but « éducatif ou artistique » sont autorisées. Là où le bât blesse (peut-être) pour Enemy Territory, c’est qu’il permet techniquement de jouer dans le camp nazi, là où les autres jeux se concentrent sur l’exécution de nazillons à la chaîne. On peut comprendre que ce soit sensible vu l’histoire allemande.
Wolfenstein: Enemy Territory est toujours disponible sur Steam hors-Allemagne. Entièrement gratuit, il propose 6 maps et 5 classes différentes (soldat, médecin, ingénieur, espion, officier). Jusqu’à 32 joueurs peuvent choisir le camp de l’Axe ou des Alliés et se faire des p’tits trous, toujours des p’tits trous à la carabine.
-
i added somes tutos for etpub if this can help you:
https://ets-clan.com/index.php?/forums/forum/15-etpub/
and you still have etpub infos :
-
morning sorry for the late answer
what pub version did u use ?
you have to add the right path for your xp saved
example :set g_XPSaveDirectory "/home/mooney/etpub/xpsave"
same for the omnibots
//Omni Bots
set OmniBot_Path "set g_XPSaveDirectory "/home/mooney/etpub/xpsave"
set OmniBot_Enable "1"
set g_bot_maxXP "1000"
set g_bots_minPlayers "5"
set g_omnibot_flags "0"send me your server cfg i will have a look
BUT FIRST REMOVE THE RCON AND REFEREE PASSWORDS
set rconpassword "xxxxx" // remote console access password
set refereePassword "yyyyy" // referee status password -
-
9 hours ago, PsychoPappy 4 said:
Also disable fireteams for bots, it's pointless to have that enabled for bots.
set FireTeam enabled=0 in your omnibot.cfg
[FireTeam]
enabled = 0our actual for the main
[Debug]
DumpFileEnable = false
DumpFileDialog = false[Script]
LiveUpdate = false[ServerManager]
MaxBots = 18
BalanceTeams = 1
SaveConfigChanges = 1
CountSpectators = 0
SleepBots = 0
MinBots = 0
InitialDelayTime = 2.1[Difficulty]
CurrentDifficulty = 1
AdjustAim = 1[CombatMovement]
moveskill = 3[HeavyWeapons]
MinPlayersForMortar = -1
MinPlayersForMobileMG = -1[Log]
LogInfo = false
LogWarnings = true
LogErrors = true
LogCriticalErrors = true[XP]
Reset = -1
Max = 200000[FireTeam]
enabled = 0[Versus]
BotTeam = -1
HumanTeam = 1
BotsPerHuman = 3-
1
-
-
will try tomorrow
i think our hoster told us also
-
10 hours ago, Bier said:
... and about wanting to balance...
Sometimes I enter the server and there is a perfectly balanced game going on. Me choosing any side will tip the balance, so I feel obliged to stay spec, at least till things change.with !howfair you can still join a team but after will be the other team who will be unfair
-
i will try to modyfy the omnibot file
-
again this recurant problem
guys complain and left ... is the best way to lose regulars
-
[MapScripting Tut] How to create spawn points..
In Theory:-
1)Download or find a map that doesnt have spawnpoints
2)Open its .pk3 file and inside you will find the "map" folder
3)Open the "map" folder you will find the (mapname).script file.
4)Open the (mapname).script file with notepad and u will see something likes this
(The .script file inside the map shows you how the map is controlled or i can say how the map is working and how is it making it run according to the objectives and the teams itself)
- Code: Select all
-
game_manager
{
spawn
{
wm_axis_respawntime 3
wm_allied_respawntime 3
wm_set_round_timelimit 30
wm_set_defending_team 0
wm_setwinner 1
setautospawn "Allies Spawn" 1
setautospawn "Axis Spawn" 1
wait 1000
}
}
-Sometimes some maps with more objectives and stuff have more codes..like this one.
- Code: Select all
-
game_manager
{
spawn
{
wm_axis_respawntime 5
wm_allied_respawntime 5
wm_set_round_timelimit 25
// Stopwatch mode defending team (0=Axis, 1=Allies)
wm_set_defending_team 0
// Winner on clock 0:00 (0=Axis, 1=Allies, -1=Nobody)
wm_setwinner 0
wait 100
setstate sroom_1 default
setstate sroom_2 invisible
setstate sroom_3 invisible
setstate sroom_4 invisible
setstate sroom_s1 default
setstate sroom_s2 invisible
setstate sroom_s3 invisible
setstate sroom_s4 invisible
setstate sroom_teleport invisible
}
}
opener1
{
trigger
{
trigger door1 open
}
}
opener2
{
trigger
{
trigger door2 open
}
}
closer1
{
trigger
{
trigger door1 close
}
}
closer2
{
trigger
{
trigger door2 close
}
}
door1
{
spawn
{
accum 0 set 0 // whether the door is open or closed
}
trigger open
{
accum 0 abort_if_equal 1
stopsound
playsound sound/movers/doors/door2_open.wav
gotomarker door1_down 640
accum 0 set 1
}
trigger close
{
accum 0 abort_if_equal 0
stopsound
gotomarker door1_up 480
accum 0 set 0
}
}
door2
{
spawn
{
accum 0 set 0 // whether the door is open or closed
}
trigger open
{
accum 0 abort_if_equal 1
stopsound
playsound sound/movers/doors/door2_open.wav
gotomarker door2_down 640
accum 0 set 1
}
trigger close
{
accum 0 abort_if_equal 0
stopsound
gotomarker door2_up 480
accum 0 set 0
}
}
sroom_1
{
trigger
{
setstate sroom_1 invisible
setstate sroom_2 default
setstate sroom_s1 invisible
setstate sroom_s2 default
}
}
sroom_2
{
trigger
{
setstate sroom_2 invisible
setstate sroom_3 default
setstate sroom_s2 invisible
setstate sroom_s3 default
}
}
sroom_3
{
trigger
{
setstate sroom_3 invisible
setstate sroom_4 default
setstate sroom_s3 invisible
setstate sroom_s4 default
}
}
sroom_4
{
trigger
{
setstate sroom_4 invisible
setstate sroom_s4 invisible
setstate sroom_teleport default
}
}
sroom_reset
{
trigger
{
setstate sroom_1 default
setstate sroom_2 invisible
setstate sroom_3 invisible
setstate sroom_4 invisible
setstate sroom_s1 default
setstate sroom_s2 invisible
setstate sroom_s3 invisible
setstate sroom_s4 invisible
setstate sroom_teleport invisible
setstate sroom_timer invisible
}
}
5)Somehow if you want to add a spawnpoint, You Should make sure you start adding it after the "Spawn{" Code Like this..
- Code: Select all
-
game_manager
{
spawn
{
create
{
scriptName "allies_obj"
classname "team_WOLF_objective"
targetname "alliesspawn_obj"
origin "-10853 -2036 6"
spawnflags 2
}
6) This is the Main(Starting Code Spawnpoint) For Allies, You must Put this Code at first if you want to start creating a spawnpoint for Allies Team.
- Code: Select all
-
create
{
scriptName "allies_obj"
classname "team_WOLF_objective"
targetname "alliesspawn_obj"
origin "-10853 -2036 6"
spawnflags 2
}
7)After adding the first code for creating spawnpoint for allies, You want to lets say add amount of 5 spawnpoints for allies, so u will put it in this way..
- Code: Select all
-
create
{
scriptName "allies_spawn1"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 384 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn2"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 468 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn3"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4287 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn4"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn5"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 380 72"
spawnflags 2
angle "0"
}
7)So All Together for an allies spawnpoint will look like this,
- Code: Select all
-
game_manager
{
spawn
{
create
{
scriptName "alliesspawn_obj"
classname "team_WOLF_objective"
targetname "alliesspawn_obj"
origin "-4288 384 72"
spawnflags 2
description "Allies Spawn"
}
create
{
scriptName "allies_spawn1"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 384 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn2"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 468 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn3"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4287 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn4"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn5"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 380 72"
spawnflags 2
angle "0"
}
Same For Axis But there will be just difference in their script words like the scriptname,classname and the targetname.
- Code: Select all
-
create
{
scriptName "axisspawn_obj"
classname "team_WOLF_objective"
targetname "axisspawn_obj"
origin "-1408 384 72"
spawnflags 2
}
create
{
scriptName "axis_spawn1"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1408 384 72"
spawnflags 2
angle "-179"
}
create
{
scriptName "axis_spawn2"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 298 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn3"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 479 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn4"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 383 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn5"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 303 72"
spawnflags 2
angle "179"
}
9)So All Together Axis & Allies Spawnpoints together should look like this :-
- Code: Select all
-
game_manager
{
spawn
{
create
{
scriptName "alliesspawn_obj"
classname "team_WOLF_objective"
targetname "alliesspawn_obj"
origin "-4288 384 72"
spawnflags 2
description "Allies Spawn"
}
create
{
scriptName "allies_spawn1"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 384 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn2"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 468 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn3"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4287 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn4"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn5"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 380 72"
spawnflags 2
angle "0"
}
create
{
scriptName "axisspawn_obj"
classname "team_WOLF_objective"
targetname "axisspawn_obj"
origin "-1408 384 72"
spawnflags 2
}
create
{
scriptName "axis_spawn1"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1408 384 72"
spawnflags 2
angle "-179"
}
create
{
scriptName "axis_spawn2"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 298 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn3"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 479 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn4"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 383 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn5"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 303 72"
spawnflags 2
angle "179"
}
10) And now Lets add this code in the map's ".script" (MAPS THAT DOESNT HAVE SPAWNPOINTS)
*It Should look like this after all, Both Allies and Axis have 5 Spawnpoints now*
- Code: Select all
-
game_manager
{
spawn
{
create
{
scriptName "alliesspawn_obj"
classname "team_WOLF_objective"
targetname "alliesspawn_obj"
origin "-4288 384 72"
spawnflags 2
description "Allies Spawn"
}
create
{
scriptName "allies_spawn1"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 384 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn2"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4288 468 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn3"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4287 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn4"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 281 72"
spawnflags 2
angle "0"
}
create
{
scriptName "allies_spawn5"
classname "team_CTF_bluespawn"
targetname "allies_spawn"
origin "-4381 380 72"
spawnflags 2
angle "0"
}
create
{
scriptName "axisspawn_obj"
classname "team_WOLF_objective"
targetname "axisspawn_obj"
origin "-1408 384 72"
spawnflags 2
}
create
{
scriptName "axis_spawn1"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1408 384 72"
spawnflags 2
angle "-179"
}
create
{
scriptName "axis_spawn2"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 298 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn3"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1407 479 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn4"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 383 72"
spawnflags 2
angle "179"
}
create
{
scriptName "axis_spawn5"
classname "team_CTF_redspawn"
targetname "axis_spawn"
origin "-1322 303 72"
spawnflags 2
angle "179"
}
wm_axis_respawntime 5
wm_allied_respawntime 5
wm_set_round_timelimit 25
// Stopwatch mode defending team (0=Axis, 1=Allies)
wm_set_defending_team 0
// Winner on clock 0:00 (0=Axis, 1=Allies, -1=Nobody)
wm_setwinner 0
wait 100
setstate sroom_1 default
setstate sroom_2 invisible
setstate sroom_3 invisible
setstate sroom_4 invisible
setstate sroom_s1 default
setstate sroom_s2 invisible
setstate sroom_s3 invisible
setstate sroom_s4 invisible
setstate sroom_teleport invisible
}
}
opener1
{
trigger
{
trigger door1 open
}
}
opener2
{
trigger
{
trigger door2 open
}
}
closer1
{
trigger
{
trigger door1 close
}
}
closer2
{
trigger
{
trigger door2 close
}
}
door1
{
spawn
{
accum 0 set 0 // whether the door is open or closed
}
trigger open
{
accum 0 abort_if_equal 1
stopsound
playsound sound/movers/doors/door2_open.wav
gotomarker door1_down 640
accum 0 set 1
}
trigger close
{
accum 0 abort_if_equal 0
stopsound
gotomarker door1_up 480
accum 0 set 0
}
}
door2
{
spawn
{
accum 0 set 0 // whether the door is open or closed
}
trigger open
{
accum 0 abort_if_equal 1
stopsound
playsound sound/movers/doors/door2_open.wav
gotomarker door2_down 640
accum 0 set 1
}
trigger close
{
accum 0 abort_if_equal 0
stopsound
gotomarker door2_up 480
accum 0 set 0
}
}
sroom_1
{
trigger
{
setstate sroom_1 invisible
setstate sroom_2 default
setstate sroom_s1 invisible
setstate sroom_s2 default
}
}
sroom_2
{
trigger
{
setstate sroom_2 invisible
setstate sroom_3 default
setstate sroom_s2 invisible
setstate sroom_s3 default
}
}
sroom_3
{
trigger
{
setstate sroom_3 invisible
setstate sroom_4 default
setstate sroom_s3 invisible
setstate sroom_s4 default
}
}
sroom_4
{
trigger
{
setstate sroom_4 invisible
setstate sroom_s4 invisible
setstate sroom_teleport default
}
}
sroom_reset
{
trigger
{
setstate sroom_1 default
setstate sroom_2 invisible
setstate sroom_3 invisible
setstate sroom_4 invisible
setstate sroom_s1 default
setstate sroom_s2 invisible
setstate sroom_s3 invisible
setstate sroom_s4 invisible
setstate sroom_teleport invisible
setstate sroom_timer invisible
}
}
-
-
2022
2022-02-21 20:53:09 ACR: Player ^3Panda! silEnT GUID (AE275262E2DF26FD7EAE454B23487176) IP (71.236.103.14) banned for detected game hack
2022-02-22 02:04:18 ACR: Player medic! silEnT GUID (1D75754E35B3CA55EFE39987657BE844) IP (76.11.50.97) banned for detected game hack
2022-03-03 10:52:43 ACR: Player freedom silEnT GUID (03C0E90890520867329C76D5D56B8F0C) IP (184.163.64.24) banned for detected game hack
2022-03-31 12:00:38 ACR: Player Ronan10th silEnT GUID (DE55BF31DA9079E7B1A07735EA00144B) IP (95.149.17.55) banned for detected game hack
2022-04-27 21:23:21 ACR: Player ETPlayer silEnT GUID (3882FFD42EEF9712EF234DA2F79B0F03) IP (138.122.88.16) banned for detected game hack
2022-05-09 16:24:40 ACR: Player KAMIL silEnT GUID (0C4AF6E73894813F36F792B8315ABD63) IP (178.255.154.180) banned for detected game hack
2022-05-13 12:44:28 ACR: Player footfetish silEnT GUID (D106AFD67D4B8BF60EBF87F2EB368E7B) IP (176.67.86.24) banned for detected game hack
2022-05-12 23:25:49 ACR: Player ^0WEARE^2BORG silEnT GUID (BF71E573AEF146C65AB89F919BAC2A04) IP (119.18.1.127) banned for detected game hack
2022-07-10 23:08:35 ACR: Player DAN DELION silEnT GUID (4C8E2FA6923E3326F2EC40D3A92E5029) IP (64.188.176.97) banned for detected game hack
2022-07-13 20:13:31 ACR: Player blije silEnT GUID (5C78F67BB76BF44AAFF8667D38C49BBC) IP (77.165.255.82) banned for detected game hack
2022-08-02 17:21:58 ACR: Player $p33dy silEnT GUID (CDE5A87074A4B20228E5470B7D2D7F1B) IP (185.157.14.38) banned for detected game hack
2022-10-02 02:38:38 ACR: Player Tom silEnT GUID (D62A659E09C20178670EAFF77F175ABA) IP (95.33.26.238) banned for detected game hack
-
2
-
-
Condump in gaming world means a save of the most recent console lines into a file (condump a file). Condump can be really useful in case when the console contains important data and you want to save it somehow (such as player info or when someone is offended and you want is as a proof, or the list of the players, or !help info or else)
Usage:
/condump et_console_save.txt
Where the "condump" is the command keyword and the text file name is "et_console_save".
Be careful on two things:
1. Never leave an empty space in the filename because it's not gonna work.
(example: et console save.txt or some name.txt)
2. Always use different names or unique names otherwise the newer file will instantly rewrite the older one.
(example: you have an old text file saved previously as etsomefile.txt and you type the same, you loose the old one. So better use a system like: servername_info_playername_001.txt or something similar)
The condump file location:
This saves the text file in the following location if you are in a jaymod server (the mod name changes depending on the type of the server where you are playing at that moment):
C:/Program Files/Enemy Territory/jaymod/et_console_save.txt
or
C:/Program Files/Enemy Territory/silent/et_console_save.txt
After saving the text file, you can go and easily open the file in any text editor program and edit it.
-
1
-
-
wich path ?
-
i just tested and the main serverlist is oki for me
-
lol these new faces via steam is just an epiphenomen and very few guys will stay to play
-
1
-
-
i run ET for my gaming computer with high priority
-
1
-
-
Sysinternals Suite is a bundle of the Sysinternals utilities including Process Explorer, Process Monitor, Sysmon, Autoruns, ProcDump, all of the PsTools, and many more. The Sysinternals website was created in 1996 by Mark Russinovich to host his advanced system utilities and technical information. Whether you’re an IT pro or a developer, you’ll find Sysinternals utilities to help you manage, troubleshoot, and diagnose your Windows systems and applications. The suite includes AccessChk, AccessEnum, ADExplorer, ADInsight, ADRestore, Autologon, Autoruns, BGInfo, CacheSet, ClockRes, Contig, Coreinfo, CPU Stress, DebugView, Desktops, Disk2vhd, DiskExt, DiskMon, DiskView, DU (Disk Usage), EFSDump, FindLinks, Handle, Hex2dec, Junction, ListDLLs, LiveKd, LoadOrder, LogonSessions, MoveFile, NotMyFault, NTFSInfo, PendMoves, PipeList, ProcDump, Process Explorer, Process Monitor, PsExec, PsFile, PsGetSid, PsInfo, PsKill, PsList, PsLoggedOn, PsLogList, PsPasswd, PsPing, PsService, PsShutdown, PsSuspend, RamMap, RDCMan, RegDelNull, Regjump, RU (Registry Usage), SDelete, ShareEnum, ShellRunas, Sigcheck, Streams, Strings, Sync, Sysmon, TCPView, Testlimit, VMMap, VolumeID, WhoIs, WinObj, and ZoomIt.
-
i dont upgraded for windows 11 : ET is not very stable with windows 10 already
-
1 hour ago, mRcOOL1 said:
I have the original Venice on my server: runs ok and....Silent Mod
i agree with pappy @mr cool : many times players crashes with silent mod and some maps like venice original, glider and some others
-
yes and they had an etpro server if i am fine
-
On 2/21/2022 at 1:22 AM, PsychoPappy 4 said:
I need to go to the chicken bucket for a bucket of chicken lol. speaking of which, we should put that map on the rotation, its been awhile. :P
adding for today
-
1
-
-
On 2/20/2022 at 1:42 PM, CYBER4WOLF said:
Back then I was at the Chicken Bucket and we ran ETPRO until it was discontinued, we tried many mods after ETPRO but security & cheaters was always an issue.
If the weapon lag, security and anti - cheat is better in Any mod then I would vote for using that mod.
guys i played here also during 2003/2004 with old et friends from servers named ION and Azl and HKF
-
22 minutes ago, CYBER4WOLF said:
Odin.DK was accused of cheating about a year ago because of this ability and a few others.
So I posted exactly how how he was doing everything. ROFL
I also demonstrated that a medic can run while firing his weapon and jump over a dead teammate switching to his needle and revive him and return to running and firing his weapon using 1 key bind and jump.
Complex key binds and scripts are a great help.
But they do cause people to make accusations because they do not understand how it is being done.
I dont use any of those scripts anymore.
Because of this reason.
many guys use custom pro scripts and the problems are the guys accuse them to cheat when they dont and are just good players
Same For Axis But there will be just difference in their script words like the scriptname,classname and the targetname.
omnibots faq
in OMNIBOT
Posted
Omni-Bot F.A.Q.
General Questions
How do I customize the bots names ?
Open the autoexec.gm script for the game you wish to customize names for. For ET, the file is called et_autoexec.gm, for Quake4 it is called q4_autoexec.gm, and so on.
Inside you will see a table being constructed that associate names with a profile script.
Here's what the q4_autoexec.gm looks like at the time of this writing.
When a bot is added to the game without a name specified, it will choose a random available name from the ones listed. Each name has a profile associated with it, in this case all of these names have def_bot.gm, which is typically common for most games. The profile script is a way to customize a particular bot. You can script additional features or modifications to existing features into a script and associate the script with a specific bot name in order to have varying yet consistent behavior. Look here for more on customizing your Omni-bots.
To add additional names, simply add another line with a new name.
Normally there should be at least as many names as there are player slots available in the game, though you can add more and Omni-bot will randomly choose between all of them.
Small note : you don't have to add the prefix [BOT] to the name of the bot, but it would be fair or at least informative to let the players on your server know in a glance that Omni-bot is enabled and running.
ET Related
How To Adjust The Difficulty
Use command /bot difficulty
How To Edit Waypoints
Here you have the Omni-bot Waypointing general info page.
How To use Custom Waypoints
When you've downloaded a custom map, your Omni-bots will need a waypoint file for that map.
When you've downloaded a waypoint file for a custom ET map, you simply put the *.way and *.gm files inside your : ... \et\nav directory.
Currently released waypoints can be found in the Assembla SVN repository.
How To Run Omni-bot On Windows(tm) Home Server
Here's a small description on how to make a quick -vanilla ET + Omni-bot server run on your Win32 home computer. You should be able to let some Omni-bots run and also view and edit or create waypoints for the maps with it.
If not already :
When the above is installed you'll see a new shortcut in your Start Menu : Omni-Bot ET. The new shortcut is also on your desktop. When you click on this shortcut you will start Enemy Territory with the mod : Omni-bot. In this way you will still have to go through the ingame menu to host and or play on your own server.
To avoid this hassle every time here below there's the double click way to start your own server. Make a shortcut like this on your desktop or wherever you want :
Note : The above settings are called Cvar's (server variables) more on : Cvar's
After you made the shortcut, you should be able to start and run the Omni-bot server with it.
More and in depth info : Advanced Wolfenstein: Enemy Territory Server Setup Guide
There's also a pdf file for download.
How To Run Omni-bot On Linux Home Server
Make sure you've read the information on Installing Omni-bot.
How To Quickly Add The Omni-bots To Your server
There are -in short- 3 ways :
Example 1 omni-bot.cfg :
Example 2 omni-bot2.cfg :
Example 3 omni-bot3.cfg :
Omni-bot and Other Mods
Running Omni-bot with Wolfenstein:Enemy Territory is also possible in combination with several other mods.
Setting up a mod server to run with Omni-bot isn't much different from running Omni-bot with vanilla etmain.
Mod Folders & Mod Versions
The modfolders called omnibot, jaymod, etpub & noquarter should all (if installed) be at the same level as the etmain folder.
So after you install the mod you can create a new shortcut that points to the specific mod (folder) like :
You'll notice that the only thing in the shortcut line changing is the setting of fs_game.
Also you can set some Cvars which are specific to your mod into your (mod)server.cfg.
Mod Specific Cvars
Note :
Version 2.0.6 of Jaymod is the latest of the "stable" branch and runs with Omni-Bot version 0.61.
General Cvars
Whatever mod you are running, the server.cfg needs to be configured before players can connect. If you are renting a server then your game server provider will probably do the initial configuration for you.
The list is not to be said : complete. You as a server admin have to tweak it !
Here below are the most common ones.
General Server Setup Tips