Previous Thread
Previous
Expand All
Collapse All
Ignore Author
Reply
Thank you for your work on this.
Whenever I have to deal with existing spaghetti code that drives me crazy I usually just start from scratch. It's those unfortunate times when you can't :(
Drives me crazy when I look at code and there is no rhyme or reason why they are doing something that makes it less efficient. People like to do that a lot in SQL views and stored procedures... especially report writers who don't care about efficiency... end random rant.
Drives me crazy when I look at code and there is no rhyme or reason why they are doing something that makes it less efficient. People like to do that a lot in SQL views and stored procedures... especially report writers who don't care about efficiency... end random rant.
Oh, I'm still here. I haven't had time to look at it much since my last post.
I was working on some internal updates for assists/referral. A new system (Internal and External) way to handle events/quests as debuted at Summit Academy. A couple things for duskruin. I have one more large project I have to finish up then I'll have some spare time to dabble back into player shops.
The issue is there are a lot of playershops that have been force-fixed over the years. I'll need to document each one of those and come up with my own spaghetti code to work around these exceptions. Alternatively, fix them then apply spaghetti code logic.
The overall system was working on the test server (based on feedback from everyone). After I get the above outlined done, I'll need to do more due diligence testing prior to putting it live. Hopefully with the help of the players who want this done. When I squint and look at things I don't always catch the same things that someone who actively looks at it would.
... and I'm already crazy, it is just which direction I point my crazy at.
Retser, ASGM
I was working on some internal updates for assists/referral. A new system (Internal and External) way to handle events/quests as debuted at Summit Academy. A couple things for duskruin. I have one more large project I have to finish up then I'll have some spare time to dabble back into player shops.
The issue is there are a lot of playershops that have been force-fixed over the years. I'll need to document each one of those and come up with my own spaghetti code to work around these exceptions. Alternatively, fix them then apply spaghetti code logic.
The overall system was working on the test server (based on feedback from everyone). After I get the above outlined done, I'll need to do more due diligence testing prior to putting it live. Hopefully with the help of the players who want this done. When I squint and look at things I don't always catch the same things that someone who actively looks at it would.
... and I'm already crazy, it is just which direction I point my crazy at.
Retser, ASGM
Geez, I need ;whatis even to read the Forum now!
>;whatis 318
--- Lich: whatis active.
318 / Raise Dead
Raise Dead (318), a utility spell from the Cleric Base Spell Circle
https://gswiki.play.net/Raise_Dead_%28318%29
---
Rohese: "... the TownCrier (tune in if you haven’t, it’s without doubt the best thing to ever happen on LNet)"
>;whatis 318
--- Lich: whatis active.
318 / Raise Dead
Raise Dead (318), a utility spell from the Cleric Base Spell Circle
https://gswiki.play.net/Raise_Dead_%28318%29
---
Rohese: "... the TownCrier (tune in if you haven’t, it’s without doubt the best thing to ever happen on LNet)"
