Bug that makes it impossible to complete
There are several post of this on the bug section, yet nothing has been replied to so posting here. The jumping puzzle Trolls Revenge is impossible to complete without a glider because the blue banner things hanging that you go across were replaced with hanging jack o lanterns with no collision. This is a very simple fix That can literally be done with the smallest patch/build..
It is not a simple fix. If it was, it would have been done last year when the same bug occurred. It requires fixing every part of the Halloween decorations that overlap with the JP. It will get fixed when the decorations are moved in 1-2 weeks.
Meantime, you can still get the chest reward by using sneaky methods to open up the caches for the keyparts and reaching the end chest.
To be clear: I think they should have fixed this and I think someone at ANet should be embarrassed that this is still an issue. All the same, it’s a temporary issue that will resolve itself.
John Smith: “you should kill monsters, because killing monsters is awesome.”
It is a pretty easy fix actually. Unless they coded it a VERY dumb/weird way.. I’ve worked in games using Unity 3D & Blender. Collision can be hard to work with on certain things.. But something like this shouldn’t be hard. And as you said it’s actually quite embarrassing.. All they have to do is make the jack o lantern wire have collision. :l
I like how the post can be moved, but not responded to by Anet.
It is a pretty easy fix actually. Unless they coded it a VERY dumb/weird way.. I’ve worked in games using Unity 3D & Blender. Collision can be hard to work with on certain things.. But something like this shouldn’t be hard. And as you said it’s actually quite embarrassing.. All they have to do is make the jack o lantern wire have collision. :l
We can’t say with certainty what the issue is, so we certainly can’t say with certainty how easy it would be to resolve. Maybe it should not be time-consuming, but evidence says that it is. It wasn’t fixed last year and it’s still not fixed. My guess is that they would have to redecorate each part of the puzzle and test it.
Regardless, it will resolve itself in 1-2 weeks, when the decorations are removed.
That makes it a medium-risk, medium-effort, low-reward fix — that won’t get prioritized over other fixes.
I like how the post can be moved, but not responded to by Anet.
I like it, too. It means that the people working on bugs aren’t spending any time at all moderating the forums. That would mean fewer bugs getting resolved.
Again, I agree that this bug should get fixed. I just can’t agree that we know it would be easy to do nor that it’s important or urgent to do so.
John Smith: “you should kill monsters, because killing monsters is awesome.”
It is easy to do, unless they coded it a very unprofessional way/their engine works differently. But trust me, otherwise this should NOT be hard. Also they should look at bug forums more. I’m not saying spend all day on there, but they can skim through some in a few minutes & give a reply if there is a fix coming or anything..
You can find the status of some bugs by following the link found in the Sticky above, ‘Known Issue Tracker’.
For an issue that will resolve itself in less than a week or so, you may just have to exercise patience.
Good luck.
Every man and his dog on these forums is an expert at computer coding. It doesn’t mean they know how ArenaNet do it. Just wait two weeks or so. Maybe next year it’ll get sorted! ^ ^
Blood & Merlot [Wine]
Every man and his dog on these forums is an expert at computer coding. It doesn’t mean they know how ArenaNet do it. Just wait two weeks or so. Maybe next year it’ll get sorted! ^ ^
Is that sarcasm? I’m sorry, but an actual programmer understands how collision works. And people like you seem to think we just want to be know it alls and defend the company to death.. We aren’t attacking them.. But.. It’s literally just changing code on that entity. They can make anything have collision. All they have to do is select it, and change the code to allow collision. It’s literally that simple, I promise you. And as others said.. Just waiting isn’t a big deal since it wont be long. It’s just kind of silly that this bug still exists for this halloween & how much of an easy fix it is. It’s like they don’t care/know..
(edited by iHeartbound.3074)
Every man and his dog on these forums is an expert at computer coding. It doesn’t mean they know how ArenaNet do it. Just wait two weeks or so. Maybe next year it’ll get sorted! ^ ^
Is that sarcasm? I’m sorry, but an actual programmer understands how collision works. And people like you seem to think we just want to be know it alls and defend the company to death.. We aren’t attacking them.. But.. It’s literally just changing code on that entity. They can make anything have collision. All they have to do is select it, and change the code to allow collision. It’s literally that simple, I promise you. And as others said.. Just waiting isn’t a big deal since it wont be long. It’s just kind of silly that this bug still exists for this halloween & how much of an easy fix it is. It’s like they don’t care/know..
It’s not sarcasm, it’s just that it’s always one of two things when the “I’m a computer programmer” card is played on these forums. Either that someone has done a little bit of coding as a hobby and is a know it all and says they are an expert at programming but are actually out of their depth. Or they are genuine a programmer to a high level, and assume because it’s a seemingly simple thing to do, it must be simple. But that’s not necessarily so. I’m not saying nor assuming you are one or the other.
Not to mention the fact that ArenaNet have a rather large plate, and a large banquet on top of it. It doesn’t matter how much you do or don’t know about programming at the end of the day. You don’t work for ArenaNet, so you don’t know fully what procedures they have to adhere to.
And people like you
What do you mean by “People like me”? You don’t know me, so how do you know which people are like me?
Blood & Merlot [Wine]
ArenaNet is always looking for programmers. Great opportunity!
I’m sorry, but an actual programmer understands how collision works.
Programmers also understand that it’s never as simple as changing one object. There are consequences to any change, no matter how small. Does the object inherit properties from something else? Does something else inherit its properties? How sure are you (the programmer) that the particular object is the only thing that needs collision added?
Enterprise programmers also have to work with the rest of their team: what was the reason that someone put a non-collide object in a JP? Did they realize it would affect the JP and decide that was the lesser of evils? Or was it an oversight?
Does the team need the person who would/could fix it working on something else that affects more people and that won’t get automatically resolved in a week or two?
And that ignores the issue of change and configuration management, quality assurance, and managing what each build includes.
But.. It’s literally just changing code on that entity. They can make anything have collision. All they have to do is select it, and change the code to allow collision. It’s literally that simple, I promise you.
You can only promise that changing one property on a single item is simple. You can’t promise that there’s nothing else to worry about, nor that someone is available to test that the “literally that simple” fix actually fixes the issue, without causing other issues.
We aren’t attacking them..
It’s like they don’t care/know..
And as others said.. Just waiting isn’t a big deal since it wont be long.
Which is it? The second quote impugns either their integrity (“don’t care”) or their skill (“don’t know”). Which is especially surprising since you agreed (3rd quote) that there’s another possibility: “waiting isn’t a big deal.”
And people like you seem to think we just want to be know it alls and defend the company to death..
I have no interest in defending ANet, to death or otherwise. I don’t work for them; they don’t pay me. I simply can’t agree that we know that this is an easy fix. If anything, the fact that they haven’t fixed it suggests that it’s more complicated than it seems.
It’s just kind of silly that this bug still exists for this halloween & how much of an easy fix it is.
It’s annoying, to be sure. It’s only silly if you imagine that the only issue is changing collision for an object or two.
tl;dr Raise the issue and be adamant that you want it fixed. Remind them in 9 months, so they don’t miss it next year. There’s no need to argue about whether the bug should have been fixed or not, or whether any of us know how easy it will be to fix — that distracts from your primary concern, which is that you’d like to run the JP without work-arounds or waiting a few weeks.
John Smith: “you should kill monsters, because killing monsters is awesome.”
I’m sorry, but an actual programmer understands how collision works.
Programmers also understand that it’s never as simple as changing one object. There are consequences to any change, no matter how small. Does the object inherit properties from something else? Does something else inherit its properties? How sure are you (the programmer) that the particular object is the only thing that needs collision added?
Enterprise programmers also have to work with the rest of their team: what was the reason that someone put a non-collide object in a JP? Did they realize it would affect the JP and decide that was the lesser of evils? Or was it an oversight?
Does the team need the person who would/could fix it working on something else that affects more people and that won’t get automatically resolved in a week or two?
And that ignores the issue of change and configuration management, quality assurance, and managing what each build includes.
But.. It’s literally just changing code on that entity. They can make anything have collision. All they have to do is select it, and change the code to allow collision. It’s literally that simple, I promise you.
You can only promise that changing one property on a single item is simple. You can’t promise that there’s nothing else to worry about, nor that someone is available to test that the “literally that simple” fix actually fixes the issue, without causing other issues.
We aren’t attacking them..
It’s like they don’t care/know..
And as others said.. Just waiting isn’t a big deal since it wont be long.
Which is it? The second quote impugns either their integrity (“don’t care”) or their skill (“don’t know”). Which is especially surprising since you agreed (3rd quote) that there’s another possibility: “waiting isn’t a big deal.”
And people like you seem to think we just want to be know it alls and defend the company to death..
I have no interest in defending ANet, to death or otherwise. I don’t work for them; they don’t pay me. I simply can’t agree that we know that this is an easy fix. If anything, the fact that they haven’t fixed it suggests that it’s more complicated than it seems.
It’s just kind of silly that this bug still exists for this halloween & how much of an easy fix it is.
It’s annoying, to be sure. It’s only silly if you imagine that the only issue is changing collision for an object or two.
tl;dr Raise the issue and be adamant that you want it fixed. Remind them in 9 months, so they don’t miss it next year. There’s no need to argue about whether the bug should have been fixed or not, or whether any of us know how easy it will be to fix — that distracts from your primary concern, which is that you’d like to run the JP without work-arounds or waiting a few weeks.
Bro I understand what you are saying. BUT it’s not as hard as you are making it out to be. It’s not anything major. It’s a VERY simple fix. THAT’S A FACT. Unless they coded it a terrible way & connected it with other things.. But It worked fine before the halloween change to that wire.. So if they changed that much just to give it a new look then someone really messed up. now if we were talking about collision on other things then you are correct. But this is NOTHING major.
And no, I’m not attacking them, don’t try to make it look like I am. It’s them not having enough clarity. Riot had trouble with this before on things. They need more clarity on things instead of leaving us in the dark on them.
Also it can be slid in with a hotfix/with a build. It’d nothing major, you are right. It’s just crazy that this is the second time it’s here this festival..
(edited by iHeartbound.3074)
Every man and his dog on these forums is an expert at computer coding. It doesn’t mean they know how ArenaNet do it. Just wait two weeks or so. Maybe next year it’ll get sorted! ^ ^
Is that sarcasm? I’m sorry, but an actual programmer understands how collision works. And people like you seem to think we just want to be know it alls and defend the company to death.. We aren’t attacking them.. But.. It’s literally just changing code on that entity. They can make anything have collision. All they have to do is select it, and change the code to allow collision. It’s literally that simple, I promise you. And as others said.. Just waiting isn’t a big deal since it wont be long. It’s just kind of silly that this bug still exists for this halloween & how much of an easy fix it is. It’s like they don’t care/know..
It’s not sarcasm, it’s just that it’s always one of two things when the “I’m a computer programmer” card is played on these forums. Either that someone has done a little bit of coding as a hobby and is a know it all and says they are an expert at programming but are actually out of their depth. Or they are genuine a programmer to a high level, and assume because it’s a seemingly simple thing to do, it must be simple. But that’s not necessarily so. I’m not saying nor assuming you are one or the other.
Not to mention the fact that ArenaNet have a rather large plate, and a large banquet on top of it. It doesn’t matter how much you do or don’t know about programming at the end of the day. You don’t work for ArenaNet, so you don’t know fully what procedures they have to adhere to.
And people like you
What do you mean by “People like me”? You don’t know me, so how do you know which people are like me?
But even people new to programming knows how collision works. Even flash 2d game developers.. It really is that easy to fix, unless they screwed something up majorly when they first changed it for halloween. And if so.. The guy in charge of that must have really made a mistake. Because I doubt that was a team thing. Even good programmers can make mistakes. We’re only human. If this was a collision issue on something other than just a small wire then yes you are right it would be harder. And I meant people like you who think someone saying something is always trying to be full of self. Those kind. If you didn’t mean that sorry. Butt hat’s how you came off.
They only need to add collision for all characters that can be made. But they also can add collision for targeted spells, which isn’t necessarily needed. Its a pretty easy fix. Also the coding for some of the other clothes lines or wires that have collision are the same thing just with different sizes/values.
Having same problem with the hero challenge on the pinion trail in queensland. I’ve done it like 6 or 7 times and it will not give me the credit.
OP mentions about knowing Unity and Blender, Guild Wars 2 uses a completely different and in-house engine. Each and every engine works differently, what’s easy in one may not be in another. Only Anet can tell if it’s an easy fix or not. What can seems a easy change may lead to a chain of breaking items.
Either way, the thing isn’t about if it’s easy or not, it’s about their priority and how serious such a bug/flaw can be. It’s a bug/mistake or an intentional change with a unfortunate side-effect (who knows) for sure, but discussing if it would be easy for them or not is going to lead nowhere.
OP mentions about knowing Unity and Blender, Guild Wars 2 uses a completely different and in-house engine. Each and every engine works differently, what’s easy in one may not be in another. Only Anet can tell if it’s an easy fix or not. What can seems a easy change may lead to a chain of breaking items.
Either way, the thing isn’t about if it’s easy or not, it’s about their priority and how serious such a bug/flaw can be. It’s a bug/mistake or an intentional change with a unfortunate side-effect (who knows) for sure, but discussing if it would be easy for them or not is going to lead nowhere.
The only possible way it would do that is if Anet were amateurs. And they aren’t. As someone else said a second ago, it’s a simple fix.. Adding collision on something like that. Other things I’d agree it’s not as simple. Their engine was built for their game. They wouldn’t mess that up. I promise you it’s a simple fix, it’s not hard and wont break a bunch of other things. You guys are over thinking it big time.. I guarantee Anet could even tell you the same.
It’s also a very fast & easy patch. But as others said it’s not really a big deal. But the fact they over looked this for 2 festivals now says something. Do they even know? I was on known issues & seen nothing about it. That’s the entire point of my post. It’s an easy fix, it’s not hard. Even you could look up a youtube video & see how it’s done & mane to recreate it on their engine. UNLESS they have a bad engine. & I know for a fact they don’t. They know what they are doing. I just believe this was overlooked. And that’s it. That’s why I keep bumping this. You guys can argue with me if youd like and tell me I’m wrong, because I never used their engine.
But a studio as big as Anet would not have a kitten engine like that. I promise you. I’m about 90% sure they over looked it or cant be bothered to mess with something so minor.
If the issue is so minor, as you state, why would they bother with fixing something that will fix itself in a few days?
If the issue is so minor, as you state, why would they bother with fixing something that will fix itself in a few days?
Because it’s the second festival in a row where this happened. They need to realize this is a thing. It’s not in the known issues thread either.
Very few bugs are listed in the Known Issue Tracker, as indicated in the header. Especially bugs that will resolve themselves.
I’m sure when it makes its way to the top of the priority list, it will be resolved.
Good luck.
The only possible way it would do that is if Anet were amateurs. And they aren’t. As someone else said a second ago, it’s a simple fix.. Adding collision on something like that. Other things I’d agree it’s not as simple. Their engine was built for their game. They wouldn’t mess that up. I promise you it’s a simple fix, it’s not hard and wont break a bunch of other things. You guys are over thinking it big time.. I guarantee Anet could even tell you the same.
It’s also a very fast & easy patch. But as others said it’s not really a big deal. But the fact they over looked this for 2 festivals now says something. Do they even know? I was on known issues & seen nothing about it. That’s the entire point of my post. It’s an easy fix, it’s not hard. Even you could look up a youtube video & see how it’s done & mane to recreate it on their engine. UNLESS they have a bad engine. & I know for a fact they don’t. They know what they are doing. I just believe this was overlooked. And that’s it. That’s why I keep bumping this. You guys can argue with me if youd like and tell me I’m wrong, because I never used their engine.
But a studio as big as Anet would not have a kitten engine like that. I promise you. I’m about 90% sure they over looked it or cant be bothered to mess with something so minor.
Yup I know. And well, I never stated that anyone here was wrong. And for sure it needs a fix. But quoting myself...
Only Anet can tell if it’s an easy fix or not.
the thing isn’t about if it’s easy or not, it’s about their priority and how serious such a bug/flaw can be.
discussing if it would be easy for them or not is going to lead nowhere.
Don’t take me bad, it’s nice and appreciated the issue is reported. But the report was made and done, no reason to keep discussing it further. Hopefully they will see this and fix it (for the next year maybe). *shrugs*
The only possible way it would do that is if Anet were amateurs. And they aren’t. As someone else said a second ago, it’s a simple fix.. Adding collision on something like that. Other things I’d agree it’s not as simple. Their engine was built for their game. They wouldn’t mess that up. I promise you it’s a simple fix, it’s not hard and wont break a bunch of other things. You guys are over thinking it big time.. I guarantee Anet could even tell you the same.
It’s also a very fast & easy patch. But as others said it’s not really a big deal. But the fact they over looked this for 2 festivals now says something. Do they even know? I was on known issues & seen nothing about it. That’s the entire point of my post. It’s an easy fix, it’s not hard. Even you could look up a youtube video & see how it’s done & mane to recreate it on their engine. UNLESS they have a bad engine. & I know for a fact they don’t. They know what they are doing. I just believe this was overlooked. And that’s it. That’s why I keep bumping this. You guys can argue with me if youd like and tell me I’m wrong, because I never used their engine.
But a studio as big as Anet would not have a kitten engine like that. I promise you. I’m about 90% sure they over looked it or cant be bothered to mess with something so minor.
Yup I know. And well, I never stated that anyone here was wrong. And for sure it needs a fix. But quoting myself…
Only Anet can tell if it’s an easy fix or not.
the thing isn’t about if it’s easy or not, it’s about their priority and how serious such a bug/flaw can be.
discussing if it would be easy for them or not is going to lead nowhere.
Don’t take me bad, it’s nice and appreciated the issue is reported. But the report was made and done, no reason to keep discussing it further. Hopefully they will see this and fix it (for the next year maybe). shrugs
It’s just no matter what I will never agree with you that it could be a hard thing to fix something like this, since we don’t know their engine.. But it being their own engine & the game was built for this type of stuff I know for a fact they would make it easier to fix things like this, not complicated. But I just keep bumping every now and then and maybe one day Anet will see it. Because as I said before it’s not on the known issues so I’m trying to get it there. Speaking of known issues.. The page stopped working for me. Does it work for you?
Again, every bug does not make it to the ‘Known Issue Tracker’.
And, just because the bug isn’t listed, doesn’t mean the Devs aren’t aware. Many bugs listed fixed in the Patch Notes were never on the Tracker.
Speaking of known issues.. The page stopped working for me. Does it work for you?
Hmm, the page is working fine for me. Maybe it was just a glitch at the time you tried or they took it off for changes (I see the whole support portal has a different visual now, not sure since when though).
This bug will be gone on Tuesday. This continued debate isn’t really worth it I don’t think.
Blood & Merlot [Wine]
The only possible way it would do that is if Anet were amateurs. And they aren’t. As someone else said a second ago, it’s a simple fix.. Adding collision on something like that. Other things I’d agree it’s not as simple. Their engine was built for their game. They wouldn’t mess that up. I promise you it’s a simple fix, it’s not hard and wont break a bunch of other things. You guys are over thinking it big time.. I guarantee Anet could even tell you the same.
It’s also a very fast & easy patch. But as others said it’s not really a big deal. But the fact they over looked this for 2 festivals now says something. Do they even know? I was on known issues & seen nothing about it. That’s the entire point of my post. It’s an easy fix, it’s not hard. Even you could look up a youtube video & see how it’s done & mane to recreate it on their engine. UNLESS they have a bad engine. & I know for a fact they don’t. They know what they are doing. I just believe this was overlooked. And that’s it. That’s why I keep bumping this. You guys can argue with me if youd like and tell me I’m wrong, because I never used their engine.
But a studio as big as Anet would not have a kitten engine like that. I promise you. I’m about 90% sure they over looked it or cant be bothered to mess with something so minor.
Yup I know. And well, I never stated that anyone here was wrong. And for sure it needs a fix. But quoting myself…
Only Anet can tell if it’s an easy fix or not.
the thing isn’t about if it’s easy or not, it’s about their priority and how serious such a bug/flaw can be.
discussing if it would be easy for them or not is going to lead nowhere.
Don’t take me bad, it’s nice and appreciated the issue is reported. But the report was made and done, no reason to keep discussing it further. Hopefully they will see this and fix it (for the next year maybe). shrugs
It’s just no matter what I will never agree with you that it could be a hard thing to fix something like this, since we don’t know their engine.. But it being their own engine & the game was built for this type of stuff I know for a fact they would make it easier to fix things like this, not complicated. But I just keep bumping every now and then and maybe one day Anet will see it. Because as I said before it’s not on the known issues so I’m trying to get it there. Speaking of known issues.. The page stopped working for me. Does it work for you?
From the ‘Known Issue Tracker’ header:
This list isn’t meant to cover every single bug in the game. For the sake of keeping things concise, we’re intentionally leaving out anything that could be used as an exploit and minor issues unlikely to impact most players.
I see the Knowledge Base (Support) has a new URL. Cool, I guess. I hope they changed all the links, or leave the old one up for a long time.