-
PraiseLuka
On
2017-05-25 06:01:32
-
I'm not "following" the backlash wave because... well... I was there before the backlash was even a thing.
here is an interesting post of mine: dah post
Notice how it's before the sage poll was made? yeah... I suspected #2 was going to be a thing before it happened.
To be clear, I am against Xserver sage, it's just that I have good rational reasons as opposed to certain thoughtless sky-dive to conclusion reasons.
I never said I was smart, all I said was that some people aren't based on what they said. There is a HUGE difference there. I mean, I take no pleasure by having more money than the homeless(well, the REAL homeless...) so...
4. I'm a programmer, so I know exactly how easy it is to change such things. I should be able to implement all 3 changes that I proposed between 20 minutes and a day, depending on how it is coded (assuming it's written in a commonly used language). That said, as far as the "increase reward goes", I can only guarantee increased reward for the top 3 in that time frame to at least preserve the reward per person quota. It may or may not be easy to increase the number of reward recipient and even if I did, changing the interface to make it "look nice" would take far longer. That said, someone did have an awesome idea: ramp up the "winning side" reward. That would work perfectly and probably far easier, just substitute one item for another and everything would be fine, in interface change required (thou it might need to be changed in a couple place to make everything line up.)
Algorithm... there aren't enough player in the game to make "algorithms" a thing. Given the small data size, the simplest, brute force and inefficient algorithm can be used unless the servers are running on commodore 64s. And frankly I don't intend to change the "algorithm" just the variables.
Well, at least that's what I'd expect if they follow any kind of good coding practice where sage is its own "thing" that have its own section of code (and preferably the player placement in its own method/function). It would indeed be difficult if everything is in one code blob....
In any case, they probably aren't going to change the code because Oasis can't and the devs won't. Thou seeing how most lesser ptws are going to be *er punched in section 1 sage, maybe they'll rage quit and that will convince them to rethink their strategy. But maybe the arms race of top ptw will cover that, whoever knows.
If you have 20 sprints worth of backlog to implement in order to catch up to the master branch ( China ), how you are going to plan and prioritize issues that are not on the board ? Like new ideas that don't exist in the master branch ?
If it were up to me, I would skip versions 2.1 and 3.0 and go straight to 4.0 parity 1:1.But these decisions have different business values and have to follow a certain workflow.
Don't know how big the team is either to do a full release in 1 week time ( that's fast for production ).