Nous sommes le 13 Aoû 2020, 15:26

Online     TeamSpeak UT99     UnrealTournament-V3     Download     Utfiles medor     Vote Weborama     Vote Unrealtop200     Vote xtremetop100     free TeamSpeak     Unreal Soundtracks     Google    Mini-Chat Mini-Chat

Poster un nouveau sujet Répondre au sujet  [ 7 messages ] 
 Nouveau ServerSide_Mods medToggle 
Auteur Message
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Nouveau ServerSide_Mods medToggle
Un couteau suisse pour votre server qui permet de gérer pleins de réglages sans mettre 36 modes un coup d'oeuil sur le readme vous aideras a comprendre l'étendu.
Complémentaire avec Mapvotela13 :ok1:

======= medToggle ========
=== a UT99 mutator by ====
_   _       _
| | | | ___ | | ___ _ __
| |_| |/ _ \| |/ _ \ '_ \
|  _  |  __/| |  __/ | | |
|_| |_|\___||_|\___|_| |_|

== Version 330 ===========
== 2011.12.31 ============

This mutator allows you to 'toggle' game settings, actors, mutators and weapons/ammo from
map to map. You can associate your settings/actors/mutators/weapons/ammo at the map level,
at the game class level, or make them overall defaults.

This mute also can be told if you are using mapvote. That way it can work in conjunction
with mapvote.

Or instead of mapvote or a regular rotation, with this mutator you can set up a map rotation
list with mixed game class types. For example the first map in the rotation could be DM,
then the next CTF, then the next DOM, and so on.

I will provide examples of all of the above.

A note on the names of your maps. If you want medToggle to work properly, the names of your
maps must have a "dash" in them, which is the position marker for the map prefix.
For example, in the map name DM-ArcaneTemple, how do I know that the prefix is "DM"? Because
there is a "-" (dash) after the "DM"! So I need that dash so I can find the prefix.

I will give examples in this order:
A) the basic settings
B) Mutators and Actors
C) working with MapVote (prerequisite reading, parts A and B!)
D) creating a mixed maplist (prerequisite reading, parts A and B!)

== First, a setting to help with debugging ===

To help figure things out along the way, set this value in the ini:


This will spit out lots of helpful messages to the log. After, when you have figured things
out and it is running as you expect, then you can set it to false.

== How to specify the basic settings at the default, game class, and map level ==

   | basic settings |

Here are the basic settings you are going to be able to set, their default values, and the
accepted value for each:

Setting Name      default      acceptable values
------------      -------      -----------------
Translocator      false      true or false
GameSpeed      1      greater than zero and less than or equal to 2 (decimals allowed)
AirControl      0.35      greater than or equal to zero and less than or equal to 1 (decimals allowed)
BotSkill      2      greater than or equal to zero and less than or equal to 7 (integers only)
MinPlayers      2      greater than or equal to zero and less than or equal to 32 (integers only)
FragLimit      30      greater than zero and less than 1000 (integers only)
MaxTeamScore      100      greater than zero and less than 1000 (integers only)
TimeLimit      20      greater than or equal to zero and less than 1000 (integers only)
WeaponStay      true      true or false
ForceRespawn      false      true or false
ForceTeamBalance   true      true or false
FriendlyFire      0      greater than or equal to zero and less than or equal to 1 (decimals allowed)
Gravity         -1      greater than or equal to zero and less than or equal to 1900 (integers only)
NoDynamicLighting   false      true or false
NoActorShadows      false      true or false
NoCorona      false      true or false
NoLensFlare      false      true or false
NoSpecialLit      false      true or false
NoLightEffect      false      true or false
NoSpecialLightType   false      true or false

Here are what the values mean for cBotSkill:

0 = novice
1 = average
2 = experienced
3 = skilled
4 = adept
5 = masterful
6 = inhuman
7 = godlike

For Gravity, the value of -1 has a special meaning. It means that medToggle should leave the
gravity alone! A value of zero means just that - zero gravity. Then as you increase the value,
the gravity gets stronger. As a measuring stick of what values to try, the normal gravity value
is 950, and the typical lowgrav in UT is 200.

The last 7 settings are for light. NoDynamicLighting is the 'master' value amongst them.
That is, if you want them all to be true, just set NoDynamicLighting = true. However if you
want finer control, leave NoDynamicLighting = false, and set to true any of the others.

Ok, so there are the defaults and their values. The defaults mentioned above are what medToggle
will use if you don't specify anything. So, let's start customizing your defaults.

In the medToggle.ini provided, you will find this line:


We need to start filling in the Settings. Let's say you are happy with the medToggle defaults,
and you only want to change the FragLimit to 22. The line would now look like this:


To specify more defaults, just separate the items with commas. I'll add 2 more as an example.


So now have your overall defaults set. Now we can start tweaking per game class, and per map.

-- Dec 31, 2011 -- MaxPlayers --
There is now one more setting... MaxPlayers. If you do not want to worry about this setting,
then just skip down to the next section called "game class settings"

MaxPlayers accepts a value between 1 and 64 inclusive.

If you want medToggle to process any MaxPlayers value you have specified, you must also set
the bSetMaxPlayers flag to true. See the example ini for the location of this flag.

DISCLAIMER: For those of you who rent your server, you know that you only get as many slots
as you pay for. If you attempt to set MaxPlayers higher than the value you have paid for, I
am not responsible for any of the consequences as a result of this.

   | game class settings |

Examples of a game classes are DeathMatch, CTF, Domination, etc. Now that your basic defaults
are in place, you can now specify settings you want applied at the game class level. You should
see these 6 lines in the ini:


Above we have the 6 typical game classes (DM, TDM, CTF, Domination, Last Man Standing, and Assault).
For an example, I'll turn on the translocator for the team games, and make sure there are more
min players. As well, realize that the default for MaxTeamScore is currently 100. That may be
good for TDM and DOM, but a bit much for CTF  :-O
So we'll lower that. I'm also going to lower the gravity a bit more just for CTF. So this gives us:


Note: you can ADD more game classes here. I will give an example of this later on.
Note: each game class can only appear in the list once.
Note: in the example each mGame line has a "prefix" setting, but just ignore this for the moment.

Note we have specify Gravity in both the defaults and for the CTF game class. This is perfectly
valid. Any setting specified at the game class level overrules any previous value for the setting.
Same with when we get to MAP settings. Settings specified at map level overrule the game and
default values.

   | Map settings |

First you have set the default Settings.
Then you were able to tweak the Settings a bit depending on the game class.
Finally, you can enter more settings that will get applied to specific maps.

Here is the first map example line from the ini:


In this example we have decided to increase the GameSpeed to 1.5, up the BotSkill to 5, and
have a MinPlayers of 10. All for just the map DM-ArcaneTemple.

Of course you can add more maps here, up to 256.

Note, map names must be REAL map names, not aliased names. This will make sense later.
Just make sure that you use real map names only.

== How to get medToggle to add Mutators and Actors, exclude Mutators/Actors, and swap Weapons/Ammo ==

First, if you are starting any mutators with a ServerActor in your UnrealTournament.ini, I
recommend you move them out of there and put them into the medToggle.ini. This will centralize
your management of your Actors and Mutators.

(NOTE, you must still leave any custom ServerPackages lines in your unrealTournament.ini!)

   | default mutators and Actors |

Ok let's say you have a default server actor you want running all the time, for example UT Pure.
So we need to add it to our mDefaults line. Here is what our mDefaults line would look like after
adding it. Note that you can put it anywhere in the line, so I took the blank Actors="" that
currently appears after the settings, and moved it to the beginning of the line):


That's it. medToggle will now start UT Pure for you. If you want more than one server actor, they
are separated with commas within the double quotes, like this:


Getting mutators to start up is basically the same thing. An example:


For multiple mutators, just separate them with commas.

   | game class mutators and Actors |

So now you have set up the actors and mutators you want to run all the time (in the defaults).
Now you can use the game classes to pile on more mutators and Actors to start per game class.
And, by default, the mutators and Actors you start adding at the game class level are going
to be ADDED to what was started at the default level. So let's say we have this for mDefaults
and the DeathMatch game class:


Notice in the mGame[0] line we have just added mutators and Actors in the same fashion as
we did for the defaults. So the mutators and Actors from the defaults and the game class
will be combined, resulting in these items getting started:


So again, by default, the lists are ADDED together.

   | Map mutators and Actors |

Same idea here. If you want mutators/Actors started for a single map, add them to one
of your mMap lines. Similarly, the mutators/Actors you specify here will be ADDED to
the default and game class ones. Let's say we have these three lines:


The resulting mutators/Actors to start will be:


So you could start up the Fatboy mutator for a single map. Kewl.

   | Excluding mutators and Actors |

In the mDefaults line you can find these two variables:


Obviously, this allows you to specify Actors and mutators that you don't want to
get started. There are two main uses for this (as well as others). I'll start with
an example at the game class level.

The first handy thing about exclusion is that some mutators/actors are not compatible
with each other. So let's say you were including UT PURE at the defaults level. But then
for one particular class, it is not compatible with PURE, so you wouldn't want it to run.
So here is an example of three new game classes, that don't want UT PURE running:


mutatorsToExclude works the same way.

Here is the second awesome use of exclusion. This one is very powerful. Besides using
this to exclude an Actor that you yourself have added at the default level, well, you
can also use it to exclude almost any actor you want! A couple of common ones that
people don't want are Invisibility and UDamage. There are a couple of mutators out
there to exclude them, but why have to bother with a couple of mutators when you can
just do this?


And you can specify ActorsToExclude at the default level, game level, or map level!
How about no health for one map?


How about never seeing that enhanced shock rifle?


And on and on. As long as you know the name of the name of the package and class,
most actors can be excluded.
(There ARE exceptions though. 'PathNode' I know to be one of them).

   | Excluding a literal INSTANCE of an Actor (advanced) |

This is advanced stuff, but if you are a control freak who has oodles of time to
spend on your server, then read on  :)

The next variable available: InstanceActorsToExclude

This variable is only available at the map level. This deals with literal instances of actors. This allows
you to remove a single instance of an actor at a time. An example. Let's imagine the map Deck16][. This
map has TWO flak cannons. Let's say we want to remove the one down by the goo. First I need to know its
unique name, so I do this:
- I open UnrealEd2
- I find that flak cannon
- I right-click on it, and select Properties
- I expand the 'Object' node.
- I can now see the value for 'Name'. In this case the value is "UT_FlakCannon1".

I now know this flak cannon is uniquely identified with the name "UT_FlakCannon1". So in my map line
I would do this:


There you have it, the flak cannon by the goo would be removed, and ONLY this flak cannon would be removed.
You can specify multiple items of course, separated by commas.

   | Swapping Weapons and Ammo (generically) |

Next two variables available are WeaponSwap and AmmoSwap. This allows you to swap weapons and ammo.
These two variables can be set at all levels.

A couple of uses for this. Let's say you hate a particular weapon and don't want it to appear in any
of the maps. But instead of using the exclude options above, it may be better to swap in a different
weapon. This is because the map may have been designed to make the weapon's location a focal point.
so if there was no longer anything there, there would be no reason to go to that section of the map.

Another use is to replace all types of weapons with a single weapon, sort of making it into an Arena.
(there is a quick way to do this, as I'll show you).

Ok, the basic way to swap - the format is first the class that exists, then a colon, then the class you
want to replace it with. So for this example we are replacing the sniper rifle with a pulse gun:


Maybe you could add this to Deck16][ and stop the camping from above :)

To easily replace ALL weapons/ammo with a particular weapon/ammo, we introduce the keyword of [all],
used like this:


There are a couple of individual flags you can set when you are replacing all weapons. These should
be self-explanatory:


These two settings go by themselves directly under the [medToggle330.medToggle] section.
That's it. For ease of reference I'll list the common weapon/ammo classes here for you.

Weapon         Ammo
------         ----
Botpack.enforcer   Botpack.EClip
Botpack.minigun2   Botpack.Miniammo
Botpack.PulseGun   Botpack.PAmmo
Botpack.ripper      Botpack.BladeHopper
Botpack.ShockRifle   Botpack.ShockCore
Botpack.SniperRifle   Botpack.BulletBox   Botpack.RifleShell
Botpack.ut_biorifle   Botpack.BioAmmo
Botpack.UT_Eightball   Botpack.RocketPack
Botpack.UT_FlakCannon   Botpack.FlakAmmo

Note - Weapons/Ammo that you are trying to add to the map do not respect the ActorsToExclude list.
So if you have specified a weapon/ammo to go in, then it's going in!

   | Swapping Weapons and Ammo (specifically) |

If you wish to swap a SPECIFIC weapon or piece of ammo in the map, here's how by using these two variables:


This is very very similar to the section above titled "Excluding a literal INSTANCE of an Actor". You need to
find the literal name of the actor, then you will specify a generic name to replace it with. For example:


So it will try to find a shock rifle named "ShockRifle0", and it will replace it with a ripper. Again you can
only use this at map level.

=============== Using medToggle with MapVoteLA13 ====================

This assumes you already know how to use the MapVoteLA13 mutator.
So you would first set up your medToggle as outlined above to handle what settings, mutators,
and Actors you want. Then you would add one more setting to the medToggle.ini:


This lets medToggle know to it has to allow mapvote to handle a couple of things. Now over to
the MapVoteLA.ini. In there you will need a CustomGameConfig line for each game class you want
to present for voting on (you should know this already). Here is an example:


For each game class, you specify just the medToggle as the only mutator, and then medToggle will
handle all the other stuff you set up within its ini.

Now of course you usually use MapVote to get a particular type of game play going associated with
a NewPrefix.

   -- NOTE!! - MapVote's "NewPrefix" and medToggle's "prefix" have nothing to do with each other --

The way to think of organizing it, is to move all the mutators and Actors that you want to start
either ALL THE TIME or all the time FOR A PARTICULAR GameClass or Map, and then move these into
medToggle. Then you keep the one mutator that distinguishes the play in mapvote. Let's say you
previously had this in mapvote:


You could change it so this is in mapvote:


and this in medToggle:


======== How to have a map rotation with mixed game classes =========

The idea here is that you could play a deathmatch game, then a CTF, then a domination, then maybe
back to CTF, then a TDM, etc, etc, all consecutively from a map rotation, without having to vote.
First we need this setting set to true:


We also MUST ensure that bMapVote is turned off:


You can also set the time it takes to load the next map. In this example it will take 5 seconds:


Ok, now we need to specify the maps in the rotation. In medToggle.ini, you would add a new section
and specify the maps like this (for example):


(... up to 256 maps).

Okaaaaay, this is finally where the 'prefix' setting in the mGame list is finally going to be used.
Notice some of the map names above. TDM-ArcaneTemple.unr. EDM-Fetid.unr. These maps do not actually
exist. What we have done is swapped prefixes.


Here are the steps per map.
- you chose a map you want to play, for example DM-ArcaneTemple
- Let's say you want the game play to be Team Death Match
- So you look in your mGame list, and find the GameClass='Botpack.TeamGamePlus'
- in this mGame line, you see that prefix="TDM"
- So you take "TDM" and swap it in as the prefix for the map name (in the ini file only! Not on the harddrive!)
- That is how DM-ArcaneTemple becomes TDM-ArcaneTemple.

Okay last requirement. Because you are going to tell medToggle you want it to run TDM-ArcaneTemple,
but that map doesn't really exist, it needs to know what the REAL prefix is. So you provide these:


... where 'prefix' is the REAL prefix, and 'alias' is of course the fake prefix, or aliased prefix.

Note: "prefix" values in the mGame list can appear only once (so they must be unique).

NOTE: When you first start up UT, it will not use a map from this list. After that first map is
over, then it will start using this list.


   |UnrealTournament.ini |

You need to add this line to the [Engine.GameEngine] section of the UnrealTournament.ini:


   | files |

Once you have finished setting up the medToggle.ini, then you will need to put these files into the System folder:

   | map vote |

If you are using in conjunction with mapvote, then you don't start it up. Rather mapvote will do that.

   | command line |

If your host allows you to edit the startup command line, here is an example that would include this mutator:

unrealtournament.exe DM-Codex?game=Botpack.DeathMatchPlus?MaxPlayers=16?mutator=medToggle330.medToggle -server

To specify more than one mutator, you just separate them with commas:

unrealtournament.exe DM-Codex?game=Botpack.DeathMatchPlus?MaxPlayers=16?mutator=CCProtector420.CCProtector,medToggle330.medToggle -server

Note: if you are using mapvote, you do not need to add it to the command line, since mapvote will start it up instead.

   | help |


== fin ==


28 Déc 2010, 00:27
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle300
La 301

Téléchargement ...


02 Jan 2011, 23:36
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle300
La 302

Téléchargement ...


06 Fév 2011, 09:51
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle v 330
La 330 ... gle330.rar


01 Jan 2012, 13:06
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle v 335
La 335 ... gle335.rar


13 Jan 2012, 20:22
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle
La 350

Téléchargement ... gle350.rar


21 Jan 2013, 19:39
Profil Envoyer un e-mail
Avatar de l’utilisateur

Inscription: 01 Oct 2008, 01:14
Messages: 5566
Nouveau message Re: Nouveau ServerSide_Mods medToggle
373 ... rch_mode=f


28 Mai 2019, 07:20
Profil Envoyer un e-mail
Afficher les messages postés depuis:  Trier par  
Poster un nouveau sujet Répondre au sujet  [ 7 messages ] 

Qui est en ligne

Utilisateurs enregistrés : Aucun utilisateur enregistré

Vous ne pouvez pas poster de nouveaux sujets
Vous ne pouvez pas répondre aux sujets
Vous ne pouvez pas éditer vos messages
Vous ne pouvez pas supprimer vos messages
Vous ne pouvez pas joindre des fichiers

Aller à:  
Powered by phpBB © phpBB Group.
Designed by Vjacheslav Trushkin for Free Forums/DivisionCore.
Traduction par: