just wanted to confirm - still broken.
you disabled the crafting of those sets when they were hitting 600, why not disable the shield while you investigate?
just disable the shields.
you know, if you could convey something to the team on the next SCRUM (or whatever you are using), can you tell them, that Asaad from Denmark wants you to know that from the outside it all looks very amature. And as an engineer who gets high on doing good work and very dark and self critical when work is less than optimal, or god forbit negative to the business, i ask you to consider your positin and passion in it, as it is not helping the game, WFH, half doing the tasks, hot potatoing issues, always “next week”, always “put a marker”, can you please just stop, managment should just put an end to this, and if managment is the issue then the employees need to voice their concern.
I can only imagine the stress that the engineers have to go through every patch cycle, having to work weekends or holidays, this is not ok. its NOT OK.
it takes minutes to make a test to go through all the crafts in the game and rolls them as a regression test and check kappa vs last verssion, it is trivial, we do it in silicone development all the time. the lack of this is un-acceptable. its a 1d regression, run all recipies with preset of params. just doing that will reveal 99% of the issues . its so easy to do.
Char class
equipment (add sets here whenever you are bored)
inventory =( loop on all recipies and read needed mats (save as resultMATS, save resultRecipies and compare this too as some recipies are uncraftable - else u miss a data point) - should be a list of mats and ammount per. THIS IS UR FIRST KAPPA - perform a diposition on all triggers.) Then (add all mats from resultMATS to char.inventory)
inventory = all items from crafts - save as resultCRAFTED - this is ur second KAPPA . add can run with perks.ignore = true or not, depends on patch cycle, actually run on both and layer them to see stdev of randomness beteween patches.
thats it, this is your 1st regression. u KAPPA on resultsCRAFTED.ammount by recipie from resultRecipies. can start adding resultCRAFTED.raity/perks/etc…
it will be so cool to start making those data points, colelcting them and sharing them even. (like the most intresting thing to come out of a dev blog is actually knowing they are logging mutation complition times (of course no idea what to do when they see a low number “we are investigating” lol, but its ok, we are all learning)
there is no way for me to better my experience in the game at this moment other than to start taking an active role and see if i can help you guys actually get this system of the ground.
I am offering my services as consultant. I specialise in big data and statistical analysis. e-mail me.
please get this to the team or at least the program manager, because these things are standard in an industry with releases.
and no your game is not complicated with many systems its just a bunch of 1d params.
