Sign in to follow this  
DevBlog

WSA: Combat issues and hotfix

Recommended Posts

WSA.png

There is currently an issue which can cause effects such as stun, etc to not wear off. We are aware of the issue and are in the process of implementing a hotfix.

Until this hotfix please refrain from entering combat on both PvP and PvE servers.

A full PvP ban is also in place until this issue is confirmed resolved.

A public list of what directives are in effect can be found here.

http://forum.wurmonline.com/index.php?/topic/137025-pvpraid-ban-directives/

Share this post


Link to post
Share on other sites
20 minutes ago, Fooligun said:

Good job testing things before implementing them

 

/sarcasm.

These changes were on the test server for several weeks, with full notes.

  • Like 1

Share this post


Link to post
Share on other sites

Full pvp ban should mean no repairs on deeds at all. A ban is a ban, you should at max be allowed to make the mats/resources. You can't just spring an update on which works in defenders favors.

Maybe this should be looked into a bit more and thought about.

  • Like 4

Share this post


Link to post
Share on other sites
20 minutes ago, Retrograde said:

These changes were on the test server for several weeks, with full notes.

 

Then why is it there is a bug with a combat related problem?  Seems like the test server should find issues like this.

  • Like 2

Share this post


Link to post
Share on other sites
3 minutes ago, Pashka said:

 

Then why is it there is a bug with a combat related problem?  Seems like the test server should find issues like this.

 

It was found and it was ignored and released anyways:

 

2016-08-26 on test server, from my local log

[19:51:06] <Lisabet> generic resistance
[19:51:22] <Lisabet> you are resistant to something undefined (if you see this there might be a bug)

 

Edited by Alexgopen
  • Like 2

Share this post


Link to post
Share on other sites

A full raid ban comes in to effect while a raid is happening without any notice and while 6 people are being camped / trapped in a mine. Good job Couldn't have had a better timing. Literally wasted a large group of players last 48 hours of work. Because now due to raid ban they can fix the deed they didn't even defend with no worries. 

 

Fuxking pathetic

Edited by Egard
  • Like 5

Share this post


Link to post
Share on other sites

They did announce a planned update for today, but lets just keep being paranoid B)

Share this post


Link to post
Share on other sites

To be fair there have been a number of times this has happened in favor of JK in the past as well as BL.

  • Like 1

Share this post


Link to post
Share on other sites
24 minutes ago, Oats said:

They did announce a planned update for today, but lets just keep being paranoid B)

 

damage is already done, 6 players are out, deed can be fixed in under an hour and a half because wurm

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Alexgopen said:

 

It was found and it was ignored and released anyways:

 

2016-08-26 on test server, from my local log

[19:51:06] <Lisabet> generic resistance
[19:51:22] <Lisabet> you are resistant to something undefined (if you see this there might be a bug)

 

 

 

Seriously?!

 

Was it submitted or just 'chat'? Either way it doesn't matter.

  • Like 1

Share this post


Link to post
Share on other sites

Guessing since she is a CM she would know how to make sure that someone knew about it.

  • Like 1

Share this post


Link to post
Share on other sites

gotta love wurm, the prize in your hands then it slips cause bugs :D all part of the fun and games. MR/JK both know that was the best timing ever/worst timing ever xD Sucks but if that was in my favor I'd be skipping out like lalalala :L


But can we atleast look at the "allowed to build yours or allied deeds" if a deed is under siege there is noway this should be allowed. All activity on that deed should stop, you should only be able to create matts with the items you got there but you should in no way be able to repair dirt walls/buildings/damage.

@Retrograde You've been told how annoying raiding is, especially for the attacker, this rule is fair for both sides as a pvp/raid ban doesn't happen often but nobody [even if they're against me] deserves to have work wiped away, as a defender, I'd be bummed that an attack/siege got ended in such a manner...Keep it fair. Please speak it over with GMS for the next time it happens.


 

Edited by Mclovin

Share this post


Link to post
Share on other sites
16 minutes ago, Mclovin said:

gotta love wurm, the prize in your hands then it slips cause bugs :D all part of the fun and games. MR/JK both know that was the best timing ever/worst timing ever xD Sucks but if that was in my favor I'd be skipping out like lalalala :L


But can we atleast look at the "allowed to build yours or allied deeds" if a deed is under siege there is noway this should be allowed. All activity on that deed should stop, you should only be able to create matts with the items you got there but you should in no way be able to repair dirt walls/buildings/damage.

@Retrograde You've been told how annoying raiding is, especially for the attacker, this rule is fair for both sides as a pvp/raid ban doesn't happen often but nobody [even if they're against me] deserves to have work wiped away, as a defender, I'd be bummed that an attack/siege got ended in such a manner...Keep it fair. Please speak it over with GMS for the next time it happens.


 

 

the funniest thing is when enemies build low stone walls just outside your deed but still blocking your exit before the pvp ban, and then during the ban you arent allowed to bash them down because they are "off deed" so you are trapped inside

Share this post


Link to post
Share on other sites

[23:58:10] 10 minutes to shutdown. 

[23:58:46] 5 minutes to shutdown. 

 

So 36 seconds seems like 5 minutes to you guys or did you catch some time traveler pokemon?

  • Like 1

Share this post


Link to post
Share on other sites
10 minutes ago, bangzuvelis said:

[23:58:10] 10 minutes to shutdown. 

[23:58:46] 5 minutes to shutdown. 

 

So 36 seconds seems like 5 minutes to you guys or did you catch some time traveler pokemon?

 

xanadu?  seemed fine on ele

 

[18:43:27] 20 minutes to shutdown.
[18:53:27] 10 minutes to shutdown.
[18:58:27] 5 minutes to shutdown.
[19:00:27] 3 minutes to shutdown.
[19:02:27] 1 minute to shutdown.
[19:02:58] 30 seconds to shutdown.
[19:03:07] 20 seconds to shutdown.
[19:03:17] 10 seconds to shutdown.

Share this post


Link to post
Share on other sites

In Xanadu ... time is truly strange.

 

[23:46:04] 20 minutes to shutdown. 

[23:58:21] 10 minutes to shutdown. 

[23:58:56] 5 minutes to shutdown. 

[00:01:24] 3 minutes to shutdown. 

[00:03:41] 1 minute to shutdown. 

[00:04:11] 30 seconds to shutdown. 
[00:04:21] 20 seconds to shutdown. 
[00:04:31] 10 seconds to shutdown. 
 

 

 

  • Like 2

Share this post


Link to post
Share on other sites

xan just needs removed from wurm... would solve 90% of problems

 

or at least reset to a 16x16km map like indy/chaos

Edited by Evilreaper

Share this post


Link to post
Share on other sites
9 hours ago, Retrograde said:

These changes were on the test server for several weeks, with full notes.

 

Then how is it possible that a very severe bug like this can get through, that is found within an hour of server up? The sad part is this isn't uncommon.

 

It means one of a few things:

1- You didn't actually test anything, or listen to anyone testing, or no one cared to report it.

2- You do not actually have a proper staging server that actually replicates the live servers.

3- You do not have a cohesive QA strategy.

4- You do not care enough, and are willing to risk loss knowing this will happen (see: mmo gaming development fallacy)

 

Will you at least address the part where a CM found this bug on the test server on August 26th, and yet it's still here almost 2 weeks later? (if true).

 

I honestly do not even have to think to post this stuff anymore...

 

  • Like 3

Share this post


Link to post
Share on other sites
15 minutes ago, Shazaam said:

 

Then how is it possible that a very severe bug like this can get through, that is found within an hour of server up? The sad part is this isn't uncommon.

 

It means one of a few things:

1- You didn't actually test anything, or listen to anyone testing, or no one cared to report it.

2- You do not actually have a proper staging server that actually replicates the live servers.

3- You do not have a cohesive QA strategy.

4- You do not care enough, and are willing to risk loss knowing this will happen (see: mmo gaming development fallacy)

 

Will you at least address the part where a CM found this bug on the test server on August 26th, and yet it's still here almost 2 weeks later? (if true).

 

I honestly do not even have to think to post this stuff anymore...

 

 

5- the posts reporting it were deleted because someone felt it was not actually tested and just guessed at.

  • Like 1

Share this post


Link to post
Share on other sites

Meh, annoying to see the same tendencies in responses to changes:

 

Its not unusual for a bug to escape testing in a closed, controlled environment. Certainly helps for issues to be documented well enough to be reproduced. Also some bugs can only be feasibly located in the wild.

 

The upcoming changes were not "sprung", they've been on test for quite a while now with substantial documentation.

 

GMs telling everyone to "get out of the pool" while matters are resolved tends to be best for everyone in the long run. Positions can easily end up being reversed down the road.

Edited by Klaa

Share this post


Link to post
Share on other sites
6 hours ago, Klaa said:

Meh, annoying to see the same tendencies in responses to changes:

 

Its not unusual for a bug to escape testing in a closed, controlled environment. Certainly helps for issues to be documented well enough to be reproduced. Also some bugs can only be feasibly located in the wild.

 

The upcoming changes were not "sprung", they've been on test for quite a while now with substantial documentation.

 

GMs telling everyone to "get out of the pool" while matters are resolved tends to be best for everyone in the long run. Positions can easily end up being reversed down the road.

 

Like (out of them)

Share this post


Link to post
Share on other sites
Sign in to follow this