Borked .du command.

[delems]

This command don't work correctly anymore in many cases.

It often shows me allied tickets, not axis.

 

[delems]

Any status?

[delems]

This still seems broke, any update?

 

[delems]

Any status update, really makes manage supply harder when it doesn't work.

 

[delems]

Is even more borked than I thought.

Showing 124 tickets for Sonsbeck, but spawn list is full?

 

[delems]

Still and issue, on the list to be looked at?

 

[delems]

Been nearly a year now, this being worked on?
 

[TMAN]

No other reports of problems that I'm aware of.  Did you do a support ticket?

 

[delems]

*** No other reports of problems that I'm aware of. 

How many reports do you need?  What kind of response is that?

Been posting and using .bug for months now.... easy to replicate.  Sheesh, go in and type '.du'.

 

The .du command is borked, been that way for nearly a year.

Go to Roos garrison.... type '.du', you'll see brit tickets, not german.

 

[B2K]

12 hours ago, delems said:

*** No other reports of problems that I'm aware of. 

How many reports do you need?  What kind of response is that?

Been posting and using .bug for months now.... easy to replicate.  Sheesh, go in and type '.du'.

 

The .du command is borked, been that way for nearly a year.

Go to Roos garrison.... type '.du', you'll see brit tickets, not german.

 

It's in the queue of things to look at - ultimately it's annoying, but not game breaking, so it'll be prioritized accordingly. 

[delems]

*** ultimately it's annoying, but not game breaking

True, but as HC it is a needed tool, and frustrating when it doesn't work right.

Do we need to aggravate and frustrate HC?

 

[B2K]

5 hours ago, delems said:

*** ultimately it's annoying, but not game breaking

True, but as HC it is a needed tool, and frustrating when it doesn't work right.

Do we need to aggravate and frustrate HC?

 

jobs@corneredrats.com - hop on board help us get down the list of stuff faster. 

[delems]

This is really a much bigger issue now with most all ticket times 24 hours +.

And agree, not critical, but would be nice.

[delems]

Been looked at?  Still shows enemy units for tickets.

[delems]

Couple years now, update?

[B2K]

11 hours ago, delems said:

Couple years now, update?

still low on the list 

[Capco]

On 7/10/2021 at 8:03 AM, B2K said:

still low on the list 

Sigh...

@delems Can you at least always see the first friendly unit's timer?  Sometimes the timer on that first unit back is the most important part.

Does this only happen with garrisons or does it happen with flags too?  

[delems]

Only happens with garrisons.

No, you don't see friendly tickets until the enemy ones are gone.

So, you take an allied town.  Say 100 allies died while taking it.

Then over the next 5 hours your new town is counter attacked, losing many axis units.

With 15 hour timers, and 5 hours of counter attacks, it means for the next 10 hours .du will show you the 100 allied tickets, before the axis tickets.

Hence, no way to see when the axis tickets start to return.

Basically, .du should only show tickets for the owner of the town.

If axis owns a town, no allied ticket should ever show.

[Capco]

16 minutes ago, delems said:

Only happens with garrisons.

No, you don't see friendly tickets until the enemy ones are gone.

So, you take an allied town.  Say 100 allies died while taking it.

Then over the next 5 hours your new town is counter attacked, losing many axis units.

With 15 hour timers, and 5 hours of counter attacks, it means for the next 10 hours .du will show you the 100 allied tickets, before the axis tickets.

Hence, no way to see when the axis tickets start to return.

Basically, .du should only show tickets for the owner of the town.

If axis owns a town, no allied ticket should ever show.

Have you tried manually entering the brigade shortcode for the garrison?  I wonder if that might make a difference.

You can find the shortcodes by entering the garrison and typing .ne (strangely they actually have fallbacks, but they are always set to some non-linked town from what I can tell).  

Edited July 22, 2021 by Capco

[delems]

Not sure if I did, think I tried the different .ne codes for each town (they very from 0 to 6 at least as I recall).

Can't test anymore, not in HC.

[Capco]

Hmmm kk. 

I recall seeing this .du issue right before I left HC but I didn't spend much time troubleshooting it.  

And why no HC?  Taking a break?  Or?

[delems]

It's complicated, but ya, taking a break.

[delems]

This is still borked couple years later.

Confusing all our new HC players.