strudo76 Posted March 18, 2018 Share Posted March 18, 2018 1 hour ago, Blackline said: My mod has only one cfg, and in that i am cloning the stock batteries and give them new names, properties etc: +PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:FOR[VenStockRevamp] if Ven* is not present, the cfg can run anytime during mm patchload using AFTER would prevent my cfg from being run at all, so no RealBattery using FOR somehow works without VEN, but i didn't check what happens if VEN is installed if Ven IS present: if i do nothing, my patch runs before (RealBattery is called before VenStockRevamp), i loose all models ingame, because VEN is path patching like this (although that path patching is done after my stuff ??? @PART[*]:FOR[zzzVSRPathPatch] ???) : @MODEL,* { @model ^= :^Squad/Parts/Electrical/z-100Battery/model:VenStockRevamp/Squad/Parts/Electrical/Batteries/model100: } if i use AFTER, it somehow works currently no idea if FOR works with VEN In everything i do, i'd love to take comments in how to improve, so don't hesitate giving feedback :-) Not an expert, but I think you'd need to have two different sections +PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:NEEDS[!VenStockRevamp] For what you want if Ven's isn't there, then another section @PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:AFTER[VenStockRevamp] For what you want if Ven's is there. Quote Link to comment Share on other sites More sharing options...
Blackline Posted March 18, 2018 Share Posted March 18, 2018 Can i "NEEDS" an AFTER ? Quote Link to comment Share on other sites More sharing options...
Starwaster Posted March 18, 2018 Share Posted March 18, 2018 20 minutes ago, Blackline said: Can i "NEEDS" an AFTER ? Yes Quote Link to comment Share on other sites More sharing options...
Blackline Posted March 18, 2018 Share Posted March 18, 2018 is this right then? @PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:[AFTER[VenStockRevamp]:NEEDS[VenStockRevamp]:] Quote Link to comment Share on other sites More sharing options...
Starwaster Posted March 18, 2018 Share Posted March 18, 2018 1 hour ago, Blackline said: is this right then? @PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:[AFTER[VenStockRevamp]:NEEDS[VenStockRevamp]:] No not like that, didn't realize that's what you meant @PART[*attery*]:HAS[@RESOURCE[ElectricCharge]]:AFTER[VenStockRevamp]:NEEDS[VenStockRevamp] You can also put the NEEDS before the phase; order doesn't matter there. But you can't nest them, no. Quote Link to comment Share on other sites More sharing options...
Blackline Posted March 18, 2018 Share Posted March 18, 2018 (edited) Sad Panda but as far as i understand it, AFTER and NEEDS is redundant, you can leave away NEEDS and it'll still do the same. Edited March 18, 2018 by Blackline Quote Link to comment Share on other sites More sharing options...
Electrocutor Posted March 18, 2018 Share Posted March 18, 2018 (edited) NEEDS allows multiple conditions and also allows a linear AND/OR logic AFTER allows only a single condition Basically, NEEDS is design to set conditions of dependency for when to include the patch whereas AFTER is designed to set patch order. Also, Ven's patch is named "zzzVSRPathPatch", not "VenStockRevamp". Edited March 18, 2018 by Electrocutor Quote Link to comment Share on other sites More sharing options...
careermode100 Posted March 22, 2018 Share Posted March 22, 2018 I am unable to download Module Manager 3.0.6 because somehow, there's a virus within the file. Is there a way to get rid of the virus? Quote Link to comment Share on other sites More sharing options...
sarbian Posted March 22, 2018 Author Share Posted March 22, 2018 1 hour ago, careermode100 said: I am unable to download Module Manager 3.0.6 because somehow, there's a virus within the file. Is there a way to get rid of the virus? On 3/16/2018 at 10:59 PM, sarbian said: Defender marked a bunch of KSP file as a virus : Update your definition manually and it should be gone: https://www.microsoft.com/en-us/wdsi/definitions Quote Link to comment Share on other sites More sharing options...
careermode100 Posted March 22, 2018 Share Posted March 22, 2018 Thanks, sarbian. Fixed it all up, and just finished downloading Module Manager. Quote Link to comment Share on other sites More sharing options...
BluBBa Posted March 23, 2018 Share Posted March 23, 2018 Please, where is the download button? Quote Link to comment Share on other sites More sharing options...
blowfish Posted March 23, 2018 Share Posted March 23, 2018 3 hours ago, BluBBa said: Please, where is the download button? Go to the first post in this thread, search for the word "download" using your browser's find function. Quote Link to comment Share on other sites More sharing options...
leatherneck6017 Posted March 23, 2018 Share Posted March 23, 2018 1 hour ago, blowfish said: Go to the first post in this thread, search for the word "download" using your browser's find function. Amazing! Quote Link to comment Share on other sites More sharing options...
Starwaster Posted March 23, 2018 Share Posted March 23, 2018 2 hours ago, leatherneck6017 said: Amazing! WHAT SORCERY IS THIS??? Quote Link to comment Share on other sites More sharing options...
FreeThinker Posted March 25, 2018 Share Posted March 25, 2018 Question, is there anyway in MM to detect if an specific RESOURCE_DEFINITION is already defined? Quote Link to comment Share on other sites More sharing options...
Psycho_zs Posted March 26, 2018 Share Posted March 26, 2018 Hi! I'm trying to use this selector: @PART[*]:HAS[@MODULE[ModuleDockingNode]:HAS[#nodeType[size0|size1|size2]]] It does not work. The problem seems to be in "size0|size1|size2" part. Is this a bug, or OR is not supported in HAS values by design? Quote Link to comment Share on other sites More sharing options...
sebi.zzr Posted March 26, 2018 Share Posted March 26, 2018 54 minutes ago, Psycho_zs said: Hi! I'm trying to use this selector: @PART[*]:HAS[@MODULE[ModuleDockingNode]:HAS[#nodeType[size0|size1|size2]]] It does not work. The problem seems to be in "size0|size1|size2" part. Is this a bug, or OR is not supported in HAS values by design? "nodeType" is inside "ModuleDockingNode" and why use that since you already selected all types with @PART[*]:HAS[@MODULE[ModuleDockingNode] Quote Link to comment Share on other sites More sharing options...
Psycho_zs Posted March 26, 2018 Share Posted March 26, 2018 1 minute ago, sebi.zzr said: "nodeType" is inside "ModuleDockingNode" Yes it is, this syntax is correct from the hierarchal standpoint. 3 minutes ago, sebi.zzr said: and why use that since you already selected all types I want to select only stock-compatible docking ports. Quote Link to comment Share on other sites More sharing options...
Warezcrawler Posted March 26, 2018 Share Posted March 26, 2018 20 hours ago, FreeThinker said: Question, is there anyway in MM to detect if an specific RESOURCE_DEFINITION is already defined? In what context. Like create it if not exists or from another node/module, like add this module only if the specific "RESOURCE_DEFINITION" exists or something else? Quote Link to comment Share on other sites More sharing options...
sebi.zzr Posted March 26, 2018 Share Posted March 26, 2018 7 minutes ago, Psycho_zs said: Yes it is, this syntax is correct from the hierarchal standpoint. @PART[*]:HAS[@MODULE[ModuleDockingNode[@nodeType[size0|size1|size2]]]] Quote Link to comment Share on other sites More sharing options...
FreeThinker Posted March 26, 2018 Share Posted March 26, 2018 2 minutes ago, Warezcrawler said: In what context. Like create it if not exists or from another node/module, like add this module only if the specific "RESOURCE_DEFINITION" exists or something else? I like know if I can declare it without hurting any other mod resource definitions Quote Link to comment Share on other sites More sharing options...
Psycho_zs Posted March 26, 2018 Share Posted March 26, 2018 20 minutes ago, sebi.zzr said: @PART[*]:HAS[@MODULE[ModuleDockingNode[@nodeType[size0|size1|size2]]]] Whoa, how is that supposed to work? 7 minutes ago, sebi.zzr said: @nodeType nodeType is a value, so it should be #nodeType. Anyway, I've checked your syntax with both #nodeType and @nodeType. I've also used "size1|size2" selector, but nodes with size0 were also affected, so something is wrong here. Quote Link to comment Share on other sites More sharing options...
leatherneck6017 Posted March 26, 2018 Share Posted March 26, 2018 2 hours ago, Psycho_zs said: I'm trying to use this selector: @PART[*]:HAS[@MODULE[ModuleDockingNode]:HAS[#nodeType[size0|size1|size2]]] It does not work. The problem seems to be in "size0|size1|size2" part. Is this a bug, or OR is not supported in HAS values by design? 57 minutes ago, Psycho_zs said: I've also used "size1|size2" selector, but nodes with size0 were also affected, so something is wrong here. How about this? @PART[*]:HAS[@MODULE[ModuleDockingNode],[#nodeType[size0|size1|size2]]] That way you get rid of the other HAS and replace it with AND. Quote Link to comment Share on other sites More sharing options...
Psycho_zs Posted March 26, 2018 Share Posted March 26, 2018 2 minutes ago, leatherneck6017 said: How about this? @PART[*]:HAS[@MODULE[ModuleDockingNode],[#nodeType[size0|size1|size2]]] That way you get rid of the other HAS and replace it with AND. nodeType is inside ModuleDockingNode. With this selector it would probe for it in root. Quote Link to comment Share on other sites More sharing options...
leatherneck6017 Posted March 26, 2018 Share Posted March 26, 2018 3 minutes ago, Psycho_zs said: nodeType is inside ModuleDockingNode. With this selector it would probe for it in root. TBH, I've never had much success with using OR with MM. The last time it gave me a lot of trouble I just added individual selectors for what I was trying to do. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.