Jump to content

Search the Community

Showing results for tags 'rdms'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Starting Zone (EN)
    • Rules & Announcements
    • General Discussions
    • Off Topic Discussions
  • Starting Zone (DE)
    • Regeln und Ankündigungen
    • Novark's Registratur
    • Allgemeine Diskussionen
  • Starting Zone (FR)
    • Règles et Annonces
    • Registres du Novark
    • Discussions générales
  • Beta Discussion
    • Beta Updates & Announcements
    • Idea Box
    • DevBlog Feedback
    • The Gameplay Mechanics Assembly
    • Streamer's Corner
    • The Builder's Corner
    • Innovation Station
  • Organizations
    • Org Updates & Announcements
    • Novark's Registry
  • Fan Art, Fan-Fic & Roleplay
    • Novark Agora
    • Novark Story Time
    • Novark Art Gallery

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location:


Interests


backer_title


Alpha


community_id

Found 11 results

  1. I did not see a way to post into upvote and did not see this feature suggestion there or here. It would be nice in the RDMS to be able to target Org Legates vs Org as a whole. Currently you have to manage rights by creating an actor that contains multiple members and adding/removing people from that. If you could target Org Legates in addition to the org that would keep Org leadership from having to create somewhat convoluted RDMS rules. Bonus points if we could have multiple levels in the org beyond just "member", "legate", and "super legate". And be able to target those from t
  2. I added this to the Upvote site, but I will also post it here for discussion: Players logging off on other people's constructs is a problem, for numerous reasons. Players that log off on someone else's construct should be "kicked off" the construct. When a character logs out of the game on a construct that they do not have permissions for (defined either by a construct-wide RDMS right similar to Board Construct, or by applying Use rights on a "Security System" element), their character should be moved outside the build area of the construct and their physics should be de-parented.
  3. Idea: Add 20 more rights to RDMS system for each build mode tool and it's negation (the alt key). Perhaps add an expanding menu to keep rights UI simpler. Why: A good sandbox game is one where cooperation and organization among players is rewarded. With respect to industrial complexes, the game is already struggling with making teamwork necessary, let alone encouraging it. Current RDMS system is one reason why teamwork is discouraged. Mega factories take a lot of time to build, and build right to delegate building. The build right is too powerful right now. Someone can scoop your
  4. Basically I can't find the option in the RDMS that I can use to prevent members from unclaiming items. It seems like every org member can unclaim items.. How do I prevent that? Can I create a sub-org that I claim the items for? And then how do I allow industry to work with these claimed items? (I know about the difference between unclaiming and stealing.. Stealing would atleast result in a notification) Thanks in advance.
  5. Hi all, I had a quick look and didn't see a post for this so apologies if there is already. Played a little last night and found that adding every single right to a policy is time consuming. Can we get an 'Add all' button? Additionally, is it possible to create sub headings? For example, rights that are to do with territories would have the Territory sub heading, or things to do with machines, vehicles or other objects might have something else like Vehicles or Objects. Then each of these sub headings can be bulk added to a policy as well? Jus
  6. It would be useful if construct owners could permit specific players to build only in specified zones of a construct via RDMS. This would be especially useful in, say, an apartment complex, where you could allow a resident to edit and furnish their apartment and not any other part of the complex. Construct owners wouldn't have to find workarounds like splitting it up with multiple core units, for example.
  7. what I'm talking about here is essentially being able to trade permissions for specific parts of a construct in exchange for money or whatever. these permissions would have a time limit on them, and (crucially) the person who owned the construct would NOT be able to modify those permissions until the time limit expired. one example of this would be a parking lot/hangar bay in a city. if I wanted to park my ship inside a hangar bay I would purchase the permissions to open and close the main doors, toggle lights, open some storage inside the bay, etc. if I just wanted to stay there for the night
  8. Hi everyone. Until now, we couldn’t manually manage (remove/promote) Legates in an organization easily on the administration side. Since Yesterday, we are able to use a feature simplifying considerably the process. As we already mentioned many times in the past, we (Novaquark) don’t want to involve ourselves in the management of organizations created by players. However, we are also aware that the current (and temporary) state of the management system contains obvious flaws. You know it. We know it. As this is still “work in progress”, we hoped that organizations
  9. I would like to know if RDMS will allow us the concept of Holding Organisations and Subsidiary Organisations. Case 1: When a single person owns both the holding organisation and subsidiary organisation. Case 2: When the owner of both the holding organisation and subsidiary organisation are different.
  10. (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 Porta
  11. Rights and Duties Management System (RDMS) will be one of the very powerful customization systems in DU. Read the DevBlog here if you have not already. Effectively tags can be used to give access to assets etc etc. I assume that in the current RDMS system, a player will know what tags he/she has. Effectively these are like keys to a spaceship or passcard for a door. The suggestion of this topic is that a tag can be placed on a person without their knowledge. These invisible tags would not be able have duties connected to them because this could lead to a player losing money without knowin
×
×
  • Create New...