Thoughts on end game raiding

[Mblake81]

Originally Posted by Sonderbeast [You must be logged in to view images. Log in or Register.]

end game mechanics seem fine to me

coo

[aaezil]

"Thoughts on end game raiding"

It sucks here and you will waste lots of 16 hours at a time of your life on essentially nothing...

I would suggest a more healthy hobby

[aaezil]

why are you weirdos arguing about off topic stuff in this thread lmao?

[ZiggyTheMuss]

This is super fascinating, guys. Thank you for sharing it here instead of in PMs.

[baakss]

Hey! That sure is simple.

You’ll revisit the issue on the next iteration of the server because you don’t understand why change management is important. Or God forbid you have a DB rollback, then you get to do this again, if you remember it. Or maybe you make a typo when you point and click in prod because you were too lazy to write a script. Or you miss a couple of records you updated in Dev.

Or you could just take the time to do it properly.

You do it your way though, kiddo. Just on your own server though because it’s not classic.

[Kika Maslyaka]

Originally Posted by baakss [You must be logged in to view images. Log in or Register.]

Hey! That sure is simple.

You’ll revisit the issue on the next iteration of the server because you don’t understand why change management is important. Or God forbid you have a DB rollback, then you get to do this again, if you remember it. Or maybe you make a typo when you point and click in prod because you were too lazy to write a script. Or you miss a couple of records you updated in Dev.

Or you could just take the time to do it properly.

You do it your way though, kiddo. Just on your own server though because it’s not classic.

a) back up Db before doing changes - point & click
b) write an sql line that adjusts not 1 mob but 12 and save it somewhere - 1 min
c) run your sql line - 10 seconds
d) back up DB after doing the changes - point & click

Are we done?

[baakss]

Originally Posted by Kika Maslyaka [You must be logged in to view images. Log in or Register.]

a) back up Db before doing changes - point & click
b) write an sql line that adjusts not 1 mob but 12 and save it somewhere - 1 min
c) run your sql line - 10 seconds
d) back up DB after doing the changes - point & click

Are we done?

I am now 100% certain you have no idea what you’re doing.

When you create the new server, green or whatever, out of the hundreds/thousands of changes, how do you remember that this change was applied?

How do you know whether this change should be applied at the beginning of Velious and not this point in the timeline?

How do the other devs on the team know what you just did?

You also left out testing, conveniently. And did you do this directly in production?

[Kika Maslyaka]

Originally Posted by baakss [You must be logged in to view images. Log in or Register.]

I am now 100% certain you have no idea what you’re doing.

When you create the new server, green or whatever, out of the hundreds/thousands of changes, how do you remember that this change was applied?

How do you know whether this change should be applied at the beginning of Velious and not this point in the timeline?

How do the other devs on the team know what you just did?

You also left out testing, conveniently. And did you do this directly in production?

Except - I don't care about those OTHER changes. I don't care about timeline changes. I don't care about Green shit. I was asked on implementation of specific feature - I got it under 5 min. And testing in this case is done by repoping npcs in question - even server reset is not required. Again I am NOT rewriting any part of the code that actually requires testing.

"How do the other devs on the team know what you just did?" - you put it into log. "Updated npcs flags set BLA to X/Y - see this sql line"