Home » MODDING HQ 1.13 » v1.13 Coding Talk » (New) Common Attachment Framework (new title; was The NAS Receiver)
Re: The NAS Receiver[message #303880]
|
Wed, 25 April 2012 02:21
|
|
Madd_Mugsy |
|
Messages:634
Registered:July 2005 Location: Canada |
|
|
Exceptions are still possible, and Attachments.xml and Launchables.xml will remain in play. In fact I don't see any way around having that per-item level of flexibility.
My hope with this new approach is to catch maybe 80% of the attachments, and especially those that are common across many items.
Quote:
You've already thought about AK-receivers, so you'd obviously need a distinction for ARs between NATO and AK. Perhaps even more (chinese stuff?). Same for sniper rifles (NATO vs. WP bc of scopes (PSO-3) ).
I'm thinking I can get away with just tags for AK / NATO receivers (in different sizes?) and then OR them with the tags for the weapons.
One possible issue is that I'm not sure if there's ever a case where you'd have a reason to limit the number of attachments. If so, then the bitwise approach is less ideal.
Quote:
How would you handle new rail system vs. 'unrailed' guns? I mean, there might be attachments that fit on a M16A4 but do not fit on a M16A1.
Right, so in this case, we'd see that the M16A1 receiver is "Assault Rifle+NATO" or something, and M16A4 is "Assault Rifle+NATO+RIS".
Quote:
Magwell adapters only fit for a specific caliber. How would you handle that?
Foregrips wouldn't make sense on single-shot shotguns, but would be useful on automatic shotguns, so you'd need 2 flags there...
These are some good examples of exceptions that would require keeping the old structure in place at the same time.
Quote:
SMGs that already have a built-in silencer won't accept a new one, so you'd need new tags there. This is under the assumption that the silencer effect has been calculated into the weapon stats, if its just a inseparable default attachment than your system is ok.
Silencers are an interesting wrinkle, in that they apply to many weapons, but also cannot be applied to all weapons. An extra tag doesn't really cut it here either, since the tags are inclusive rather than exclusive. Might be able to do something in combination with nasAttachmentClass...
Perhaps the approach to take here is to implement a list of attachments that are not compatible with a given item?
Quote:
Don't get me wrong, I like your idea. I guess what I'm saying is that once this gets adopted, people will soon find guns that are in some way distinct, and you'll therefore need a lot of new flags. If you add new flags afterwards, you'll have a ton of work.
Yep - hence keeping the old way too But I do agree that we should nail down a list of initial receiver values as best we can first.
If anyone has any good ideas for an initial set of possible receiver values, feel free to post 'em.
Report message to a moderator
|
|
|
|
|
|
(New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: The NAS Receiver
By: Flugente on Wed, 25 April 2012 01:45
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: Flugente on Wed, 25 April 2012 02:49
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: Wil473 on Wed, 25 April 2012 18:51
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: Wil473 on Thu, 26 April 2012 10:07
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: Wil473 on Thu, 26 April 2012 16:48
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: Wil473 on Thu, 26 April 2012 18:16
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
|
|
|
Re: The NAS Receiver
By: JMich on Fri, 27 April 2012 10:50
|
|
|
(New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Fri, 27 April 2012 18:19
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Sun, 29 April 2012 23:20
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Sun, 03 June 2012 18:14
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Thu, 07 June 2012 22:38
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Sun, 02 August 2015 01:44
|
|
|
Re: (New) Common Attachment Framework (new title; was The NAS Receiver)
By: Wil473 on Sun, 07 April 2013 19:19
|
Goto Forum:
Current Time: Fri Jan 10 10:31:48 GMT+2 2025
Total time taken to generate the page: 0.01435 seconds
|