The list for flags on Residences is rather large so decided to port them here.
Commands these flags are useful with:
/res set [flag] [true/false/remove] – set flags on residences. /res setall [flag] [true/false/remove] – set flags on all residences over all worlds. /res setallfor [playerName] [flag] [true/false/remove] – Set general flags on all residences owned by particular player /res pset [PlayerName] [flag] [true/false/remove] – set flags on different players
To reset your flags use these commands: /res clearflags – Remove all flags from residence (Not as clear command, only clears what residence you are standing in I believe. /res default [residence] – Restores residence to default flags.
Flags: anvil – Allows or denys interaction with anvil. admin – Gives a player permission to change flags on a residence. animalkilling – Allows or denys animal killing. animals – Allows or denys animal spawns. anvilbreak – Allows or denys anvil break in residence. backup – If set to true, restores previous look of area (WordEdit required). bank – Allows or denys deposit/withdraw money from res bank. bed – Allows or denys players to use beds. beacon – Allows or denys interaction with beacon. brew – Allows or denys players to use brewing stands. build – Allows or denys building. burn – Allows or denys Mob combustion in residences. button – Allows or denys players to use buttons. cake – Allows or denys players to eat cake. canimals – Allows or denys custom animal spawns. chorustp – Allow or disallow teleporting to the residence with chorus fruit. chat – Allows to join residence chat room. cmonsters – Allows or denys custom monster spawns. commandblock – Allows or denys command block interaction. command – Allows or denys comamnd use in residences. container – Allows or denys use of furnaces, chests, dispensers, etc…. coords – Hides residence coordinates. craft – Gives table, enchant, brew flags. creeper – Allow or deny creeper explosions. dragongrief – Prevents ender dragon block griefing. day – Sets day time in residence. dye – Allows or denys sheep dyeing. damage – Allows or denys all entity damage within the residence. decay – Allows or denys leave decay in the residence. destroy – Allows or denys only destruction of blocks, overrides the build flag. dryup – Prevents land from drying up. diode – Allows or denys players to use redstone repeaters. door – Allows or denys players to use doors and trapdoors. egg – Allows or denys interaction with dragon egg. enchant – Allows or denys players to use enchanting tables. explode – Allows or denys explosions in residences. enderpearl – Allow or disallow teleporting to the residence with enderpearl. fallinprotection – Protects from blocks falling into residence. falldamage – Protects players from fall damage. feed – Setting to true makes the residence feed its occupants. friendlyfire – Allow or disallow friendly fire. fireball – Allows or denys fire balls in residences. firespread – Allows or denys fire spread. flowinprotection – Allows or denys liquid flow into residence. flow – Allows or denys liquid flow. flowerpot – Allows or denys interaction with flower pot. grow – Allows or denys plant growing. glow – Players will start glowing when entering residence. hotfloor – Prevent damage from magma blocks. hidden – Hides residence from list or listall commands. hook – Allows or denys fishing rod hooking entities. healing – Setting to true makes the residence heal its occupants. iceform – Prevents from ice forming. icemelt – Prevents ice from melting. ignite – Allows or denys fire ignition. itemdrop – Allows or denys item drop. itempickup – Allows or denys item pickup. jump2 – Allows to jump 2 blocks high. jump3 – Allows to jump 3 blocks high. keepinv – Players keeps inventory after death. keepexp – Players keeps exp after death. lavaflow – Allows or denys lava flow, overrides flow. leash – Allows or denys aninal leash. lever – Allows or denys players to use levers. mobexpdrop – Prevents mob droping exp on death. mobitemdrop – Prevents mob droping items on death. mobkilling – Allows or denys mob killing. monsters – Allows or denys monster spawns. move – Allows or denys movement in the residence. nanimals – Allows or denys natural animal spawns. nmonsters – Allows or denys natural monster spawns. night – Sets night time in residence. nofly – Allows or denys fly in residence. fly – Toggles fly for players in residence. nomobs – Prevents monsters from entering residence. note – Allows or denys players to use note blocks. nodurability – Prevents item durability loss. overridepvp – Overrides any plugin pvp protection. pressure – Allows or denys players to use pressure plates. piston – Allow or deny pistons from pushing or pulling blocks in the residence. pistonprotection – Enables or disabled piston block move in or out of residence. place – Allows or denys only placement of blocks, overrides the build flag. pvp – Allow or deny pvp in the residence. rain – Sets weather to rainny in residence. redstone – Gives lever, diode, button, pressure, note flags. respawn – Automaticaly respawns player. riding – Prevent riding a horse. shoot – Allows or denys shooting projectile in area. sun – Sets weather to sunny in residence. shop – Adds residence to special residence shop list. snowtrail – Prevents snowman snow trails. spread – Prevents block spreading. snowball – Prevents snowball knockback. sanimals – Allows or denys spawner or spawn egg animal spawns. shear – Allows or denys sheep shear. smonsters – Allows or denys spawner or spawn egg monster spawns. subzone – Allow a player to make subzones in the residence. title – Shows or hides enter/leave message in residence. table – Allows or denys players to use workbenches. tnt – Allow or deny tnt explosions. tp – Allow or disallow teleporting to the residence. trade – Allows or denys villager trading in residence. trample – Allows or denys crop trampling in residence. trusted – Gives build, use, move, container and tp flags. use – Allows or denys use of doors, lever, buttons, etc… vehicledestroy – Allows or denys vehicle destroy. witherspawn – Allows or denys wither spawning. phantomspawn – Allows or denys phantom spawning. witherdamage – Allows or denys wither damage. witherdestruction – Allows or denys wither block damage. waterflow – Allows or denys water flow, overrides flow. wspeed1 – Change players walk speed in residence to %1. wspeed2 – Change players walk speed in residence to %1.
```1. Minecraft Username```
-**semi_661**
```2. What time zone are you in?```
-**GMT+2**
```3. Why do you want to become staff?```
-**I really like the server and the people in it , I enjoy helping people out as much as I can and as a staff member I will be able to help in more ways than I currently can at the moment.**
```4. How many hours do you have on Minecraft?```
-**Idk about hours because ive been playing this game since beta/for like 10 years **
```5. How would we benefit from you becoming staff?```
-**Im active in the server quite often even on school days , i can watch over the server and deal with any issue if there isnt any staff online, also i can help u find or make new plugins**
```6. What experience do you have with being staff? Please provide detailed list, along with the servers you have had experience on. (IF ANY)```
-**About the experience thing i do have alot , i dont think i can provide it in detailed list because from the past years that i played minecraft ive been in alot of servers and ive been staff/moderator in most of them , some of them i even owned (the server had an average of 30 people per day and it was quite active) **
```9. How old are you?```
-**Currently im 15 years old but ill be 16 soon**
```10. Do you have a mic?```
-**I do indeed have a mic **
```11. Are you able to type in a legible format?```
-**Well about that u can be the judge from above and the time we played/build stuff together**
```12. How much time will you be putting into this server a week?```
-**Alot of time-- everyday for atleast 6 hours**
```13. Will you be able to get a long with our current staff?```
-**Yes or atleast i hope so im very friendly and i would like to make new friends** ||
The most Pythonic way to check if a list has an even number of elements is to use the modulo expressionlen(my_list)%2 that returns 1 if the list length is odd and 0 if the list length is even. So to check if a list has an even number of elements use the expression len(my_list)%2==0.
As background, feel free to watch the following video on the modulo operator:
The length function is explained in this video and blog article:
A slight variant of this method is the following.
Method 2: len() and Modulo and bool()
To check if a list has an even number of elements, you can use the modulo expressionlen(my_list)%2 that returns 1 if the list length is odd and 0 if the list length is even. So to convert the even value 0 to a boolean, use the built-in bool() function around the result and invert the result, i.e., not bool(len(my_list)%2).
As background, you may want to look at this explainer video:
Method 3: Bitwise AND
You can use the expression len(my_list)&1 that uses the Bitwise AND operator to return 1 if the list has an even number of elements and 0 otherwise. Now, you simply convert it to a Boolean if needed using the bool() function and invert it using the not operator: not bool(len(my_list)&1).
Python’s bitwise AND operator x & y performs logical AND on each bit position on the binary representations of integers x and y. Thus, each output bit is 1 if both input bits at the same position are 1, otherwise, it’s 0.
If you run x & 1, Python performs logical and with the bit sequence y=0000...001. For the result, all positions will be 0 and the last position will be 1 only if x‘s last position is already 1 which means it is odd.
After converting it using bool(), you still need to invert it using the not operator so that it returns True if the list has an even number of elements.
Bitwise AND is more efficient than the modulo operator so if performance is an issue for you, you may want to use this third approach.
You may want to watch this video on the Bitwise AND operator:
Where to Go From Here?
Enough theory. Let’s get some practice!
Coders get paid six figures and more because they can solve problems more effectively using machine intelligence and automation.
To become more successful in coding, solve more real problems for real people. That’s how you polish the skills you really need in practice. After all, what’s the use of learning theory that nobody ever needs?
You build high-value coding skills by working on practical coding projects!
Do you want to stop learning with toy projects and focus on practical code projects that earn you money and solve real problems for people?
If your answer is YES!, consider becoming a Python freelance developer! It’s the best way of approaching the task of improving your Python skills—even if you are a complete beginner.
If you just want to learn about the freelancing opportunity, feel free to watch my free webinar “How to Build Your High-Income Skill Python” and learn how I grew my coding business online and how you can, too—from the comfort of your own home.
[freebies.indiegala.com] Happy Arbor Day! Plant a tree or more, and then reward yourself with a cute, funny and charming hand drawn game with a vast replayability!
[www.indiegala.com] [www.indiegala.com] Save an EXTRA 30% for every bundle & an extra 15% for every store purchase when paying with any supported crypto
Whodunnit... or who will do it?! A new mystery simulation game with player-vs.-player action arrives on the crime scene!
In a manor in the midst of a blizzard, a grisly murder is about to occur. But who will be the victim?
Among the game's characters are one "villain", who carries out a murder, and one "target", the villain's future victim.
The player on the Moriarty side must fulfill objectives to complete their crime, while the players on the Sherlock side must prevent it from happening. Over the course of a match, the villain and the target will slowly come to light.
Will you join hands with Moriarty to outwit Sherlock and take down your target? Or will you team up with Sherlock to foil Moriarty's sinister schemes?
The secret is out: Bleed builds are OP in the current Elden Ring PvP meta, and are just as fantastic in PvE. With enough points put into Dexterity, most Bleed weapons--from the Moonveil to Rivers of Blood--are viable options. But it's the equipment you choose to pair with these weapons that make a Bleed build really tick, and the White Mask is the best of the bunch.
The White Mask increases attack power when you inflict Bleed.
The White Mask is the Helm of the War Surgeon Set. When worn, it increases your attack power by 10% for 20 seconds after inflicting Bleed on an enemy. It even stacks with the Lord of Blood's Exultation Talisman, which increases your attack power by 20%. Combined, you'll consistently be hitting enemies for 30% more damage.
While it's possible to get your hands on the White Mask early in the game, it will take some effort. It's found in Mohgwyn Palace, one of the most brutal Zones in all of Elden Ring. Getting through it under-leveled is a tall order, but when you do, you'll have a key piece of equipment for any Bleed build that can carry you through the whole PvE experience, and even into PvP.
DevOps is a set of practices that automates the processes between software development and IT teams, in order that they can build, test, and release software faster and more reliably.
A DevOps engineer/specialist works with engineers, software developers, system operators (SysOps) and administrators (SysAdmins), and other production IT professionals to release and deploy code in the real world.
DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.
You can play this video as you go over the full article—it’ll play well in the background and you can absorb more information this way:
If you’re interested in learning more about the income and opportunities of DevOps engineers, feel free to check out my in-depth tutorial on the Finxter blog.
Let’s dive into the top 20 skills of a DevOps engineer one by one:
Skill 1: Communication
DevOps engineers do not sit in an office and code all day. They must align goals and coordinate with both the developers and the operations teams. Great communication is crucial for DevOps engineers!
Skill 2: Listening
Many problems can be solved before they occur if you listen either to the developers who are close to the code or to the operators who are close to the customers. As a DevOps engineer, you need to listen to both in order to prevent problems before they happen.
A DevOps engineer is a great listener!
Skill 3: Specific DevOps Tools
There are multiple popular tools specifically to increase efficiency of DevOps engineers. Understanding relevant DevOps tools well is crucial for any professional!
I’ve written an “Income and Opportuntiy” article on some of the most popular tools here:
Skill 4: Basic Programming such as Python, Java, C++
Without understanding code, you cannot possibly become a great DevOps engineer. Yes, you are neither a developer nor an operator so you don’t need to lose yourself in the nitty-gritty details of programming.
However, you need to know your stuff. Because If you don’t know at least the basics of coding, developers and operators alike will run all over you!
DevOps engineers are coders too!
Skill 5: Basics of Scripting Languages
Likewise, SysAdmins are really great in scripting, Linux, SSH, Powershell, and many other scripting languages that help them keep a system running smoothly.
That’s why DevOps engineers need to understand the basics of scripting so they can talk the language of SysAdmins and SysOps engineers.
We already established that communication is important for DevOps—and scripting is communication.
Skill 6: Operating systems (e.g., Windows, Linux, Scheduling)
Technologies fade away. Fundamentals stay. If you learned the basics of operating systems 20 years ago, you’d have built yourself a skillset for life!
DevOps engineers know the basics of operating systems because it helps them easily keep up with new technologies and tools that arise in both the developer and operator fields.
DevOps engineers understand operating systems.
Skill 7: Distributed systems (e.g., Client/Server, P2P)
Yeah, you don’t need to be a distributed system master. But again, you must know the stuff that’s in, say, a 10 page Wikipedia article on distributed systems:
What’s a client server system?
What does peer to peer mean?
How do computers communicate with each other?
What are the basic technologies to create the WWW?
DevOps engineers understand distributed systems because they need to keep up with the latest developments in cloud computing.
Speaking of which…
Skill 8: Cloud (e.g., Amazon Web Services (AWS) and Microsoft Azure)
Deployment is where DevOps engineers shine.
Make no mistake: Learning cloud computing is one of the most important, most sought-after, and most profitable things you can do as a developer! This is also true for DevOps engineers.
Cloud services such as storage, compute, scaling, and machine learning provide a comprehensive IT environment to a wide range of businesses.
This is where the applications get deployed, so as a DevOps engineer you must understand cloud computing very well!
You can find out more about the three biggest cloud providers — and related job roles in our Finxter blog tutorials here:
Before deploying software, you need to test it to find all bugs you can possibly find.
Testing is an integral part of any software engineering cycle because it helps you find bugs that both affect the future development of new features, as well as the deployment and operations of an existing software system.
You won’t be leading a stress-free life if you don’t spend lots of effort testing your application before launching it. This is one of the main responsibilities of a DevOps engineer as well!
Who said it’s going to be easy?
Skill 10: Team Building, Motivation, and Management
DevOps engineers only orchestrate but seldomly build themselves.
The building is done by developer teams that need to be managed. DevOps engineers help in managing those teams.
The operations is done by operators such as SysAdmins that need to be managed as well.
And management is only half of the job — every leader must know how to motivate their teams and reduce friction.
Much of this can be done by listening to the concerns of the implementers. A great DevOps engineers knows this and invests great effort in learning those soft skills.
Speaking of which…
Skill 11: Soft skills
Well, some of the skills mentioned in this article already are soft skills (e.g., listening and communication). However, there are more. DevOps engineers often have great presentation skills and they can figure out problems quickly.
They are sharp thinkers and they remain solution-oriented when bottlenecks in development and operations occur.
Don’t panic!
Really, don’t panic—you’ll learn many of the soft skills just by osmosis being in the field for a long time.
Skill 12: Agile and Scrum
Here’s a great excerpt on the relationship of DevOps and agile from Wikipedia:
The motivations for what has become modern DevOps and several standard DevOps practices such as automated build and test, continuous integration, and continuous delivery originated in the Agile world, which dates (informally) to the 1990s, and formally to 2001.
Agile development teams using methods such as Extreme Programming couldn’t “satisfy the customer through early and continuous delivery of valuable software” unless they subsumed the operations / infrastructure responsibilities associated with their applications, many of which they automated.
Because Scrum emerged as the dominant Agile framework in the early 2000s and it omitted the engineering practices that were part of many Agile teams, the movement to automate operations/infrastructure functions splintered from Agile and expanded into what has become modern DevOps.
Today, DevOps focuses on the deployment of developed software, whether it is developed via Agile or other methodologies.
Why not read the article on Agile — and checking out one of the many free courses online?
Skill 13: Security
Speed of deployment leads to risk in the operations phase: your application or system can get attacked by malicious hackers.
(Yes, some hackers are not malicious.)
Security is one of the pillars of a reliable system that is capable to survive and even thrive in the long term. Without it, your system will eventually fail.
There’s even a term for security for DevOps: DevSecOps. I know it’s not pretty but it delivers the message: security skills are needed and deeply desired by companies seeking DevOps engineers.
DevSecOps stands for development, security, and operations. It’s an approach to culture, automation, and platform design that integrates security as a shared responsibility throughout the entire IT lifecycle.
Skill 14: Automation
Automation is at the heart of any DevOps process.
It’s your bread and butter as a DevOps engineer, so give it the attention it deserves:
Automate configuration tasks for your cloud infrastructure
DevOps engineering is a lot about automation so don’t skip this skill set!
Skill 15: Customer Research and Customer Understanding
Make no mistake—being able to understand the needs and pain points of your customer is a skill.
As a DevOps engineer, you’re ultimately paid by the customers of your organization. They pay the stakeholders of your company who pay you.
So, DevOps engineers know on a high-level basis what their customer need. However, they are not marketing or sales people so a rough understanding is sufficient.
You cannot do everything as a DevOps engineer after all.
Skill 16: Software Engineering
Software engineering is a systematic engineering approach to software development.
Definition: Software engineering examines the design, development, and maintenance of software. It concerns the reduction of problems and issues that arise with low-quality code such as exceeding timelines, budgets, or quality of service (QoS). (source)
This is one of the fields where a detailed study can yield extraordinary results for your practical work as a DevOps engineer.
So, take a mental note to take a course or two on “software engineering”. A great introductory book on the topic is “The Art of Clean Code”.
Skill 17: Site Reliability Engineering (SRE)
Site reliability engineering applies software engineering principles to infrastructure and operations to create scalable and highly reliable software systems.
It is closely related to DevOps in that it helps deliver value to customers by focusing more on operations rather than the creation of a software system.
A DevOps engineer needs to understand the relevant developer tools, at least rudimentary, such as Git, building tools such as Gradle, or IDEs such as PyCharm.
DevOps engineers know the coding tools!
Skill 19: Understanding Operators Tools
A DevOps engineer needs to understand the basic tools used by SysOps and SysAdmins.
Here’s a list of the most relevant (Windows) tools recommended by SysOps expert Paolo:
Notepad++
RSAT: Remote Server Administration Tools for Windows 10)
Sysinternals Suite
PingInfoView to ping multiple host names and IP addresses and watch the result in one table
TreeSize
USB Disk Ejector, allows you to quickly remove USB (and firewire) drives in Windows.
DeviceTool, a Device Manager for administrators. DeviceTool can enable and disable devices remotely – and run on Windows 10.
Rufus, a small portable tool to create bootable USB Flash drives, includes an option to download the Windows.
Microsoft WSUS Client Diagnostic Tool, designed to aid the WSUS administrator in troubleshooting client machines which may be failing to report back to the WSUS Server.
Putty
RVTools, windows .NET 4.6.1 application which uses the VI SDK to display information about your virtual environments. Interacting with VirtualCenter.
vCenter Converter, quickly converts local and remote physical machines into virtual machines without any downtime.
Starwind V2V Converter, makes VM and virtual disk migration between different hardware sets easier by booting the migrated VM in Windows Repair Mode.
Skill 20: Learning to Learn
If you haven’t figured it out already, DevOps engineering is one of the most demanding jobs in any organization in terms of the skills you’ll build over time.
Nobody expects you to have all the skills from the getgo. Be bold and get started — and commit yourself to lifetime learning!
Summary
We’ve explored the following skills of a DevOps engineer:
Skill 1: Communication
Skill 2: Listening
Skill 3: Specific DevOps Tools
Skill 4: Basic Programming such as Python, Java, C++
Skill 5: Basics of Scripting Languages
Skill 6: Operating systems (e.g., Windows, Linux, Scheduling)
Skill 7: Distributed systems (e.g., Client/Server, P2P)
Skill 8: Cloud (e.g., Amazon Web Services (AWS) and Microsoft Azure)
Skill 9: Testing (e.g., PyTest)
Skill 10: Team Building, Motivation, and Management
Skill 11: Soft skills
Skill 12: Agile and Scrum
Skill 13: Security
Skill 14: Automation
Skill 15: Customer Research and Customer Understanding
Skill 16: Software Engineering
Skill 17: Site Reliability Engineering (SRE)
Skill 18: Understanding Developer Tools
Skill 19: Understanding Operators Tools
Skill 20: Learning to Learn
You don’t need to master all of them before starting out—this would be impossible. Just keep them in mind as you gain practical experience and never stop learning!
Where to Go From Here?
Enough theory. Let’s get some practice!
Coders get paid six figures and more because they can solve problems more effectively using machine intelligence and automation.
To become more successful in coding, solve more real problems for real people. That’s how you polish the skills you really need in practice. After all, what’s the use of learning theory that nobody ever needs?
You build high-value coding skills by working on practical coding projects!
Do you want to stop learning with toy projects and focus on practical code projects that earn you money and solve real problems for people?
If your answer is YES!, consider becoming a Python freelance developer! It’s the best way of approaching the task of improving your Python skills—even if you are a complete beginner.
If you just want to learn about the freelancing opportunity, feel free to watch my free webinar “How to Build Your High-Income Skill Python” and learn how I grew my coding business online and how you can, too—from the comfort of your own home.
JDK 13.0.2, 11.0.6, 8u241, and 7u251 Have Been Released!
The JDK 13.0.2, 11.0.6, 8u241, and 7u251 update releases are now available. You can download the latest JDK releases from the Java SE Downloads page. OpenJDK 13.0.2 is available on http://jdk.java.net/13/. New Features, Changes, and Notable Bug Fixes For information about the new features, changes, ...
[www.indiegala.com] [www.indiegala.com] Save an EXTRA 30% for every bundle & an extra 15% for every store purchase when paying with any supported crypto
If your answer is YES!, consider becoming a 
Make no mistake: Learning cloud computing is one of the most important, most sought-after, and most profitable things you can do as a developer! This is also true for DevOps engineers.
