Open PandaDriver156 opened 4 years ago
I like the idea on having the weapons/loadouts, but my issue is that the current operators.json file is getting quite long already and quite difficulty to work with. So my current plan is to have the operator data (like metadata & loadout) seperated from the weapons so we can reuse weapon data for other operators as well.
So my plan is to have two different root folders:
operators
: Contains icon, images & metadata for the operatorweapons
: Contains each weapon object as a seperate JSON fileI've pushed the new branch @feat/loadouts
where i've restructured already the icons to be in their seperate folders. Feel free to clone that branch and do your changes there.
That sounds like a nice structure, but the issue with it is that the loadout for weapons are not the same for every operator. For example, both Doc and Oryx has an MP5, but Doc can equip it with an ACOG while Oryx can't.
Oh, i didn't know that. Then having a loadout.json
file inside the operator folder should be the easiest solution with the different possible weapons (+attachments) & gadgets. One thing we also could do is seperate the base weapon and extend the loadout with the different possible attachments, so we can update the weapon data independently from the operator specific data.
What do you think is the better approach?
I like the original idea on having the weapons separated from the operators, so my suggestion would be to have all the weapons and their data in the weapons folder, with the attachments included. And for such operators who has a different weapon loadout, we "overwrite" the attachments in the operator's json file. That way we could avoid having to add attachments to all the operators separately. Also, it's not common that a loadout differs, other than Oryx, i can't say anyone else who has the same issue.
@PandaDriver156 Just to keep you updated, i'm still working on this but i'm quite busy right now with other stuff so it might take a while to get finished.
In Y7 all primary weapons will have all 1x scopes (source)
Hey @PandaDriver156, I know it's been more than two years :D, but are you still interested in this? I'm planning to publish new project soon which will be used as dependency for my r6api.js and it could really use operator loadouts!
I already have array of objects for every weapon, that's why I'm using just a weapon slug in operator object. Will take me a while to do that just by myself for every operator in game.
Hey @danielwerg, you got the timing right, just started playing Siege recently again :smile:
are you still interested in this?
If you mean interested in helping you then yes, i'd be happy to do so.
I'd like to add loadouts to all operators. I think it's a big change (and a lot of work for me) so it's better to ask whether it would be approved or denied.
Here is an example on how an operator object would look like: