You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
With increasing mod compatibility efforts there, my ModOps get complex only because I want to supress not found warnings.
In the following example I add a product to storage lists, but only if it's not added already (shared product).
So, not finding a storage list where the product is missing is an expected scenario and should not lead to a warning.
To avoid it I create a fake fallback Asset so that at least one list is always found, and remove that Asset later.
<!-- create fallback container to avoid warnings in case the product is already available -->
<ModOpType="addNextSibling"GUID="120055">
<Asset>
<Template>fallback</Template>
<Values>
<Standard>
<GUID>1500010221</GUID>
</Standard>
<ProductStorageList>
<ProductList>
<Item />
</ProductList>
</ProductStorageList>
</Values>
</Asset>
</ModOp>
<!-- StandardProductList,StandardMarketplaceModerateStorageList: after bricks -->
<ModOpType="addNextSibling"GUID="120055,120057"Path="/Values/ProductStorageList/ProductList/Item[Product='1010205' and not(../Item/Product='1500010825')] | //Values[Standard/GUID='1500010221']/ProductStorageList/ProductList/Item[last()]">
<Item>
<Product>1500010825</Product>
</Item>
</ModOp>
<ModOpType="remove"GUID="1500010221" />
The code would be a lot simpler, if we had a flag like disableNotFoundWarning I can set individually per ModOp.
The text was updated successfully, but these errors were encountered:
With increasing mod compatibility efforts there, my ModOps get complex only because I want to supress not found warnings.
In the following example I add a product to storage lists, but only if it's not added already (shared product).
So, not finding a storage list where the product is missing is an expected scenario and should not lead to a warning.
To avoid it I create a fake fallback Asset so that at least one list is always found, and remove that Asset later.
The code would be a lot simpler, if we had a flag like
disableNotFoundWarning
I can set individually per ModOp.The text was updated successfully, but these errors were encountered: