Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Annual public releases of sanitized code
#21
(09-13-2017, 09:23 AM)Mordent Wrote: Include sensible documentation detailing the changes, and respond to feedback appropriately.

Big plus on this. You might notice Mordent had some of the nicest writeups on how their patches operated, and now they seem to be a coder? Correlation does not imply causation, but...

(09-17-2017, 06:56 AM)Crystalwarrior Wrote: Yeah not to mention that recently implemented phobias worked perfectly on my branch and yet they're still broken on the current code server and I cannot do anything to even begin trying to fix it. It's frustrating.

They're working fine for me on live!

(09-17-2017, 05:58 AM)amaranthineApocalypse Wrote: Unless you have the full code for the feature and all of it's dependencies, you cannot compiler test or playtest your feature properly. And even if you have it, implementing it, testing everything, then removing the non-public code every single time you want to push it to your branch is a hell of a lot of work

Can you name a case where you would need the full code and not just the associated procs/args/variables to pass? If you can name it and the idea is of merit, talk to a coder about getting more of the behind-the-scenes code. Also, if you're dealing with secret stuff just put it in the exploits section like we've said for all secret content.
Reply


Messages In This Thread
RE: Annual public releases of sanitized code - by ZeWaka - 09-18-2017, 11:02 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)