Skip to content
TORNLIFE More

Can't Declare?

Started by MightyGoober [812478] on in Bugs & Issues.

20 replies · 288 views · thread synced · 5 days ago · View on torn.com
About this thread

Posts archived: 21 / 21 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
21
Discussion span
→
Authority score
61 / 100
Historical score
40 / 100
Story score
45 / 100
Engagement score
62 / 100

People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.

Most-liked replies

LDP [1580562]

I can replicate this issue on Bad Company..

EDIT: It is more complex than i thought because I get the message "You cannot declare on N.0.0.B! You currently have a Non-Aggression pact with them!" for other factions, but not Bad Company (yes we have a NAP with Bad Company).

EDIT2: Think Stewie figured it out - it may be the 'tm' in the faction name preventing the warning message.

Passing to Chedburn



[image: gyazo.com]


MightyGoober [812478]

NAP with BAD COMPANY for 1 days
NAP with HT for 1 days

HT also gives a blank error message.

But the other NAPS at 1 day give the correct "can't NAP declare"
Kopites [1701371] Admin Staff

I've changed template for displaying response mesage. Please check if it works for you? Also, let me know if war was started when the response message was empty?
The_Healer [1787515]

Factions can be at war with a maximum of 500 enemy faction members. They're currently at war with test

Can't declare, might be same problem
Harley [258120] Wiki Contributor

Can this be fixed ASAP? This is hampering our ability to continue warring quite badly.
Tascon [209070]

Factions can be at war with a maximum of 500 enemy faction members. They're currently at war with test

Unable to declare still...
DevilSoldier [1731252]

Other people are having issues with certain notifications, as stated, when trying to declare, we're not getting the empty message, we're getting the "currently at war with test"