Search the Community
Showing results for tags 'management'.
Found 3 results
Dear NQ, this is not really an idea but more a kind request. As a lot of us (players) are going to gather in the Dual Universe adventure, the need to decently manage our corporation will come. At FrogSwarm we are a bit elitist about security and corporation management and so, we already kindly asked for web API to be able to manage our members using our tools. So in the wait of the API, can you at least, since there is no private information to be hidden here, make the user account publicly available instead of restricting it with a dual id logon (ie: https://community.dualthegame.com/accounts/profile/Silmerias)? Then we could crawl it with our tool to start using some identity security check like we do with Star Citizen since the citizen dossier is public available (https://robertsspaceindustries.com/citizens/Silmerias) The tool behind the scene is asking a player to add a temporary code in the 'About me' section to be able to validate his account under our tool and ensure us he's the owner of the dual universe account. The idea was any
A list which lets us define who can not interact with an element. With only a permission list no combination of sensors can distinguish between: Only an authorized person is in range Both an authorized and any other person are in range For example, you can not have a door which automatically opens only when you're alone. It would also help attempts at starting civilizations, since it would allow having public spaces by default and banning particular people from interacting or building in them.
(Posted Friday 31th of March 2017 on the DevBlog) Hi everyone! Today we are going to talk about the organizations in a more detailed way! As usual, keep in mind this is how the organizations are planned to be implemented for the official release of Dual Universe, not for the Alpha. As it is still work in progress, some mechanics might change based on community feedback and/or for technical reasons. For the Alpha (currently planned for September), we will most likely have a basic version similar to what we currently have on the Community Portal*. Veteran MMORPG players will undoubtedly be familiar with the basic concepts of guilds and clans from other games so some of this information might feel like a review to you. However, we wanted to give a complete overview of Organizations so that even players new to Massively Multiplayer games would understand what Organizations are, the benefits of joining one, and why you might choose to create one. If you have friends who like building games but haven’t ventured into MMORPGs yet, then they might be interested in this Blog post. (*we are talking here of the current version on the Community Portal + an update scheduled to add a Super-Legate rank and many changes for Members and Legates rights) What exactly is an Organization in Dual Universe? It’s a Moral Entity able to: - accumulate “Quanta” (the in-game currency) - own Assets (Items and Constructs) - gather Player Characters under the same flag for a common goal. - create a hierarchy, with ranks and roles for all Player Characters gathered in it. - be a member of another Organization, just like a Player Character. What are the purpose and benefits of an Organization? - It enables players to accomplish greater goals than what a player could do alone: The ability to pool resources and in-game currency will help a lot. - It consolidates the continuity of a long-term project: Players can enter and leave an organization without heavily impacting long-term projects supported by the group. - It gives a political dimension to the game: Rights & Duties can be transferred from one Player to another, and Powers are decided by the Legates through a vote (if the Organization is a democratic one). - It legitimizes conflicts between several group of Players: This will enable members of different Organizations to fight between themselves and kill each other, without being the target of reprisal mechanics (like bounty hunting) if a war has been declared between the said Organizations. RDMS (Rights & Duties Management System) in an Organization: - Different actions can be done on each Asset: each possible action is defined as a Power. - Access to a Power on an Asset is given by a Tag. - Each Power has a list of Tags associated to it. - Each Player Character has a “wallet” of Tags. Here is a quick example illustrating the system: Here we have an Asset having 3 Powers: Use, Sell and Edit. The Organization is composed of 3 Player Characters: Alice, Bob and Warren. In this situation: - Only Bob can edit the Asset. - Only Warren can sell the Asset. - All three can use the Asset: 1) Alice can use the Asset through the Tag “alice” 2) Bob can use the Asset through the Tag “bob” and “squad1” 3) Warren can use the Asset through the Tag “squad2” But that’s not all: you will be able to create more complex administration rights by creating a hierarchy between Tags! Let’s say “stock_management” is the parent Tag of “ammo_management” and “raw_materials_management”. If a player has the Tag “stock_management” in his wallet of Tags, he will be able to use or manage any of the Organization’s Assets having the Tag “ammo_management” or “raw_materials_management” depending on which powers are associated with those tags. The Rights and Duties Management System is also used to create the Functions. A Function will contain various Tags defining an assignment. Let’s say that Warren gets the Function “President” in the Organization “MyOrg”. Now his Tag Wallet in “MyOrg” looks like as follow: As the President, Warren will have the ability to declare war to another Organization. A Treasurer will manage the Organization bank account , a Gunman will be able to use some (or even all) weapons and military Elements to defend the Organization, etc. Of course, we will provide standard, ready-to-use Functions such as President, Treasurer, Miner, Industrialist, Gunman, and Military Officer to save time and allow players to quickly get their Organization operational. Acting in your name or in the name of an Organization: A Player Character can be a member of several Organizations. Therefore knowing whether they are acting on their own behalf or on behalf of an Organization (and which one) is very important. We call “Role” the state where a Player Character represents an Organisation (or just himself). By default, a Player Character has at least the Role where he can represent himself. Under each role, the Player Character has a Tag Wallet. When a Player Character is accepted into an Organization, the Player Character automatically gets an additional Role where he can represent the Organization. While under the Role representing the Organization, all the actions can affect the Organization. For example: - Receive Quanta on behalf of the Organization: Quanta are transferred to the Organization - Craft an Element: the Element is owned by the Organization (not the Player) as a result. - Harvesting resources: The resources are owned by the Organization (not the Player) as a result. Example: After declaring a war that displeased most of the members in “MyOrg” (which has a democratic system), Warren has been demoted from his function of President and kicked out (Warren, what have you done? You should have consulted your guildmates before doing that!). He has now joined a new organization, “Corpo1”, as a miner and has just discovered he can act in the name of “Corpo1” or act just for himself. In the windows where he could choose his active Role for the time being, it will look a bit like this: However, keep in mind this is a simplified view of the Tags: as it will probably become quite common to have the same name for a Tag in different Organizations, the Tags will be “scoped” to avoid conflicts. Let’s say Warren is accepted again in “MyOrg” and gets the Tag “miner”, just like in “Corpo1”. To avoid conflicts, the Tags will be scoped as follow: Political Action (Vote) in an Organization: Only Legates will be able to vote. Votes could be used for administrative decisions like: - Accepting a new Member in the Organization - Excluding a Member from the Organization. - Giving a Function to a Member - Changing of the Vote rules Of course, the list of administrative decisions above is far from exhaustive. A Legate can also give his/her ability to vote to a representative (another Legate) Above, the Organization “MyOrg” has 5 Legates: Kim, Bob, Alice, John, Steve. John and Steve give their right to vote to Alice. Alice now counts as 3 votes. However, she will be absent for the next vote so she delegates her right to vote to Kim. Bob also gives his right to vote to Kim as he trusts her completely. In the end Kim will have all the votes so she will be able to make important decisions for the Organization without involving the other Legates. Big responsibility for Kim! We hope this has given you a better grasp of how an Organization will work in Dual Universe. Not all related game mechanics have been explained as it’s still currently in development, so there will be probably a second part later. As always we can’t wait to read your feedback of what we’ve discussed so far! The Novaquark team