Forum

Will be updated next time you log in.

I can also tell you what is going on. Your Admin Alex is targeting everyone who is against Joe.

Remember - you don't know what you don't know.
Just because Joe and "his gang" don't keep shouting how many times they've been banned on the shoutbox, doesn't mean it hasn't happened. I can guarantee that it has.

When I pointed out his double standards, he muted me. Instead of responding to me as a good admin, he ignored my PM and did not even respond to this post. No one from the Assist  Admin staff wants to dig into why I was muted without cause.

It's possible you were banned on the shoutbox as a mistake. If there's a lof of nonsense on there, it can be hard to pinpoint who's trying to do what. So perhaps your example was a mistake. I do not know.
However, given this thread, I've got a feeling it wasn't.
With that said, we're a busy bunch. We don't have time to reply all sort of nonsense PMs. Believe me, we get plenty of it. Remember - we're running this place as volunteers. Free of charge. In our (limited!) free time. Trust me, it's (for the most part) not for the "fun" of it (especially recently).

I have been in the community for a very long time, as many others, and I don't start trouble, but your admin has decided to show his hand on his bias. The issue is that the rest of the Assist Admins don't want to deal with the cold, hard truth. You would rather delete our post or mute us, which is not the America's Army Way.

I'm sorry you don't like how we try to keep the peace in this community. I must admit, we've not done a perfect job of it. Clearly many of you are mad. Either at person A, person B, or their friends, or just the people trying to keep the peace (i.e the administrators).

I will re-iterate again. All we're trying to do with the shoutbox moderation is to lower the (perceived) level of drama and hatred that is rampent in this community. We're not shutting down any one narrative. If we had, you would notice that there wouldn't be any fighting since there'd be nobody to fight. We're trying real hard to make this community feel welcoming and friendly for new (or returning) players. We're trying real hard to limit the moderation to the shoutbox only. But the commmunity keeps proving - time and time again - that our efforts are futile.

So perhaps we should give up? And just admit that this is a toxic community that nobody should want to be a part of. That we might as well let this game die altogether. It's about time, isn't it?
Surely none of us want that!

I don't know whether or when you were banned from shoutbox. All I could see is that shortly before you posted this thread you had - in fact - posted on the shoutbox.

With that said, whenever someone does get banned, there is never any "explanation". It's just not something that's built into that system.

But if you were in fact banned, it was a temporary 24h ban. Probably for something you said. And that something was probably removed as well.
I could probably manually dig through the database to find what you posted and what was removed. But I really don't feel like it.

Yes. I played until 2am last night

Username: hgm2112
Tried to log in and the username doesn't exist. I played like 18 months ago.

The login name for that account is "hgm!". Login names are separate from in game names.

I'm not entirely sure and certainly no expert, but it used to be possible to VM Windows on Mac, wasn't it. If so, that'd be your best option.

So you might be able to do that, to an extent.

But the problem is that today, an M1/2/3/4 MacBook runs on an ARM based CPU architecture. So all it can do in a VM is run Windows on ARM. And Windows on ARM does provide an emulation layer for x86 to run applications built for that. So if all that works (which is not guaranteed given the age of this game and other specifics), you'd be loosing performance in 2 places: first, the VM emulating Windows; and second the Windows on ARM emulation layer for x86.

The underlying problem here is that the M1/2/3/4 processors are based on ARM. Whereas the processors used by MacBooks before (by Intel) and the processors (mostly!) used by other PCs were/are x86. Those are two different instruction sets for processor architecture. While Apple was able to introduce an emulation for x86 applications (called Rosetta 2), these are only really suitable for native MacOS apps (which at the time were 64bit applications - like said above, 32bit applications were phased out before) and won't be extendible to run 25Assist (or AA).

PS:
If someone does manage to get M1/2/3/4 -> Windows on ARM VM -> 25Assist running, don't hesitate to post a thread about how that went. Or even if you try and it doesn't work - so others can potentially save time.

Usually this indicates that the authentication server has a log in session with your account that hasn't been terminated yet.
As you suggested, this will normally happen if the Assist cleint crashes or something else goes wrong such that the authentication server wasn't told of the ending of the session (i.e loss of an interent connection could be another cuplrit).

The sessions are timed out after a certain time (don't know off the top of my head, but minutes rather than hours). And after that you should be fine to log in again on the account.

Now, if this happened hours from when you didn't have a 25Assist client open any time in the immediate past, it would indeed be a more concerning situation. However, we do track some login information on a per account basis - and like Bart said above, your account didn't have any logins from anywhere other than your computer/IP.