RHS Feedback - AFRF |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001344 | AFRF | [All Projects] General | public | 2015-11-02 13:32 | 2015-11-03 17:50 |
|
| Reporter | ruPaladin | |
| Assigned To | PuFu | |
| Priority | none | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Is it a wish/request? | No |
| RHS version | |
| Arma 3 version | 1.52 |
| Did you used any other mod when the error occurred? | No |
| Which mods? | |
|
| Summary | 0001344: Weapon classnames inconsistency |
| Description | Some weapons in RHS:USAF have old classnames (misses "_weap_"). For example, "rhs_m4a1_eotech", "rhs_m4_acog_usmc", "rhs_m4a1_m203_acog_usmc". Instead of "rhs_weap_m4a1_eotech", "rhs_weap_m4_acog_usmc", "rhs_weap_m4a1_m203_acog_usmc". |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-11-02 13:32 | ruPaladin | New Issue | |
| 2015-11-02 13:32 | ruPaladin | Description Updated | bug_revision_view_page.php?rev_id=1215#r1215 |
| 2015-11-02 13:40 | ruPaladin | Description Updated | bug_revision_view_page.php?rev_id=1216#r1216 |
| 2015-11-02 13:53 | PuFu | Note Added: 0002714 | |
| 2015-11-02 13:53 | PuFu | Status | new => closed |
| 2015-11-02 13:53 | PuFu | Assigned To | => PuFu |
| 2015-11-02 13:53 | PuFu | Resolution | open => won't fix |
| 2015-11-02 13:53 | PuFu | Note Edited: 0002714 | bug_revision_view_page.php?bugnote_id=2714#r1218 |
| 2015-11-02 13:54 | PuFu | Resolution | won't fix => suspended |
| 2015-11-02 20:10 | ruPaladin | Note Added: 0002718 | |
| 2015-11-03 12:00 | PuFu | Note Added: 0002721 | |
| 2015-11-03 16:10 | ruPaladin | Note Added: 0002722 | |
| 2015-11-03 16:11 | ruPaladin | Note Edited: 0002722 | bug_revision_view_page.php?bugnote_id=2722#r1224 |
| 2015-11-03 17:50 | PuFu | Note Added: 0002723 | |
|
Notes |
|
|
(0002714)
|
|
PuFu
|
|
2015-11-02 13:53
|
|
in theory, we'd like to have everything consistent: that said - we won't be changing any of the class names mid development, because everything that is dependent on these classes so far, from missions to scripts will break.
|
|
|
|
|
|
Wrong position. We will get more mods in time and it will be harder to change classnames in future. You tries to build something big on a quicksand. |
|
|
|
(0002721)
|
|
PuFu
|
|
2015-11-03 12:00
|
|
|
not your place to judge. when some of the descriptions and layout in the editor was changed there was turmoil. imagine breaking every mission and 3rd party config out there. the consistency alone doesn't justify the negative impact |
|
|
|
(0002722)
|
|
ruPaladin
|
2015-11-03 16:10
(edited on: 2015-11-03 16:11) |
|
I just want to point that someday you will do that. It will be better to do that earlier. You did that earlier, I remember that you changed several classnames (connected with m320 and one more time with another classname). I am working on mod and found that I have to find a workaround because of that inconsistency.
I don't want to give advices. But you can make mirrored classes with scope=1 (old one's). And delete them in 3-4 months.
For now every new update make it harder, you make more inherited classes with them.
It is your mod and your rights. I accept any decision.
|
|
|
|
(0002723)
|
|
PuFu
|
|
2015-11-03 17:50
|
|
|
duplication of existing classes with consistent class names could be a solution that might be worth investigating |
|