stanhope

Start with running it completely vanilla, then keep adding mods until the issue occurs again. The last mod(s) you've added will be the issue or will combined with some other mods that have been added be the issue. Once you've done that, check in your server's RPT to see what the problem is. Then inform the maker of the mod about the problem.

You're intentionally using an outdated version of a mod but are requestion help when a part of it doesn't work?

Do you have access to an operating system or are you just given an interface for hosting an arma server?

SaaS or HaaS?

Could you share both your and the server's RPTs?

You've got to contact the owner of the server you're trying to connect to. We don't know which version of CBA the server you're trying to join is using.

Which mission?

How is it dysfunctional in arma? It worked perfectly fine for me yesterday, the circle is a bit bigger but the bomb always lands smack in the middle of that circle for me.

Could you share the full code you ran there, monitor your knowsabout value and send a screenshot of how everything is set up in that scenario?

In mission sqm, at the top there's a list of mods, you can remove certain mods there

Have a look here:

Put the mission file in the mpmissions folder and do #missions on server

You don't have to uninstall anything to play multiplayer? Just untick the contact option on the DLC page in the launcher. You'll still have access to most of the assets, just not the actual alien stuff.

It's not like they were hiding that they were doing it. You just either didn't do your research or failed to notice it. How exactly is BI at fault here? Installing a mod and hacking the game are in no way, shape or form similar. In some games they might be, but in Arma they're not even close

There's a mod to bring back the normal screen. BI has said that contact itself is incompatible with multiplayer but nothing's stopping you from trying. See https://arma3.com/contact for more info (there's a FAQ at the bottom)

Have a look at: And

Verify the integrity of your local game files through steam (right click on arma > properties > local files > verify)

Have a look at these topics:

And apparently me telling you something doesn't help. So go to the editor and test it.

Straight answer: No, the titan cannot lock onto lasers, source: https://armedassault.fandom.com/wiki/Titan_MPRL_Compact (look under sensors) Also, keep it English

It all depends on what exactly you're trying to lock onto a laser. IIRC the titan AA and AT cannot lock on to lasers, the AP might? I really can't remember. Just give it a try, set up a darter in the editor, lase something and try to lock on.

Well, read the kick message. It tells you you're banned for 3 days ([3d]) for ramming in spawn (ramming in spawn) and to appeal at the discord link provided (appeal@c4g.cc/discord).

What do you mean? Which launcher should lock on to a laser? Or do you mean lock onto one specific laser if there's multiple lasers?

Go to: C:\Users\yourUser\Documents\Arma 3 or C:\Users\yourUser\Documents\Arma 3 - Other Profiles\yourProfile\ In there there are 3 files with the extension Arma3Profile, copy those over to your new machine. Your loadouts will specifically be saved in yourProfile.vars.Arma3Profile, but the others probably also contain stuff you want transferred over.

This bot has been discontinued and replaced with this one: https://forums.bohemia.net/forums/topic/231021-stans-server-monitor-bot/ Arma server monitor discord bot I recently made a discord bot that is able to monitor arma server to check if they go down. Additionally it also allows user to check the amount of players on server etc. There are other noteworthy features that are mentioned bellow. In this post I'm providing the source code for this bot so you can host your own bot doing this. Features Support for an unlimited amount of arma and teamspeak servers Pings given roles or users if one of those servers goes down The ability to turn those pings of for servers dynamically Logging for the number of players on those servers (can be turned on or off for every individual server) The ability to change how often the status of those servers should be checked The ability for users with certain roles to launch certain queries to those servers A 2 tier system for all bot commands (admin tier and normal users. Normal users can only run a limited amount of commands, admins can run every commend (see available commands) The ability to reread the config without having to restart the bot The ability to mute all down pings between 2 given hours (for scheduled restarts) The ability to upload missions to a server and change the default mission for a server The ability to launch and stop servers with this bot The bot is restricted to 1 channel A timeout between pings for the same server being down RSS reader support Uses discord embeds Available commands Usage This is simply source code, this is not a bot you can add to your server. You need to create your own bot and host this code. To create a bot I suggest googling 'how to create a discord bot', at the time of writing there are several very good tutorials available. To host the code; download the source from the link provided bellow, open the readme and read through it carefully, edit the config.json in the \config directory (there is a configExplenation.txt available in the same directory with some extra explanation on what each value is/does) and finally start the bot up using the commands provided in the readme. Requirements This bot requires node.js and a discord bot License This work is licensed under Apache License 2.0, full license included on the gitlab. Download - Bugs Please report bugs here or on the issue section of the above linked gitlab Planned features uploading missions via a link in addition to the traditional way Feel free to make suggestions though (but I make no promises about putting them in, all I promise is that I'll try) Updates