MidnightRunner

I tend to call out people if they are too rude and this time it's you @MidnightRunner. It doesn't matter how frustrating something is, stay polite in public channels. That's a fair account. I did lose my cool at times yesterday.

The faux outrage is a little misplaced since we started using it months ago

The use of discord rich presence does not constitute recruitment/advertising (Especially since Ahoyworld has now incorporated it) Playing with another community does not constitute recruitment/advertising

Honestly, I'm sick of being polite, I'm sick of trying to be fair in this fucking witch hunt. You of all people, our ex community referee, should understand the burden of proof. The burden of proof was never satisfied, you would know this is you stayed around long enough to see the detailed report to staff from CS. I am also very disappointed that many "pillars of the community" would have been passing around a document supposed to be privy to Core Staff only. There is only 2 places that could come form, the person who filed the report or the poor member of Core Staff who resigned after being disagreed with. Fuck this victim complex. You among others tried to undermine the application of Ahoyworlds principles in some failed attempt to get your own way. The mob mentality ruled. But no Core Staff taking time to properly investigate and not just blindly ban people without evidence makes us the bad guys. Get real.

Note to all members from the Core Staff team: As several of you have already noted the public staff team has been reduced in number, I will detail here what information I can while respecting the privacy and confidence of those involved. On May 20th Core staff received an admin report (Note 1) against 2 members of staff. Within 3 hours a member of Core Staff concluded in favour of the report and took action against one of the reported parties, removing them from a staff role they held, this is not in line with the standard practice for admin reports (Note 2). In the days that followed Core Staff followed the procedure noted below in Note 2. We believe that our ability to investigate the situation in the manner described in Note 2 was harmed by the way the report was handled initially. This fostered an "Us V Them" mentality and likely led to the reactions explained in the next paragraph. During this time following the demotion of a staff member, several members of staff aware of the demotion and of the admin report (aware of its existence but with no access to its content) came to the conclusion that the reported persons were guilty and should be banned. Some even stated that they would resign should Core Staff not find in their favour. Core Staff asked for calm while they completed a proper investigation into the matter. Following the several day investigation Core Staff met and reviewed all the gathered and available information and found that there was no clear evidence that a rule had been broken. There was what could be called circumstantial evidence but nothing more. A number of members of staff unhappy with decision resigned, including the member of Core Staff who had acted in error in the first instance. Core staff believe that they acted with fairness to all parties in mind. We would be setting a worrying precedent if staff members were allowed to dictate who was guilty without reviewing the evidence first, especially in the case of an admin report. (Note 3) I would like to stress that other than the person described above no members were removed from a staff role. The nature of these events is unfortunate and regrettable. Many of the staff members who resigned were members whom I call my friends, and I along with the rest of the Core Staff team would like to thank them for all they have done for Ahoyworld during their tenure and wish them the best in the future. If anyone has any questions relating to this please direct them to me and I will be happy to share any information I can while respecting the privacy of those involved. Regards, Midnight Note 1 An Admin report is the tool available for members to submit a report relating to a member of staff. It is similar to that of the "Player Report" function except an Admin Report is visible to Core Staff only. Both can be found along the top bar of the forum under the report heading. Note 2 The normal procedure when Core Staff receive an admin report is to spend a number of days speaking to those involved and collating all available information on the matter before meeting as a team and reviewing the information gathered and making a decision on the matter. This allows Core Staff to investigate a situation thoroughly, with discretion taking our time to come to a fair conclusion on the issues reported. Note 3 Staff members are routinely included and their conclusions used in respect of player reports but not Admin reports as it would not be appropriate.

Mission Name: PMC Ops Revenge Week 1 Server Details: IP: 116.202.224.207 Port: 2302 Mods Required: Arma 3 Preset CHADS Revenge.html (Plus usual optional mods) TS address: ts.ahoyworld.net TEAMSPEAK MISSION BRIEFING FOR ALL PLAYERS WILL BEGIN AT THE TIME STATED IN THE TITLE Expected Mission Length: 120+ minutes (may go over or under expected mission length) Player Slots: 43 Platoon // 3 man element Alpha - Delta // 9 man elements Nomad // 2 man recon element Vortex // 2 man pilot team Situation The CHADS have deployed to Chernarus as a contract force to securely deliver humanitarian aid. Corporate has also accepted an unofficial contract to covertly help the local resistance undermine the Chernarus government. The local government, backed by Russia, has been putting down a rebellion and the civilian population has taken the brunt of the reprisals. There are also criminal organisations operating in the area which the CHADS may encounter. Assets: 1 x UH-60M 1 x MH-6M Various ground support vehicles Friendly Forces: UN Observation force Chernarussian rebels Enemy Forces: Officially none Neutral Forces: Chernarus Defense forces Russian Military observers/advisors Civilians: Civilian presence to be expected, concentrated in built up areas. Mission Our first mission is to deliver 6 units of aid to 3 locations in the local area. While this happens we must also make first contact with the local rebel elements. Execution Objectives: 1. Deliver aid supplies to the designated targets 2. Meet with the rebel elements at the agreed meeting point 3. Maintain the cover supplied by the humanitarian mission Movement Plan: At Commanders discretion Rules of Engagement: Enemies may be engaged on sight based on current squad orders Civilians are present in the area so collateral damage is to be kept to a minimum. Admin & Logistics Equipment & Resupply: At the commander’s control, assets are available at base to facilitate this. Reinforcements: Unlimited At commanders discretion, transport assets are available. Command & Control Command: Overall command lays with codename "Overlord" who will set objectives and ROE. Operational control on the ground lies with the Platoon Commander. Communication: Radio channels are set for each element and can be viewed as part of the map. Platoon has limited discretion for change but structure is to be maintained.

Frontlines Version 0.4.6 update for 16/06/21 [Tweaked] Map lights added to all factions [Tweaked] HuntIR rounds added [Tweaked] Counterattack timer increased by 5 minutes [Tweaked] If counterattack is successful, garrison strength will match average across the region [Fixed] Sometimes PoW's could not be captured [Fixed] Sometimes the helicopter mobile respawn couldn't be used

The Ahoyworld Mod is constantly growing and with the hard work of our dev team it now provides both custom factions and many useful functions. However we have noticed that the dependency on BAF and RHS has limited it's usefulness. To this end we have split the AW mod into two separate mods. Effectively Ahoyworld Functions and Ahoyworld Factions. This 2 mods are available now for mission makers to make use of and will be implemented to Fronlines on EU3 Wednesday 16th June in time for our weekly Frontlines gamenight. The original mod will remain on the workshop for the short term but will be taken down after the switch is complete. Links: Functions Mod: https://steamcommunity.com/sharedfiles/filedetails/?id=2511307284 Factions Mod: https://steamcommunity.com/sharedfiles/filedetails/?id=2511307886 Any questions please ask.

The next iteration of the CHADS will start this Friday 18th June. Setting: The CHADS fresh from leave after their stint in Africa have gotten an aid contract in Chernarus. The local governement forces, backed by Russia are fighting against an uprising of local forces. Civilians have been hit hard and the UN has sent aid workers to the area. The CHADS have been contracted to deliver this aid. However, since the events in Finland the CHADS have been looking for a way to get back against the Russians they have also taken secret contracts with the local rebel forces. The CHADS will have to maintain the guise of the provision of humanitarian aid, while working covertly to undermine government forces. Expect the brief for the first mission in the next day or so. Factions involved: Chernarus Local Government Rebel Chernorussians Local smugglers Serbian UN detachment Modlist: Arma 3 Preset CHADS Revenge.html

Frontlines Version 0.4.5 update for 11/06/21 [Tweaked] Crates can now spawn anywhere within a town/city's sector [Tweaked] Handling of crates now uses base classes [Fixed] Units that are captured will no longer be deleted once a secondary objective is left [Fixed] Crates will no longer despawn when ACE loaded after IED factory

Changelog for 3.4.05 - [Fixed] Typo - [Fixed] Briefing for rescue pilot mission - [Fixed] Destroyer not despawning on completion - [Tweaked] Radio tower subobj can now spawn on all maps - [Tweaked][Cam Loa Nam] Missing AK ammo added to arsenal - [Tweaked][Cam Loa Nam] RKG-3 has been added to the arsenal - [Added][Cam Loa Nam] More AOs

Changelog for 3.4.05 - [Fixed] Typo - [Fixed] Briefing for rescue pilot mission - [Fixed] Destroyer not despawning on completion - [Tweaked] Radio tower subobj can now spawn on all maps - [Tweaked][Cam Loa Nam] Missing AK ammo added to arsenal - [Tweaked][Cam Loa Nam] RKG-3 has been added to the arsenal - [Added][Cam Loa Nam] More AOs

Changelog for 3.4.03 [Added] Destroyer side mission [Added] Map param to remove overcast at night (off on altis, on on Cam Loa Nam) [Fixed] Prio arty ammo truck not being cleaned up [Fixed] Jets on which the ejection seat was used not being cleaned up [Tweaked] Made tank platoon subobjective compatible for all maps [Tweaked] Weapon shipment side mission: civies are now more random [Tweaked] Range from the center at which squads will patrol in the main AO [Tweaked] Side missions will spawn a given distance away from a base or FOB [Tweaked] Expanded the garrison blacklist for the main AO to include prisoner cages [Tweaked] AO garrison: buildings will have a max garrison of 50%, max 40 garrison units will be created [Added][Altis] Prairie Fire builboard - [Tweaked][Cam Loa Nam] Changed classnames of player units [Tweaked][Cam Loa Nam] Infantry can be copilot in the AH-1 and UH-1 [Tweaked][Cam Loa Nam] Set mission date to have a full moon [Tweaked][Cam Loa Nam] Main base layout (just a bit this time) [Tweaked][Cam Loa Nam] AA weapons of F4s are assigned to the copilot again [Tweaked][Cam Loa Nam] Default vehicle loadouts now include backpacks and flare launchers [Tweaked][Cam Loa Nam] Arsenal restriction: Added mission weapon for grenadier and more face and headgear [Removed][Cam Loa Nam] Seahorse from the side mission rewards list

Changelog for 3.4.03 [Added] Destroyer side mission [Added] Map param to remove overcast at night (off on altis, on on Cam Loa Nam) [Fixed] Prio arty ammo truck not being cleaned up [Fixed] Jets on which the ejection seat was used not being cleaned up [Tweaked] Made tank platoon subobjective compatible for all maps [Tweaked] Weapon shipment side mission: civies are now more random [Tweaked] Range from the center at which squads will patrol in the main AO [Tweaked] Side missions will spawn a given distance away from a base or FOB [Tweaked] Expanded the garrison blacklist for the main AO to include prisoner cages [Tweaked] AO garrison: buildings will have a max garrison of 50%, max 40 garrison units will be created [Added][Altis] Prairie Fire builboard - [Tweaked][Cam Loa Nam] Changed classnames of player units [Tweaked][Cam Loa Nam] Infantry can be copilot in the AH-1 and UH-1 [Tweaked][Cam Loa Nam] Set mission date to have a full moon [Tweaked][Cam Loa Nam] Main base layout (just a bit this time) [Tweaked][Cam Loa Nam] AA weapons of F4s are assigned to the copilot again [Tweaked][Cam Loa Nam] Default vehicle loadouts now include backpacks and flare launchers [Tweaked][Cam Loa Nam] Arsenal restriction: Added mission weapon for grenadier and more face and headgear [Removed][Cam Loa Nam] Seahorse from the side mission rewards list

Uraaa!

Mission Name: The Parthian Incident Week 3 Server Details: IP: 116.202.224.207 Port: 2302 Mods Required: Arma 3 Preset Parthian Incident.html TS address: ts.ahoyworld.net TEAMSPEAK MISSION BRIEFING FOR ALL PLAYERS WILL BEGIN AT 18:00 UTC Expected Mission Length: 120+ minutes (may go over or under expected mission length) Player Slots: 45 (31 USMC, 14 VDV) Situation After the events of the previous mission fighting has intensified between the Russian backed government forces and the US backed revolutionaries. Neither the US or the Russians have made any signs of backing down and with stories leaking to the press about direct confrontations between the countries forces all eyes are on the region. The region hangs in the balance. Currently it is unclear who will be the victor as the government forces struggle to contain the revolutionaries expansion. Assets: Redacted for mission security Non player Factions Involved: Iranian government forces Iranian revolutionary forces Civilians: Civilian presence to be expected, concentrated in built up areas and centred around villages. Mission Redacted for mission security Execution Objectives: Redacted for mission security Movement Plan: At Commanders discretion Rules of Engagement: Rules of engagement are dependant on objectives and commanders orders Civilians are present in the area so collateral damage is to be kept to a minimum.

Frontlines Version 0.4.4 update for 02/06/21 [Added] Build menu overhauled with a new GUI and more information [Tweaked] VDV no longer have access to T-80 and T-90

Update to the Mission makers Framework. should be a bit more efficient than previous versions. VR_Template_May_21.vr.zip (Requires CBA and Ace) Contains updated zeus code TFAR specific code (which can be commented out) Radio channel chart support Improved event handling Updated diary Removed CHVD in favour of AW Mod Cleaned up mission

Hello and welcome. Glad you are enjoying our Invade and Annex servers.

Mission Name: The Parthian Incident Week 2 Server Details: IP: 116.202.224.207 Port: 2302 Mods Required: Arma 3 Preset Parthian Incident.html TS address: ts.ahoyworld.net TEAMSPEAK MISSION BRIEFING FOR ALL PLAYERS WILL BEGIN AT 18:00 UTC Expected Mission Length: 120+ minutes (may go over or under expected mission length) Player Slots: 45 (31 USMC, 14 VDV) Situation Following a US incursion into Iranian territory and direct conflict between the two factions the Iranian government has declared war on America. The Americans not wanting to get caught in another lengthy middle eastern war have decided to provide support to the fledgling anti government factions in Iran rather than sending in it's full force. These revolutionaries have been emboldened by the US incursion as it has given a bloody nose to the seemingly overpowering government regime. Meanwhile, US Russian relations have not publicly shown any reaction to the engagement between Russian and American forces. It is likely that neither side wishes for the resultant escalation that may bring. However, Russia have taken the opportunity to publicly side with Iranian government forces against what it calls American interference in the region and have offered to aid the government forces in their struggle. It is unknown at this time what form this support may take. Assets: Redacted for mission security No player Factions Involved: Iranian government forces Iranian revolutionary forces Civilians: Civilian presence to be expected, concentrated in built up areas and centred around villages. Mission Redacted for mission security Execution Objectives: Redacted for mission security Movement Plan: At Commanders discretion Rules of Engagement: Rules of engagement are dependant on objectives and commanders orders Civilians are present in the area so collateral damage is to be kept to a minimum.

Frontlines Version 0.4.2 update for 19/05/21 [Tweaked] Zeus modules are now created as required in the mission [Removed] Zeus modules from the mission.sqm

Frontlines Version 0.4.1 update for 19/05/21 [Added] Vehicle crew drivers are now basic engineers [Added] CBA setting to disable the resources UI on the map [Tweaked] Squad engineers are now advanced engineers [Tweaked] Opfor objectives now consider 5 areas along the frontline [Tweaked] Server now runs more object initialisations through CBA Events [Tweaked] Default loadout added to ACE Arsenal Default Loadouts [Fixed] Deploy menu not opening all the time [Fixed] Naming in SQM

I won't comment on the Arma ban but context on my name being shown is his joining of and subsequent ban from Discord today.

Hi @malkiqrambo, Please double check that the version of JSRS you are using is the one which appears in the below https://forums.ahoyworld.net/topic/9331-ia-accepted-addons-repository-info/. If this is the case then you could try to repair the mod by; Opening the launcher and selecting the mod On the right side is a button with 3 dots click that and click repair. Hope this helps.

I have a full PDF copy of this in my Arma root folder along with a game manual.. I think it is part of the game install For me it is in: SteamLibrary\steamapps\common\Arma 3 arma3_manual.pdf arma3_keyboard_layout.pdf