plott1964 Posted March 22 Posted March 22 (edited) As discussed here: ...I think it would be a great idea for ED offer the possibility of a Closed "unofficial" Mod Maker Beta Testing Group that would allow a mod maker to test out their mods just prior to ED's update. I am not suggesting that ED stop the posting of an update to ensure a mod maker is ready, just to provide them with a leg up in the development process so they can either fix or be made aware of bugs causing their mods to not work correctly. I would propose a special user account (closed) that ED vets to make sure the mod maker is legitimate and has a history with ED or making mods. ED would make an announcement to the special user group a week or so before the actual deployment to allow a little time for adjustments. There are several mod makers who would benefit from some a situation and the community would be better served. Edited March 22 by plott1964 5 3 PC specs: Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/Multiple M.2 SSD Drives/T.Flight HOTAS X/HP Reverb G2
MAXsenna Posted March 22 Posted March 22 This would be absolutely amazing for both mod makers and the rest of the community! Take my upvote!
joey45 Posted March 24 Posted March 24 (edited) Will defo help with damage control after patches.. Edited March 24 by joey45 1 The only way to make sense out of change is to plunge into it, move with it, and join the dance. "Me, the 13th Duke of Wybourne, here on the ED forums at 3 'o' clock in the morning, with my reputation. Are they mad.." https://ko-fi.com/joey45
Hammer1-1 Posted March 24 Posted March 24 I cant imagine this would ever succeed but Id like to place an alternative idea. Would be great if ED can give modders a heads up on what to expect in next patches, but make their own forum that only confirmed community modders can join and discuss with ED as sort of a cooperation program. 2 1 Intel 13900k @ 5.8ghz | 64gb GSkill Trident Z | MSI z790 Meg ACE | Zotac RTX4090 | Asus 1000w psu | Slaw RX Viper 2 pedals | VPForce Rhino/VKB MCE Ultimate + STECS Mk2 MAX / Virpil MongoosT50+ MongoosT50CM | Virpil TCS+/ AH64D grip/custom AH64D TEDAC | Samsung Odyssey G9 + Odyssey Ark | Next Level Racing Flight Seat Pro | WinWing F-18 MIPS | No more VR for this pilot. My wallpaper and skins On today's episode of "Did You Know", Cessna Skyhawk crashes into cemetery; over 800 found dead as workers keep digging.
Abburo Posted March 28 Posted March 28 Wishful thinking, but 100% unrealistic ! Say, that tester finds out some issues with a mod... the mod dev is on the sunny beach... or just busy with some booze... what should be done :D. Don't get me wrong, i like the mods... but we need to set the correct expectations. Romanian Community for DCS World HW Specs: AMD 7900X, 64GB RAM, RTX 4090, HOTAS Virpil, MFG, CLS-E, custom
Ahmadrizik Posted March 28 Posted March 28 Sounds like a great idea mate! Passed it over to ED ppl on Discord 1
Solution MAXsenna Posted March 29 Solution Posted March 29 On 3/28/2025 at 7:23 PM, Abburo said: Say, that tester finds out some issues with a mod... the mod dev is on the sunny beach... or just busy with some booze... what should be done :D. Don't get me wrong, i like the mods... but we need to set the correct expectations. You missed the point. The Beta testers have access to a pre-release. I have no idea how often that's updated. The Modders would have access to the same build, and are able to test themselves, not relying on testers. If they discovers some issues, they can either fix that, with or without ED, and/or give the community a heads up. They could even tell the community they're going away. We sort of know the patch cycle now, so it wouldn't be too hard to anticipate when a "conflicting" patch drops. 1
plott1964 Posted March 31 Author Posted March 31 (edited) I will also add to the suggestion that I do not propose such an opportunity (for the mod developer) to be a type of collaboration situation. "Hey ED fix your code to make my mod work." would not be the type of interaction afforded a Mod Maker Beta Testing Group member. The only basic interaction opportunity provided should be one of a "fly on the wall" type of testing. Again, the goal would be (as stated by @Joey45) "help with damage control after patches". Edited March 31 by plott1964 1 PC specs: Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/Multiple M.2 SSD Drives/T.Flight HOTAS X/HP Reverb G2
Recommended Posts