drmskr
New Member
Posts: 8
Likes: 0
|
Post by drmskr on Feb 9, 2016 9:45:53 GMT -5
Hello again, No the Ground Ants and Flying ants are not the same thing. The option in the manager only controls Ant_Character_BP_C and not FlyingAnt_Character_BP_C so they are NOT being controlled by the same check mark. When removing them, it only adds Ant_Character_BP_C to the .ini file to remove, and ignores the FlyingAnt_Character_BP_C Can you please indicate what you are trying to do with the flying ants. Like everything Wildcard does, they are not consistent with the server settings. When setting spawn rates for the creatures the DinoTagName is used. When setting the damage and resistance multipliers the BP name is used. Yes, the BP name for Ants and Flying Ants is different, but the DinoTagName is the same. When the Flying Ant was included in the ASM it would write out 2 sets of spawn information for Ants and caused occasional problems. So are you: 1. Trying to change the spawn rates and multiplers? 2. Trying to change the Damage and resistance multipliers? Yes, to be more specific, when selecting the Titanomyrna (ant) in the creature section, it only refers to the land ants, and does nothing for the flying ants. In my case, I am disabling the ants due to rediculous behavior, so when I uncheck the box, only the land based ants are removed. I have to add NPCReplacements=(FromClassName="FlyingAnt_Character_BP_C",ToClassName="") manually into the .ini file. Even worse, is every time I hit save, I have to re-add it again, as it gets removed. bletch Cliff Hudson James
|
|
|
Post by bletch on Feb 9, 2016 17:29:50 GMT -5
Thank you for the clarification. I will begin working to correct the problem.
|
|
drmskr
New Member
Posts: 8
Likes: 0
|
Post by drmskr on Feb 11, 2016 3:45:44 GMT -5
Thank you for the clarification. I will begin working to correct the problem. Whoot!! Thanks for the fix, awesome work.
|
|
|
Post by tineastwood on Feb 11, 2016 6:25:29 GMT -5
-BattlEye - for me BattleEye don´t work with ASM - a on/off would be nice
?AllowDeprecatedStructures=true * Halloween Structures (Placeable Jack-o-Lanterns, Scarecrows, etc) removed from Inventories unless ?AllowDeprecatedStructures=true commandline is used)
|
|
|
Post by bletch on Feb 11, 2016 8:07:06 GMT -5
-BattlEye - for me BattleEye don´t work with ASM - a on/off would be nice ?AllowDeprecatedStructures=true * Halloween Structures (Placeable Jack-o-Lanterns, Scarecrows, etc) removed from Inventories unless ?AllowDeprecatedStructures=true commandline is used) I am in the process of adding the Battleye option to ASM, though I have not been able to get it to work in the command line as Wildcard has suggested. I think there is a bug with it. We I set this option on my server, I am still able to connect to it with the old client. Anyway, the option is being included so if they do fix it, you can use it. It will be a checkbox to Enable/disable Battleye
|
|
nait
New Member
Posts: 1
Likes: 0
|
Post by nait on Feb 19, 2016 10:28:25 GMT -5
I am in the process of adding the Battleye option to ASM, though I have not been able to get it to work in the command line as Wildcard has suggested. I think there is a bug with it. We I set this option on my server, I am still able to connect to it with the old client. They changed the switch for it - though I don't recall where I read that. On the topic of switches, is there a definitive list of them? My game starts with the following and I'd like to know what each does (and what others are available): -BattlEye (depracated and replaced with something new that does the same thing?) -servergamelog (I think this stores chat? logs for RCON) -nosteamclient (doesn't check for a steam client if you're running a server from steamcmd ??) -game (I have no idea) -server (I have no idea - it works without it too) -log (logs... something... but what?) Thanks! EDIT: I found a couple of posts that state the new method of enabling BattlEye is "UseBattlEye=True" in the config file, or -UseBattlEye as a switch on the command line. I have not tested this.
|
|
Deleted
Deleted Member
Posts: 0
Likes:
|
Post by Deleted on Feb 19, 2016 13:32:57 GMT -5
I am in the process of adding the Battleye option to ASM, though I have not been able to get it to work in the command line as Wildcard has suggested. I think there is a bug with it. We I set this option on my server, I am still able to connect to it with the old client. They changed the switch for it - though I don't recall where I read that. On the topic of switches, is there a definitive list of them? My game starts with the following and I'd like to know what each does (and what others are available): -BattlEye (depracated and replaced with something new that does the same thing?) <-- see below-servergamelog (I think this stores chat? logs for RCON) <-- Enables server admin logs-nosteamclient (doesn't check for a steam client if you're running a server from steamcmd ??) <-- I believe this is correct
-game (I have no idea) <-- still looking-server (I have no idea - it works without it too) <-- still looking-log (logs... something... but what?) <-- still lookingThanks! EDIT: I found a couple of posts that state the new method of enabling BattlEye is "UseBattlEye=True" in the config file, or -UseBattlEye as a switch on the command line. I have not tested this. <-- Confirmed this is the method and is used by ASM.
|
|
skrosh
New Member
Posts: 6
Likes: 0
|
Post by skrosh on Feb 27, 2016 8:57:06 GMT -5
Missing configuration to beaver and Casteroides  And I don't see the saddle in engrams
|
|
Deleted
Deleted Member
Posts: 0
Likes:
|
Post by Deleted on Feb 27, 2016 9:04:11 GMT -5
Missing configuration to beaver and Casteroides  And I don't see the saddle in engrams If you're talking about ASM, it takes time for these things to make it into the program (as it's been stated numerous times before). However, it is in the vanilla game so if you're not seeing them then you might need to update your client/server. Since this has nothing to do with the OP's issue, I'm closing the thread because their issue was resolved. skrosh if you want to continue this please create your own thread.
|
|