Reusing the same pngs for different "traits" #301
Replies: 1 comment 1 reply
-
From what I understand, you want to be able to have two Also, the generator skips duplicate trait_types, so you will need a config like:
while not ideal for your use case, after the generation, do a find and replace to change 'Items2' => 'Items' To setup the incompatible mappingin config.js, you would need to loop over the Items directory, create an incompatible mapping, then push it to
then, before them incompatible, grab the zflag, and clean name function from main.js (easiest is to probably copy paste it), rarity delimiter will need to move up in the file
finally, create the incompatible maps by looping over the read items
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I'm interested in using the same pngs in a folder for more than 1 trait. However I would like the engine to be aware if a png was already selected by the previous layer.
For example, lets say I have:
layers/common-items/asset01#33.png
layers/common-items/asset02#33.png
layers/common-items/asset03#33.png
with the following config:
const layerConfigurations = [ { layersOrder: [ { name: "common-items" trait: "Items"}, { name: "common-items" trait: "Items"}, ], } ]
How can I have the engine say select
asset01#33.png
for the first layer and prevent it from selecting the same one for the second layer?What would be the best route for this if possible?
Beta Was this translation helpful? Give feedback.
All reactions