- What is your character name in New World: Namsi
- What server/world did you experience your issue on: Sutekh
- Describe the issue you are experiencing: I can’t sign up for a defence war. I have only done 1 attack war today, and 0 defence wars, but it says I hit my daily defense limit as well as attack…
- Is this a bug?: yes
- (if a bug) How did the issue affect your gameplay: couldn’t sign up for a defence to help
- (if a bug) Were you able to recover from the issue: no
- (if a bug) Please include a screenshot or video of the issue that you have experienced: N/A - simply can’t sign up due to this error that has miscounted my wars for the day.
- What are the steps to reproduce the issue as you experienced: not sure, just couldn’t sign up for the defence even though I had only done 1 attk war 0 defence war that day
- When did this happen? 09/12/2022 approx. 9:35pm AEDT
1 Like
Same bug for all my company.
1 Like
Also seemed to trigger for a member in my company in this exact scenario (hopefully can help with fixing):
He had 1 defence war and 0 attack war this day. So he has an available attack war to use overall.
-
He was signed up to an attack war. This sign up worked. He was signed up to this war before his upcoming defence war. This attack war starts at 11pm.
-
Defence War starts at 9pm - commences and completes.
-
He then left his next upcoming war roster (the attack war at 11pm) before the war starts & before invites are out.
-
He wanted to sign back up to this attack war (war has not started yet), but it now says he has reached his limit. No other wars aside from his completed 1 defence war had actually occurred this day.
It seems this bug triggers if you try to sign up for a war AFTER you completed a war that day. So you can’t sign up to a war - for either side - after you finish a different war that day.
Possible Temporary Solution?: You seem to have to sign up to your 2 limited wars BEFORE any Wars actually occur? For example, if you are signed up to 1 defence war for the day, and you have another attack war afterwards (on this same day), you should be signed up to both before the 1st war starts. And do NOT leave the roster or the bug will occur, lol.
This is a huge issue that needs to be fixed ASAP as this essentially makes it only possible to do 1 war for many who get the bug.
Adding onto this, you can’t seem to sign up for a war the FOLLOWING day (or next 2 days) if you have done your wars the CURRENT day. You have to wait until the daily refresh, which makes doing rosters in advance an absolute pain and hassle.
1 Like
I joined a defense war las night and as it started, it popped up on my screen that I had reached my attack and defense limit. Yet I had only just started the only war of the night.
If my game had to crash for example, as NW often does, then I wouldn’t even be able to get back into the ongoing war. The limit should only count near the end of the war and for the correct type of war.
1 Like
Got the same bug on fresh start servers. Did an attack war, and now I cant defend in our own company war.
This game currently is feeling a lot like launch…
Musket broken beyond belief with machinegunning, war cd bugged, closing trading post for days because they open up for the same exploits once again.
This is exactly why people like me quit the game, its just unplayable. Were very enjoyable to start out, very stable only getting stuck in environment etc, no real exploits with weapons etc - and now we are just backtracking to the same old mill - economy exploited and weapons being exploited and glitched.
1 Like
What is your character name in New World: Lhiana
What server/world did you experience your issue on: Abaton
Describe the issue you are experiencing: I can’t sign up for a defence war. I have only done 1 attack war today, and 0 defence wars, but it says I hit my daily defense limit as well as attack…
Is this a bug?: yes
(if a bug) How did the issue affect your gameplay: couldn’t sign up for a defence to help
(if a bug) Were you able to recover from the issue: no
(if a bug) Please include a screenshot or video of the issue that you have experienced: N/A - simply can’t sign up due to this error that has miscounted my wars for the day.
What are the steps to reproduce the issue as you experienced: just couldn’t sign up for the defence even though I had only done 1 attk war 0 defence war that day
When did this happen? 10/12/2022 22:53 CET
1 Like
Another note to add:
When my FIRST war of the night actually “began” (the timer starts, invisible wall drops), the notice on screen appeared, saying “you have reached your ____ war limit for the day.” This indicates your remaining war eligibility for the day.
BUT this notice said that I had reached both my 1 attack + 1 war daily limit when it was my first war of the evening (a defence war). This is an incorrect notice, but it also seems to correlate to the issue where you can’t sign up for any war after the first war you are in has commenced.
However, after this war completed, I was still signed up for my next war (attack) that was later in the evening, despite the notice saying otherwise. Although, if I were to then leave the roster for that attack war, it would not have let me sign back up - this is the bug, and that “notice” corresponds to it. If that makes sense lmao
Same bug just happened for me on Heliopolis. I did one attack war today and it won’t even let me sign up for a defense TOMORROW.
It will let you after the daily refresh
But if you have another war tonight after your attack war and didn’t sign up to it prior to the first war starting, it won’t work I think.
Just take off this war cd, this came to game just to destroy it… doesnt make any sense, you cant play a wars , that is the only thing good to do after take all bis set, and 625 gs…
Have they fixed the bug that war is now limited to 1 day because 1 war is counting as both an attack and defense yet?
Just had a war this evening and firstly, it unsigned me from a war tomorrow and secondly, when I tried to resign up, it won’t let me because “I have reached my limit” for today. It’s ridiculous that this hasn’t been fixed after weeks
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.