Coh3n
2010-06-09 18:09:20
[INDENT]
Hey guys,
Since I've been working a lot lately, and a lot of my work is pretty repetitive and doesn't really require me to pay attention, I've had a lot of time to think about a lot of things. Naturally, MSI came to my mind.
I've had a lot of time to think about this one, and I honestly think it would be better for MSI as a whole if we ditched colour walking and went 100% reflection (like the original plan). Here's why:
Thoughts?
[/INDENT]
Hey guys,
Since I've been working a lot lately, and a lot of my work is pretty repetitive and doesn't really require me to pay attention, I've had a lot of time to think about a lot of things. Naturally, MSI came to my mind.
I've had a lot of time to think about this one, and I honestly think it would be better for MSI as a whole if we ditched colour walking and went 100% reflection (like the original plan). Here's why:
- I'm sure I'm not the only one who would say that the colour part of the walking has been a pain in the ass so far, and since MSI is such a big project, it's only going to get worse.
- Do I think the hybrid walking system would be the most efficient way of walking? Yes, but let's be honest, scripting activity has increased dramatically since the release of the new reflection, and a lot of work has to be put in to making colour walking points using TPAs. I don't want to have only the SL's maintaining the colour walking because other members find it too complicated or too frustrating.
- Since the minimap colours are much more detailed, I feel that a project this large just won't work well enough to have colour walking incorporated. I know I'm just kind of repeating what I've already said in different ways, but I don't care. :p
- The hardest part of a colour script is the walking, by far, and we can't expect any requested scripts (VEM, yew cutter, Karamja fisher) that require a lot of walking to be added in a decent amount of time when the walking takes to long to write, and even longer to test and critique to perfection, all to have it break due to Jagex adding a building, or changing some colours.
- Yes, reflection hooks get outdated often, but now that we have reflection back up and running, it won't be long after an RS update that we have updated hooks. This is why I would still like to have the option to disable reflection. If the hooks are outdated and reflection is compiled, the script will execute. But if reflection is disabled, then the user can still use any non-walking scripts.
- Yes, Jagex could make another massive update that completely breaks reflection, but I honestly don't see that happening any time soon. That is a risk that I'm willing to take.
- Having the walking reflection-only, we can easily add in relocation features and player location checks using TBoxes, which I think would be a cool, accurate feature. All of this would of course be in {$IFDEF REFLECTION} defines to avoid compilation errors.
From: 3Garrett3
We understand the risk in using reflection. But the immense amount of scripting large walking scripts in custom TPA functions with RRW backup and other methods (Symbols, educated guesses) to back that up is a much larger con that grows exponentially for the amount of steps that have to be done in colour. Doing two steps is realistic with colour. Doing 20 isn't. Doing 20 with reflection is a possibility, which allows us to focus on other areas of scripting instead of the walking.
Thoughts?
[/INDENT]