Latest posts for the topic "Loopholes in the "L" stats menu"

Loopholes in the "L" stats menu

Szlat — GMT

We are trying out a new "L" stats menu, that paves the way for subclasses. In the past, each ability has had its limit built in, so it was almost impossible to buy something that was not permissible. With the subclasses, each ability has to be a lot more open, and it relies on the subclass stats menu to restrict who can buy what. So, if you get the old stats menu, and it does give you options to buy things, please do not exploit the bug by purchasing skills you are not supposed to have. Instead, please report to me how you managed to get the wrong stats menu up so I can fix it. Two points to note:

If you have purchased an ability that you are not supposed to have, next time you reconnect it will remove it, and credit you back with the points

It also logs that you have had this incorrect skill. What Druid will decide to do to frequent offenders is at his discretion.

Re:Loopholes in the "L" stats menu

synchronyze — GMT

When you reset a character all the options appear to become available that you meet stat requirements for. At first I figured with the new subclass system coming in that maybe if you don't choose a class at all you could buy a large variety of abilities from all the classes but limited to low levels. But after seeing this thread it appears to have been a bug. Details: Name: Rorschach I made a new character, bought medic class and loaded medic, then put the rest of the points into stats. Then decided to reset. Upon doing so I found that many options were now available that I hadn't noticed before. It looked more or less like everything could be bought. So I bought loaded weapons, loaded medic, and loaded artifacts. The medic weapon maker wouldn't work on any gun, saying something to the effect of "You cannot convert this type of weapon." I had a critical error at some point around this time, but didn't think anything of it since it happens to from time to time normally. Upon reconnecting someone else that was playing at the time also had the same issue of not being able to use the medic weapon maker (I'm not sure if this was related to what I was doing). The map then ended. Next map I clicked reset again. (I didn't notice or look to see if the bugged abilities had been reset automatically beforehand like you said they should.) Then bought loaded weapons, loaded medic, then eng. class. Then leveled and bought loaded engineer and shield healing(w/e the abil. is to get inf. eng. link?). Upon leveling, the options would lock again and I could only buy what I was supposed to. I spawned with one of each weapon as expected and the eng. link and constructions worked fine too. This time I could also make medic weapons, however the medic weapon I made wouldn't heal at all no matter how low on health a person was. So it was essentially a vanilla inf. weapon. After the second map I changed characters. After reading this thread I logged back on. His abilities have not been reset. He still is an eng. class with loaded weapons and loaded medic. I won't play him like this now that I know it's a bug. But I'll leave him as is for now if it's useful as a coding reference or whatnot. Hopefully this was helpful.

Re:Loopholes in the "L" stats menu

Szlat — GMT

Thanks synchronyze. I will investigate.

Loopholes in the "L" stats menu

greg11 — GMT

Szlat, back with druids200, it was possible to edit the stats file and add abilities. It would make the log entry, but nothing would be removed automatically. Was something added since then to remove the abilities?

Loopholes in the "L" stats menu

Szlat — GMT

greg11 wrote:

Szlat, back with druids200, it was possible to edit the stats file and add abilities. It would make the log entry, but nothing would be removed automatically. Was something added since then to remove the abilities?

Yes. The SubClass configuration is allowed to be dynamic, where server admins can change the configuration in the ini file. So, if an admin decides that this subclass shouldn't have this ability, or should have it to a lower level, then when the player joins, it checks, and fixes it. Obviously the reset bypasses that somehow, but I will sort that out.

Re:Loopholes in the "L" stats menu

Szlat — GMT

Ok. I have now got a fix for the reset stats problem. UT2004RPG wasn't re-initialising everything correctly, and so the correct list of abilities was not getting limited. Also put in more checks to sort out invalid data, including checking for multiple classes. Should be in the next build - whenever that is.

Re:Loopholes in the "L" stats menu

cribbage — GMT

I was looking at my L stats and noticed that I had countershove and retaliation that were at level 0. I thought that it was some kind of bug so I shrugged and re-maxed them seeing as I have a ton of points to burn. The changes stayed upon reconnecting. If I should not have that level of cs and retal, please knock me back down. Thanks, -Crib EDIT: Ok, so I don't keep up on all the threads like I should. I just saw the thread dealing with this. I wonder if I could then make one request - that the countershove on my account be reset to 0. I hate it.

Re:Loopholes in the "L" stats menu

Ratar_Killer — GMT

After using all my lifes in in an "assult" game, all items were avail. for purchase.

Re:Loopholes in the "L" stats menu

Flak Monkey — GMT

While at the end of a map, waiting during voting...I went into my stats and found Hording available to me....but at the beginning of the next map, it was gone.

Re:Loopholes in the "L" stats menu

Clone-Engineer — GMT

That could be a bug. I've seen hoarding on other servers and they allow you to gather items-much like a lucky weapon in this server the ability could've been removed-and it may come back once in a whiel as a temporary bug

Loopholes in the "L" stats menu

greg11 — GMT

Szlat, after taking a quick look at 2.21, and the 600+ lines of abilityconfigs in SubClass. Does the list of abilities need to be removed from the ut2004RPG config file? Would that at least prevent users from buying abilities they shouldn't have?

Loopholes in the "L" stats menu

Szlat — GMT

greg11 wrote:

Szlat, after taking a quick look at 2.21, and the 600+ lines of abilityconfigs in SubClass. Does the list of abilities need to be removed from the ut2004RPG config file? Would that at least prevent users from buying abilities they shouldn't have?

I don't think I can. The UT2004RPG code still needs to read it into the RPGStatsInv and do its own checks. I haven't checked recently, so it might not be needed anymore in the main list. A lot of the subclass code is getting the config to replicate to the client. It takes too long to replicate everything, so it just replicates what it thinks it needs. EDIT: It looks like the list of abilties is just used by the StatsMenu. I thought it was used by the code checking what skills a person had already bought - I didn't want the check to not find the ability and hence give the person the points to spend. But as you say, it looks like the list isn't used by core UT2004RPG code. However, at the moment to keep the size of the SubClass configuration down, I am not configuring all abilities into the SubClass code. The idea is you can buy any ability to its maximum, unless the SubClass code limits it. So abilities like Iron Legs are just left as defaults. Having to put all the abilities into the subclass configuration would up it by about ten more entries per subclass. So the list is still used by the new SubClass configuration code. Perhaps I should turn the configuration on its head, and say you can't buy anything unless it is configured in the SubClass config. Have a new section of the config which lists all the abilities and what their global availability is - so I wouldn't have to repeat Iron Legs for each subclass. Then I wouldn't need anything in the UT2004RPG available abilities list. (I would also need to change the Class purchasing part of the code. Again that still uses the UT2004RPG list of abilities)

Re:Loopholes in the "L" stats menu

Grimelark — GMT

Grimelark MD, somehow I got into the L screen after I died. I was the highest level on at the time and it was on the 2nd of Dec. When I got into that screen it had hoarding as well as several other things I don't think my medic shoudl have been able to use. Also didn't exp healing use to have 10 levels?

Re:Loopholes in the "L" stats menu

Szlat — GMT

Grimelark wrote:

Also didn't exp healing use to have 10 levels?

Loopholes in the "L" stats menu

greg11 — GMT

Szlat wrote:

However, at the moment to keep the size of the SubClass configuration down, I am not configuring all abilities into the SubClass code. The idea is you can buy any ability to its maximum, unless the SubClass code limits it. So abilities like Iron Legs are just left as defaults. Having to put all the abilities into the subclass configuration would up it by about ten more entries per subclass. So the list is still used by the new SubClass configuration code.

I keep seeing the configuration, and I keep thinking that there must be a better way. At +76k, the subclass code is about 10% of all of the code. Although it should compress well. Can a string be used as an array: Code:

     AbilityConfigs(0)=(AvailableSubClasses="0,3,6,12",AvailableAbility=Class'DruidsRPG221.DruidSomeAbility',MaxLevel="5,15,15,10")

"0,3,6,12" are the indexes for the subclasses array with the corresponding maxlevels. I just don't know if parsing strings like this would be possible.

Loopholes in the "L" stats menu

Szlat — GMT

greg11 wrote:

I keep seeing the configuration, and I keep thinking that there must be a better way. At +76k, the subclass code is about 10% of all of the code. Although it should compress well.

I know what you mean. It is quite cumbersome, and quite easy to make mistakes in :( Fortunately it doesn't have to be modified very frequently. However, if you add an ability in and want to keep it grouped by subclass, there are a whole lot of index numbers to change. I agree - there must be a better way. I thought about configuring it per ability, by giving a list of subclasses each ability could be used by, and storing it in the ability config - but then the subclass config is distributed all over the place, and would be more difficult for others to modify in the ini file.

greg11 wrote:

Can a string be used as an array: Code:
     AbilityConfigs(0)=(AvailableSubClasses="0,3,6,12",AvailableAbility=Class'DruidsRPG221.DruidSomeAbility',MaxLevel="5,15,15,10")
"0,3,6,12" are the indexes for the subclasses array with the corresponding maxlevels. I just don't know if parsing strings like this would be possible.

It is possible to parse strings - you have a number of functions including the good old left function. But then you have to keep remembering the subclass numbers. You could even slice it the other way, and have Code:

SubClass(0)=(SubClass="AM/WM Hybrid",ClassesAvailable="1,2,4",MinClassLevel="80,80,80",AbilitiesAvailable="1,2,7,9,15,26,29",MaxAbilityLevel="5,15,15,10,1,5,3")
// numbers and abilities I just made up - it doesn't match the real configuration

and so configure the whole subclass in one line. But I am not sure how maintainable it would be since you use numbers for the classes and abilities. EDIT: Perhaps it might be best to go for a very compact configuration like this, but then have a program or excel spreadsheet that would generate the config?

Loopholes in the "L" stats menu

greg11 — GMT

I can work on a script to convert a human readable config to this format. No matter which format it is in, I don't see a server admin having an easy time making their own configuration unless there is a program/script to assist. What I can do is have it convert the human readable form to all three ways. (and convert it from the current format too) I think I can make the human readable format something like: Code:

Class: DruidsRPG221.ClassAdrenalineMaster
  Available Subclasses:
    AM/WM hybrid,  80
    AM/MM hybrid,  80
    AM/Eng hybrid, 80
    Extreme AM,    100
  Available Abilities:
    DruidsRPG221.DruidArtifactLoaded,         4
    DruidsRPG221.AbilityEnhancedReduction
    

Class: DruidsRPG221.ClassWeaponsMaster
  Available Subclasses:
    AM/WM hybrid,  80
    WM/MM hybrid,  80
    WM/Eng hybrid, 80
    Extreme WM,    100
  Available Abilities:
    DruidsRPG221.DruidRegen,                  5
    DruidsRPG221.DruidVampire,                10


SubClass:  AM/WM hybrid
  Available Abilities:
    DruidsRPG221.DruidAmmoRegen,              4
    DruidsRPG221.DruidAwareness,              2
    DruidsRPG221.DruidNoWeaponDrop


SubClass:  AM/MM hybrid
  Available Abilities:
    DruidsRPG221.DruidArtifactLoaded
    DruidsRPG221.DruidArtifactLoadedHybrid
    DruidsRPG221.DruidAdrenalineSurge
    DruidsRPG221.DruidEnergyVampire
    DruidsRPG221.AbilityEnergyShield
#    DruidsRPG221.DruidLoaded
#    DruidsRPG221.DruidVampire
#    DruidsRPG221.AbilityEnhancedDamage
#    DruidsRPG221.AbilityLoadedEngineer
#    DruidsRPG221.DruidShieldRegen
#    DruidsRPG221.AbilityShieldHealing
#    DruidsRPG221.DruidArmorRegen
#    DruidsRPG221.DruidArmorVampire
#    DruidsRPG221.AbilityConstructionHealthBonus
#    DruidsRPG221.AbilityEngineerAwareness
#    DruidsRPG221.AbilityRapidBuild
#    DruidsRPG221.AbilityLoadedHealing
    DruidsRPG221.AbilityExpHealing
    DruidsRPG221.AbilityMedicAwareness
    DruidsRPG221.AbilityLoadedMonsters,       5
    DruidsRPG221.AbilityMonsterHealthBonus,   4
    DruidsRPG221.AbilityMonsterPoints,        5
    DruidsRPG221.AbilityMonsterSkill,         3
    DruidsRPG221.AbilityMonsterDamage
    DruidsRPG221.AbilityEnhancedReduction
    DruidsRPG221.DruidAmmoRegen
    DruidsRPG221.DruidAwareness
    DruidsRPG221.DruidNoWeaponDrop
#    DruidsRPG221.DruidRegen
    DruidsRPG221.DruidAdrenalineRegen
    DruidsRPG221.AbilityVehicleEject
#    DruidsRPG221.AbilityWheeledVehicleStunts
#    DruidsRPG221.AbilityBerserkerDamage

The last ability list shows how abilities could be commented out to show what abilities are removed.

Re:Loopholes in the "L" stats menu

Szlat — GMT

Looks good. I wouldn't do all 3 ways though. There may be two options required - one for us to type the stuff into the subclass.uc file. The second for server admins to put in their UT2004RPG.ini. (I wonder if we should use a different config file for the subclass stuff?) Although the two should be basically the same, one has index numbers in, which are a pain to maintain. Only problem with using python is that it means every server admin will need a copy. I know its free, but it is one extra hassle.

Re:Loopholes in the "L" stats menu

greg11 — GMT

Szlat wrote:

Only problem with using python is that it means every server admin will need a copy. I know its free, but it is one extra hassle.

If the server is running linux, it shouldn't be a problem. There is also a way to compile python programs into windows executables so python is not needed.

Loopholes in the "L" stats menu

Szlat — GMT

greg11 wrote:

Can a string be used as an array: Code:
     AbilityConfigs(0)=(AvailableSubClasses="0,3,6,12",AvailableAbility=Class'DruidsRPG221.DruidSomeAbility',MaxLevel="5,15,15,10")
"0,3,6,12" are the indexes for the subclasses array with the corresponding maxlevels. I just don't know if parsing strings like this would be possible.

I think I'll knock up a test this way, and see if it looks better. For the short term, I'll just use it to populate existing data structures since I don't want to recode the replication.

Loopholes in the "L" stats menu

Szlat — GMT

Szlat wrote:

......I think I'll knock up a test this way, and see if it looks better. For the short term, I'll just use it to populate existing data structures since I don't want to recode the replication.

Actually, it is a bit easier than that. If I create the structure Code:

struct AbilityConfig
{
	var class AvailableAbility;
	var Array AvailableSubClasses;	
	var Array MaxLevels;	
};
var config Array AbilityConfigs;

then I can configure as Code:

AbilityConfigs(0)=(AvailableAbility=Class'DruidsRPGcvs.DruidRegen',AvailableSubClasses=(0,3,6,12),MaxLevels=(5,15,15,10))

Re:Loopholes in the "L" stats menu

Szlat — GMT

Actualyy, I am wondering if we shouldn't just list the maxlevl for every subclass, rather than specifying the subclass and maxlevel as a pair. So something more like AbilityConfigs(0)=(AvailableAbility=Class'DruidsRPGcvs.DruidRegen',MaxLevels=(5,0,0,15,0,0,15,10,0,0,0,4,0)) Might be a lot easier to understand, and easier to generate with scripts.

Re:Loopholes in the "L" stats menu

Szlat — GMT

So, with the one big list of levels, I can configure the whole thing as: Code:

//                                                                                                   N, AW,AM,AE,WM,WE,ME, XA,XW,XM,XP,XE, B,  A, W, M, E, G
AbilityConfigs( 0)=(AvailableAbility=Class'DruidsRPGcvs.DruidArtifactLoaded',            MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  5, 0, 0, 0, 0, 0,  4, 0, 0, 0, 0))
AbilityConfigs( 1)=(AvailableAbility=Class'DruidsRPGcvs.DruidArtifactLoadedHybrid',      MaxLevels=( 0,  2, 2, 2, 0, 0, 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 0, 1))
AbilityConfigs( 2)=(AvailableAbility=Class'DruidsRPGcvs.DruidAdrenalineSurge',           MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  3, 0, 0, 0, 0, 2,  2, 0, 0, 0, 0))
AbilityConfigs( 3)=(AvailableAbility=Class'DruidsRPGcvs.DruidEnergyVampire',             MaxLevels=( 0,  5, 0, 0, 0, 0, 0,  2, 0, 0, 0, 0, 0,  5, 0, 0, 0, 3))
AbilityConfigs( 4)=(AvailableAbility=Class'DruidsRPGcvs.AbilityEnergyShield',            MaxLevels=( 0,  0, 1, 2, 0, 0, 0,  3, 0, 0, 0, 0, 0,  2, 0, 0, 0, 0))
AbilityConfigs( 5)=(AvailableAbility=Class'DruidsRPGcvs.DruidLoaded',                    MaxLevels=( 0,  2, 0, 0, 2, 2, 0,  0, 6, 0, 0, 0, 5,  0, 5, 0, 0, 1))
AbilityConfigs( 6)=(AvailableAbility=Class'DruidsRPGcvs.DruidVampire',                   MaxLevels=( 0,  3, 0, 0, 0, 3, 0,  0,15, 0, 0, 0,10,  0,10, 0, 0, 2))
AbilityConfigs( 7)=(AvailableAbility=Class'DruidsRPGcvs.AbilityEnhancedDamage',          MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0,10, 0, 0, 0, 0,  0,10, 0, 0, 2))
AbilityConfigs( 8)=(AvailableAbility=Class'DruidsRPGcvs.AbilityBerserkerDamage',         MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 0, 0,20,  0, 0, 0, 0, 0))
AbilityConfigs( 9)=(AvailableAbility=Class'DruidsRPGcvs.AbilityLoadedHealing',           MaxLevels=( 0,  0, 2, 0, 2, 0, 2,  0, 0, 4, 2, 0, 0,  0, 0, 3, 0, 2))
AbilityConfigs(10)=(AvailableAbility=Class'DruidsRPGcvs.AbilityExpHealing',              MaxLevels=( 0,  0, 2, 0, 2, 0, 2,  0, 0,15, 0, 0, 0,  0, 0, 9, 0, 0))
AbilityConfigs(11)=(AvailableAbility=Class'DruidsRPGcvs.AbilityMedicAwareness',          MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 2, 1, 0, 0,  0, 0, 2, 0, 0))
AbilityConfigs(12)=(AvailableAbility=Class'DruidsRPGcvs.AbilityLoadedMonsters',          MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0,20, 0, 0,  0, 0,15, 0, 0))
AbilityConfigs(13)=(AvailableAbility=Class'DruidsRPGcvs.AbilityMonsterHealthBonus',      MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0,10, 0, 0,  0, 0,10, 0, 0))
AbilityConfigs(14)=(AvailableAbility=Class'DruidsRPGcvs.AbilityMonsterPoints',           MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0,30, 0, 0,  0, 0,20, 0, 0))
AbilityConfigs(15)=(AvailableAbility=Class'DruidsRPGcvs.AbilityMonsterSkill',            MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 7, 0, 0,  0, 0, 7, 0, 0))
AbilityConfigs(16)=(AvailableAbility=Class'DruidsRPGcvs.AbilityMonsterDamage',           MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0,20, 0, 0,  0, 0, 0, 0, 0))
AbilityConfigs(17)=(AvailableAbility=Class'DruidsRPGcvs.AbilityEnhancedReduction',       MaxLevels=( 0,  0, 0, 0, 0, 0, 5,  0, 0,10,10, 0, 0,  0, 0,10, 0, 2))
AbilityConfigs(18)=(AvailableAbility=Class'DruidsRPGcvs.AbilityLoadedEngineer',          MaxLevels=( 0,  0, 0, 8, 0, 8, 8,  0, 0, 0, 0,20, 0,  0, 0, 0,15, 5))
AbilityConfigs(19)=(AvailableAbility=Class'DruidsRPGcvs.DruidShieldRegen',               MaxLevels=( 0,  0, 0, 0, 0,10, 0,  0, 0, 0, 0, 0, 0,  0, 0, 0,15, 0))
AbilityConfigs(20)=(AvailableAbility=Class'DruidsRPGcvs.AbilityShieldHealing',           MaxLevels=( 0,  0, 0, 0, 0, 0, 3,  0, 0, 0, 0, 0, 0,  0, 0, 0, 3, 0))
AbilityConfigs(21)=(AvailableAbility=Class'DruidsRPGcvs.DruidArmorRegen',                MaxLevels=( 0,  0, 0, 0, 0, 2, 2,  0, 0, 0, 0, 5, 0,  0, 0, 0, 5, 0))
AbilityConfigs(22)=(AvailableAbility=Class'DruidsRPGcvs.DruidArmorVampire',              MaxLevels=( 0,  0, 0, 0, 0, 5, 0,  0, 0, 0, 0,15, 0,  0, 0, 0,10, 0))
AbilityConfigs(23)=(AvailableAbility=Class'DruidsRPGcvs.AbilityConstructionHealthBonus', MaxLevels=( 0,  0, 0, 6, 0, 6, 6,  0, 0, 0, 0,10, 0,  0, 0, 0,10, 3))
AbilityConfigs(24)=(AvailableAbility=Class'DruidsRPGcvs.AbilityEngineerAwareness',       MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 1, 0))
AbilityConfigs(25)=(AvailableAbility=Class'DruidsRPGcvs.AbilityRapidBuild',              MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 0,10, 0,  0, 0, 0, 5, 0))
AbilityConfigs(26)=(AvailableAbility=Class'DruidsRPGcvs.DruidAmmoRegen',                 MaxLevels=( 0,  4, 2, 2, 2, 2, 0,  1, 4, 0, 0, 0, 4,  4, 4, 0, 0, 2))
AbilityConfigs(27)=(AvailableAbility=Class'DruidsRPGcvs.DruidAwareness',                 MaxLevels=( 0,  2, 0, 0, 0, 0, 0,  2, 2, 0, 0, 0, 2,  2, 2, 0, 0, 2))
AbilityConfigs(28)=(AvailableAbility=Class'DruidsRPGcvs.DruidNoWeaponDrop',              MaxLevels=( 0,  0, 0, 0, 0, 0, 0,  0, 0, 0, 0, 0, 0,  3, 2, 0, 0, 0))
AbilityConfigs(29)=(AvailableAbility=Class'DruidsRPGcvs.DruidRegen',                     MaxLevels=( 0,  3, 3, 0, 5, 3, 3,  0, 0, 5, 5, 0, 0,  0, 5, 5, 0, 3))
AbilityConfigs(30)=(AvailableAbility=Class'DruidsRPGcvs.DruidAdrenalineRegen',           MaxLevels=( 0,  0, 3, 3, 1, 0, 1,  4, 0, 2, 2, 0, 0,  3, 0, 3, 0, 3))
AbilityConfigs(31)=(AvailableAbility=Class'DruidsRPGcvs.AbilityVehicleEject',            MaxLevels=( 0,  1, 1, 1, 1, 1, 1,  0, 0, 0, 0, 4, 0,  1, 1, 1, 4, 1))
AbilityConfigs(32)=(AvailableAbility=Class'DruidsRPGcvs.AbilityWheeledVehicleStunts',    MaxLevels=( 0,  1, 1, 1, 1, 1, 1,  0, 0, 0, 0, 3, 0,  1, 1, 1, 3, 1))
AbilityConfigs(33)=(AvailableAbility=Class'DruidsRPGcvs.DruidGhost',                     MaxLevels=( 3,  3, 3, 3, 3, 3, 3,  2, 3, 3, 3, 2, 3,  3, 3, 3, 3, 3))
AbilityConfigs(34)=(AvailableAbility=Class'DruidsRPGcvs.DruidUltima',                    MaxLevels=( 2,  2, 2, 2, 2, 2, 2,  2, 2, 2, 2, 2, 2,  2, 2, 2, 2, 2))
AbilityConfigs(35)=(AvailableAbility=Class'DruidsRPGcvs.DruidCounterShove',              MaxLevels=( 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5))
AbilityConfigs(36)=(AvailableAbility=Class'DruidsRPGcvs.DruidRetaliate',                 MaxLevels=(10, 10,10,10,10,10,10, 10,10,10,10,10,10, 10,10,10,10,10))
AbilityConfigs(37)=(AvailableAbility=Class'UT2004RPG.AbilityJumpZ',                      MaxLevels=( 3,  3, 3, 3, 3, 3, 3,  3, 3, 3, 3, 3, 3,  3, 3, 3, 3, 3))
AbilityConfigs(38)=(AvailableAbility=Class'UT2004RPG.AbilityReduceFallDamage',           MaxLevels=( 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4))
AbilityConfigs(39)=(AvailableAbility=Class'UT2004RPG.AbilitySpeed',                      MaxLevels=( 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5))
AbilityConfigs(40)=(AvailableAbility=Class'UT2004RPG.AbilityShieldStrength',             MaxLevels=( 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4))
AbilityConfigs(41)=(AvailableAbility=Class'UT2004RPG.AbilityReduceSelfDamage',           MaxLevels=( 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5, 5,  5, 5, 5, 5, 5))
AbilityConfigs(42)=(AvailableAbility=Class'UT2004RPG.AbilitySmartHealing',               MaxLevels=( 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4))
AbilityConfigs(43)=(AvailableAbility=Class'UT2004RPG.AbilityAirControl',                 MaxLevels=( 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4, 4,  4, 4, 4, 4, 4))
AbilityConfigs(44)=(AvailableAbility=Class'UT2004RPG.AbilityFastWeaponSwitch',           MaxLevels=( 2,  2, 2, 2, 2, 2, 2,  0, 2, 2, 2, 1, 2,  2, 2, 2, 2, 2))

which is a lot smaller, and is easy to read EDIT: Except of course you can't have spaces in the config. Grrr

Loopholes in the "L" stats menu

greg11 — GMT

It's beautiful. Requiring all MaxLevels to be set could be good for error checking. If an ability doesn't have the correct length output it to the log. The spaces issue should be minor since a find&replace could be used to remove all the spaces. Just keep a text file with the spaces. This should be even easier to export from a spreadsheet too. I am assuming the order still depends on the index of the subclasses array.

Loopholes in the "L" stats menu

Szlat — GMT

greg11 wrote:

I am assuming the order still depends on the index of the subclasses array.

Agreed

Re:Loopholes in the "L" stats menu

TON80 — GMT

I'm seeing Counter Shove and Retaliation listed twice on the menu. (Medic subclasses)

Re:Loopholes in the "L" stats menu

RoadKill v3.4 — GMT

TON80 wrote:

I'm seeing Counter Shove and Retaliation listed twice on the menu. (Medic subclasses)

this occurs with all sub-classes I believe the second set is the newer versions

Re:Loopholes in the "L" stats menu

cribbage — GMT

And I am very happy that I learned my lesson about countershove and shun them like the plague.

Re:Loopholes in the "L" stats menu

HighwratH — GMT

Counter shove has it's place: romramoonstation, spacenoxx, megawoot, otherwise it's a pain.