TheConen

I just want to address an argument that's always brought up from the "Pro Monetization" side (and has been brought up in this thread, too): Needing the monetization money to pay for the server. As a leader of one of the larger ArmA communities in the german sector, I can say: this is simply not true. There was a time where I paid our server myself, with my own money. About two years ago (IIRC, exactly two years ago), we started to do so called "donation runs", where we would give members of our community the opportunity to donate some money if they wished so - completely voluntarily, without getting anything in return. Since then, I never had to pay the server with my own money again. Our last donation run was in December 2016 and collected over 1100€, which will pay our server for more then the next two years (the server is ~40€/month, and it's running several websites, Arma servers and HCs without any performance problems). So whenever someone says he needs monetization to pay for the server, I just don't get it. If you can't run your community by voluntary donations or your own money, you probably shouldn't be running a community at all. //Edit: In case anyone still wanders: I'm on the triple-nope-train.

Hey there, the last update seems to have some incompatibility with ACE3 - the "Passengers" option for vehicles is not shown anymore in the ACE Interaction menu which prevents medical treatment in vehicles. We removed the mod until that is fixed.

That's definitely the most important thing! Also I recommend to read this: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Regarding the "missing addons" error messages: They are usually caused by a corrupt download, the addons are definitely in CUP Terrains.

Dude, you should start using pboProject, there are a lot of errors in the config. I can help you with those if you want, you can contact me in the CUP discord.

Haven't had a chance to try this yet - is the target pod view fixed? Only read the changelog on Armaholic, should've read it here...

Yes, Complete is nothing else but Core + Maps combined. We only offer Complete for those who want one download with everything, on platforms with dependency support like Steam WS and PWS you will only find Core and Maps, with Maps having a dependency to Core. You can safely delete any maps you want.

Errors shall never be ignored. Every good programmer knows that. Warnings however are another thing, and - oh wonder - warnings get written to the rpt instead of pestering the player. So BI did everything right here. Period.

What's not in the feedback tracker, doesn't exist: http://dev.cup-arma3.org

Thanks a lot.

Actually I do mind, that server belongs to me and it is not configured to handle a large number of download requests and runs several other services that might get impacted by those. We use it only for internal distribution in CUP and I would kindly ask you to remove the links to that server.

You have to set your zeus module to include unofficial addons as well...

In fact, most of the maps work with the new lighting just fine because with the 1.60 update CUP Terrains 1.1.0 was released which adapted CAWorld to the new lighting.

Not only that, but Vehicles need a crew (CUP Units), and the crew again needs weapons (CUP Weapons)

You can use nearly every ArmA 1/ArmA 2 map in ArmA 3 with CUP Terrains, including Podagorsk, so what exactly is your problem?

With the newly introduced target pods, the view looks like this: That's quite a pity, that way one can't use the new CCIP..... is there a chance for a fix?

Actually, there is - at least if you don't download it from Steam. Steam downloads are placed in a folder that's named after the name in the Steam Workshop.

As long as you adhere to the license (APL-SA), meaning: provide credits to the original author (in this case: CUP) share your source as well (so potential improvements can be implemented back into the original source) keep the license (publish your mod under APL-SA as well)

Open source doesn't mean the source is publicly available, it just means everyone can get access to the source if they want to. Just take a look at the Unreal Engine 4 - it is open source, too, however, you still have to register and be activated to get access to the source. The same applies for CUP.

Well, you are mistaken - your screenshot shows all reported bugs of CUP Terrains in Phabricator. The only ones that might be missing would be the ones that haven't been transferred from Mantis. In case you didn't notice: you can scroll down the "Backlog" panel. If you prefer a "list view" of the tickets, you can quite easily achieve that via the Advanced Search: Now, if I understood you correctly, what you are actually missing, are some pre-defined views. If you would have taken a closer look at the picture I posted earlier, you would have noticed that we as devs have a different Dashboard than the public - and you would have noticed that we have such views. The public dashboard didn't get much love, I admit - we might put the views we have on the public dashboard.

BecauseCamelCaseWritingIsACommonStandardInDevelopmentAndWeExpectAnAdminOfALinuxServerToBeAbleToWorkAroundSuchSpecialNeedsOfLinuxOtherwiseHeWouldBeBetterOffShuttingDownHisServer

Don't copy paste the examples from the manual, ArmA can't handle the encoding of the " signs, you have to enter them manually.

@alanford: I have no idea what your problem with Phabricator is, it is one of the best project management systems out there and its functionality goes far beyond simple issue tracking. BTW, we didn't move to Phabricator, we worked on Phabricator all the time. Only the public bug tracker was on Mantis - and it was a PITA to maintain two bug trackers. Now everything is in one place and you can even see what we are currently doing. Just an example of how it looks for us devs:

I know he did, and that's not the point - he asked why I have a problem with mods not being updated and I explained it to him.

There are tons of mods out there which did work with previous versions of ArmA3, but don't work anymore because of an update and don't get updated anymore, e.g. because the author isn't active anymore. Good examples of ArmA updates breaking mods are the recent hitpoint updates on vests and helmets or the sound changes on weapons (I think it was 1.24 or something like that). So when an update breaks a mod, and the mod author doesn't update the mod (for whatever reason) and we used that mod, we have to remove the mod from our repository. If it is a mod that adds dependencies to a mission, that means all missions done with that mod don't work anymore or have to be reworked. As we strive for consistency and being able to still play missions some time after they were created, we are extremely cautious about the mods we put into our repository and prefer mods with a large developer base (like CUP, RHS or ACE), so there's a high change they don't get abandoned. However, if a mod doesn't add dependencies to a mission and can be removed without consequences, that doesn't matter so much. That's also the reason why I asked about a dependency-free version of your mine detector - or an integration into ACE3.

Will missions created while using this mod still work when this mod gets removed from the modset (e.g. because it doesn't work anymore after an ArmA update)?