Jump to content

To Mod Devs who release their mods during Pre-Release


Stone Blue

Recommended Posts

To those Mod Devs who release, or at least post accessible links ON A PUBLIC FORUM, of pre-release versions of their mods:

I understand that you dont want to deal with all the "people" who pester you with comments/requests/complaints about issues with your mod, who should know full well that EVERYTHING, (mods as well as KSP itself) is in limbo and may NOT work during the pre-release period, and possibly even for the next two or three updates of KSP...

HOWEVER, DO NOT GET YOUR UNDIES IN A BUNCH, AND BE SURPRISED WHEN PEOPLE DOWNLOAD YOUR, BUGGY, POSSIBLY NOT WORKING MOD, OR EVEN IF YOUR MOD IS WORKING PERFECTLY IN YOUR EYES, BUT SHOULDNT BE USED BECAUSE KSP OR SOMEONE ELSES MOD IS NOT READY FOR RELEASE, VIA A LINK WHICH YOU PROVIDED, IN A PUBLICLY ANNOUNCED FORUM POST, HAILING YOUR ALMIGHTY MOD AS NOW PRE-RELEASE COMPATABLE, AND THEY START POSTING EVEN SANE, HELPFUL COMMENTS AND DISCUSSION ON YOUR THREADS.

DO NOT BE SURPRISED WHEN YOUR THREADS GET CLUTTERED BECAUSE YOU DECIDED TO RELEASE SOMETHING DURING PRE-RELEASE, KNOWING FULL WELL POEPLE ARE GOING TO JUMP ALL OVER IT.
THEN AT THE SAME TIME, OUT OF THE OTHER SIDE OF YOUR MOUTH, COMPLAIN THAT MODS (INCLUDING YOUR OWN), SHOULD NOT BE USED AT ALL WITH PRE-RELEASE VERSIONS OF KSP.

IF YOU DONT EVEN WANT HELPUL DISCUSSION, SUGGESTIONS, OR YES, "BUG REPORTS", BY PEOPLE WHO DO KNOW AT LEAST A LITTLE ABOUT WHAT THEY ARE DOING, THEN I SUGGEST YOU TAKE THE RESPONSIBILITY FOR YOURSELF, AND MAKE THE DECISION TO EITHER,

A) GO AHEAD AND PRE-RELEASE IT KNOWING FULL WELL YOUR GONNA HAVE LOTS OF DISCUSSION, GOOD AND BAD

or

B) HOW ABOUT YOU NOT PUBLICLY RELEASE IT, THEN *ITC* WHEN THE DRAMA STARTS

AND IF YOU DECIDE on B), MAYBE IT WOULD BE A GOOD IDEA FOR YOU TO TEMPORARILY LOCK DOWN YOUR RELEASE THREADS SO THE PEASANTS CANT BUG YOU UNTIL YOU'RE READY TO BE BUGGED??

If the reason you publicly post pre-release versions of your mods, is so OTHER mod devs who depend or interact with YOUR mod, can begin their own work as soon as possible, may I suggest sharing those pre-release versions amongst other mod devs PRIVATELY, over PMs, or some other PRIVATE means??

Now, I know I have probably ticked off, upset, or at least entertained a lot of respected mod devs with this rant... But I felt it needed to be said during this feverish, high-tension period during pre-release...

I'll also say that, the way this, and the last pre-release went, I would rather see Squad go back to NO "pre-release" at ALL, or have something where people have to specifically sign up, or justify their ability to help with serious bug tracking... OR, I would like to see all you mod devs who have popular mods, just keep everything to yourselves until AFTER a FULL release hits

Thank You... Let the flaming begin :)

 

Edited by Stone Blue
Link to comment
Share on other sites

...This is in relation to something, I'm sure.  I'm not sure what, though.  Every mod thread I follow has either not released for 1.2, and been happy with that, or is doing beta testing for their mod in 1.2, and is happy with that.

Link to comment
Share on other sites

Oh Darn it. SB just has his panties in a twist because he got growled at ("pre-release, what you expect") for reporting a bug in a dev version... in a "dude, this is totally broken" tone. All caps rant over-reaction much.

N.B: paraphrasing from memory, no quoting on mobile.

 

 

 

Link to comment
Share on other sites

5 minutes ago, steve_v said:

Oh Darn it. SB just has his panties in a twist because he got growled at ("pre-release, what you expect") for reporting a bug in a dev version... in a "dude, this is totally broken" tone. All caps rant over-reaction much.

Perhaps you should not paraphrase from memory, since that is exactly what did NOT happen.

Link to comment
Share on other sites

No useful content in this thread, and it's only going to go downhill from here.  Locking before it gets any worse.

To the OP:  With all due respect, this thread is unnecessary, for a variety of reasons:

  • Mod authors are perfectly within their rights to decide what they want to do.  They may release for 1.2 while it's in pre-release.  Or they may not.  It's completely up to them.  It's their mod, after all, not yours-- and they're perfectly capable of making their own decisions.  So any exhortations from you about what they should do with their mods are, at best, superfluous.  If there are any mod authors out there who would like your advice as to what to do with their mod's release schedule, I'm sure they will ask you.
  • Any mod author (or, indeed, any thread OP) who wishes to lock their thread can always ask the moderator team and we're happy to oblige.  Again, it's the mod author's choice.
  • If there's any concern about users "pestering" mod authors for updates:  Also not a problem.  For one thing, it's against the forum guidelines (specifically, rule 2.3.f), so if anyone sees egregious mod-pestering, feel free to report the post and the moderator team can take any action that may be required.  So there's a mechanism for this already, no need to tell people how to run their threads.
  • TELLING PEOPLE WHAT TO DO IN ALL CAPS SOUNDS LIKE SHOUTING AND IS GENERALLY CONSIDERED POOR FORUM ETIQUETTE.  IT TENDS TO ANNOY PEOPLE AND MAKE THEM STOP READING YOU.  THEREFORE, IF YOUR OBJECTIVE IS TO ACTUALLY PERSUADE ANYBODY OF ANYTHING, IT IS PERHAPS BEST AVOIDED.

Thank you for your understanding.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...