Zahzi

Both tech & I couldn't be around earlier in the day. Could've not bent the knee and not had a server or dev around if something went wrong

Changes Included changes from the January update (textures, hints, etc)- hotfix for that coming soon Added Service stations near all rebels on Malden & Tanoa "Safe Redeploy" is now at the bottom of the scroll options Logging in and spawning directly at a rebel will no longer void your protection Temporarily disabled problematic code that caused network lag spikes under load

@Mako smh will be fixed in the hotfix

Spangling a player that is shooting at you as a last resort (life or death), then leaving the area to let them reset before engaging. If you're driving in an Ifrit and have a clear ability to leave without killing, but you wait and frag, you've done a VDM.

This is the way it's always been in the rules. If you spangle someone, you leave. Once again, this is not a rule update. This is simply a reminder that VDM and DPI jumping isn't allowed, and some examples of the rule since there have been lots of confusion in tickets recently.

Another s3 quest today with a few small changes. Probably going to stick with having these weekly instead of the planned biweekly given their popularity. Other maps will probably come soon. Fixes Transformers at Chapoi alpha no longer despawn when hit by vehicles Chapoi north rebel vehicle spawner now actually works Admin whitelists can now spectate players while dead without waiting for a 3m cooldown

Yeah, let's waste dev time making a system that let's admins waste time doing tickets disabling and eventually reenabling casino for gambling addicts instead of comp requests/player reports.

Olympus Developer Applications We're currently looking to fill some developer positions for Olympus. This will most likely be at a "Contributor" level to start. If you're interested in applying for either role please read below and submit an application in the support section of the forums for "Developer/Designer Application" then select the desired position. Those who have applied previously are welcome to re-apply. I highly suggest putting good effort into your application for best results. We would rather have quality vs quantity. Developers: Developers are seen as staff members. They are invited to staff meetings, seen as staff on the directory and within the game, have staff perks, generous rewards, and significant payouts. However, Developers are expected to commit more to the mission file. They should be well versed in SQF and basic concepts should be understood fully. They are also expected to act as staff. Contributors: Contributors are not seen as staff. They are not invited to staff meetings and do not see rewards to the degree that staff do. However, they do receive rewards for their work and are expected to maintain a level of activity (not as heavy as Developers). They may still be learning SQF and basic concepts should be understood to a moderate degree. They are not expected to act as staff, however they are expected to act with maturity. Requirements: 17+ Years of Age (exemptions can be made, however there is a level of maturity expected) Basic knowledge of SQF (ability to create a script to perform on demand basically) Knowledge of nearly all potential loop structures and formatting for them Knowledge of different variable types (Global/Local/Public) and how they function in Arma 3 General understanding of scopes General understanding of the different data types available for Arma 3 Basic knowledge of Multiplayer/Dedicated Server Environments for Arma 3 Basic knowledge of MySQL as well as able to form general SQL query statements (for server-side database queries) Basic Arma 3 GUI design knowledge Basic knowledge of GitHub or other version control repository provider (GitLab, BitBucket, etc) Ability to demonstrate the above before acceptance Preferences: 18+ Years of Age Knowledge and experience with other coding languages. Basic knowledge of a programming language Experience with SQF Development Experience with the Olympus Community Experience with the Olympus ArmA servers Good Reputation on Olympus Strong Database Knowledge Ability to show unique and creative styles in reference to Altis Life, coding, and problem-solving **This cannot be stressed enough when it comes to work examples** In your staff application, please answer the following questions: Why do you feel you are a good pick for the development team? Are you familiar with any other coding languages? What is your programming background (if any)? What is your schedule like in a typical week? How well do you work with a team? Can you work well under pressure (there will be times when at least a slight crunch time is expected)? Anything else you would like to add? Applications should not be posted as a reply. They should be submitted as a "Developer/Designer Application" under the support tab or by clicking below. Developer Application If you have any questions or wish for more information regarding either of the positions feel free to PM @Zahzi or @Civak. Thanks, Olympus Development Team

Look at this roleplayer