Steps to remember when you call to nerf something or make changes
Posted: Wed Jul 07, 2021 11:57 am
All of the calls to nerf or change anything do forget that you need a person who is:
1: Capable of making that change. Understands enough code to make the fix.
2: Navigating the atrocious code that volunteer devs have created over multiple years. I am not a coder, but I've heard from multiple people how disastrous the code on BG is (BGTSCC is not alone, most servers have messy code with unpaid and very passionate volunteers who don't understand basics like linking to a 2DA instead of hardcoding everything). There are unintended consequences if you change things when the code is not clean and those consequences are not always apparent.
3: Has the time to code those changes. Depending on ability and complexity, time is an unknown variable and a task could take minutes to weeks or months. You don't want to fix something only to screw up something somewhere else.
4: Is actually interested in making those changes. Coders are volunteers and often people treat them like crap or as their personal servants. Get a dev excited about a change and you can get things done.
QC are not always coders, and not all devs are coders, to my understanding (some are builders, for instance).
You can say a change is not complex. Maybe it's not. But sometimes it is and you don't know until you are in the thick of it.
Source: Wife of someone who does brilliant NWN2 dev work. See an incomplete list of his projects here (Google doc). One of my favorites is ammo recovery for arrows/bolts.
I am reluctant to chime in on nerf discussions precisely because unless you get a dev on board to do work then you're just shouting into the wind.
1: Capable of making that change. Understands enough code to make the fix.
2: Navigating the atrocious code that volunteer devs have created over multiple years. I am not a coder, but I've heard from multiple people how disastrous the code on BG is (BGTSCC is not alone, most servers have messy code with unpaid and very passionate volunteers who don't understand basics like linking to a 2DA instead of hardcoding everything). There are unintended consequences if you change things when the code is not clean and those consequences are not always apparent.
3: Has the time to code those changes. Depending on ability and complexity, time is an unknown variable and a task could take minutes to weeks or months. You don't want to fix something only to screw up something somewhere else.
4: Is actually interested in making those changes. Coders are volunteers and often people treat them like crap or as their personal servants. Get a dev excited about a change and you can get things done.
QC are not always coders, and not all devs are coders, to my understanding (some are builders, for instance).
You can say a change is not complex. Maybe it's not. But sometimes it is and you don't know until you are in the thick of it.
Source: Wife of someone who does brilliant NWN2 dev work. See an incomplete list of his projects here (Google doc). One of my favorites is ammo recovery for arrows/bolts.
I am reluctant to chime in on nerf discussions precisely because unless you get a dev on board to do work then you're just shouting into the wind.