Jump to content

Arrow768

Head Admins / Devs
  • Posts

    1,704
  • Joined

  • Last visited

Everything posted by Arrow768

  1. To address a few things. Monetizing PRs We are running a purely non-profit community. This also includes trying to post bounties for PRs or the removal of PRs. While this position might change some day for feature PRs in the form of a bounty system, something like that will never happen for revert PRs. At the current time, do not offer to pay money or try to accept money for a feature / revert PR. Change Cloning to have no traumas I do not want to argue if it was the intention of @LordFowl to nerf cloning with the brain trauma PR or if it was just a side effect. Ultimately it does not matter. I believe that the addition of brain traumas helped to bring a bit more of an impact to death in the game. As its no longer as simple as "put patient into cloning. wait 2 minutes. put them into cryo. wait 1 minute. release them.", which was a common issue before. As @LordFowl is working on further tweaks to the brain traumas and the interaction with cloning, I do not see a immediate need to change the way cloning works.
  2. I am not convinced either. We already have paramedics, emts and emergency physicians, who can (with coordination between these departments) fill in that role.
  3. Voting for dismissal. We already have that for some doors and it is annoying as is if certain people try to constantly open it when they dont have access to it.
  4. Archiving this topic as there has been no response in 48h.
  5. I am going to ignore the snark from your response. As you pointed out, robotics and science already have a desk facing the main hallway which is used to service visitors. If a crew member comes to a incorrect desk, they can be redirected to the correct one by the personell present there or by asking on the radio for the correct desk. If a crew member comes to a unoccupied desk they can use: The ringers, the Radio, the PDA to get the attention of someone who can work this specific desk. Or just walk a few tiles up/down the hallway to the other desk to see if someone is there. Again, the same thing from the "unoccupied desk" apply. Ringers, PDA, Radio, walk to the other desk. The same situation (a single RD working both the robotics and science lab) wouldn't change much with a front desk. The RD would still have to run around between both labs and wouldn't have a lot of time to sit at the desk and wait for people to come by. It is quite likely that you would find the RD in the science lab instead of the front desk. Engineering also has a "front desk", it is very rare that this desk is actually manned by someone. And you have failed to address the removal of the ooc purpose of the library. Oh no, that is just to inform you of a requirement before you touch the book/library code. If you would touch the book / library code you would have to give it a overhaul and couldnt just copy / paste it over because it is old code that will not pass the review process without some adaptations. (And removing them is out of the question as the books are one of the few things where the players can actively shape the server) Indeed. I oversaw that. The idea of having a reader application on the modular computer framework is interesting but not fleshed out well enough. We already have IDs for the books, however those ids are static, would not change during the rounds and can be acquired by ooc means. If kept that way, it would render the "librarian" obsolete for this specific part of the job as once you have the id of a book you can just memorize it and reuse it. On the other hand side if randomized ids were used, then we would have a strict requirement for a "librarian" to get specific books (although we already have that) I believe the outlined suggestion is flawed, as the reason behind it is not to improve the library, but to expand certain sections within research to improve it. And that is something that would be worth pursuing, however not by botching the library and exposing it almost completely to the main hallway (which in turn severely limits its usefulness) (I am definitely not saying that the current library design is ideal -> There are quite a few things that can be improved, but the library isnt improved by reducing the space available to it) Therefore I propose a alternative approach: Rethink the lab layout on the sublevel. There is quite a bit of redundancy between xenoarcheology and the former misc research lab on the main level as well as some other labs. Therefore I would suggest to combine some of those labs, maybe move the misc lab and xenoaflora to the sublevel and combine it with xenoarch/xenobio. (Maybe even combine the xenoflora / xenobio jobs as its rare that there is a xenobiologist and xenoflorist present and the xenobio qualification should imho cover xenofauna and xenoflora) This would lead to some overlap, but I dont think that is a bad thing necessarily. But by doing so you free up a large area on the surface level that can be reused for other things.
  6. Moving this to the dismissed suggestions for the following reasons: OP has not responded within 5 months. All PRs mentioned as "problematic" by the OP have either been tweaked as a result of community feedback or no community feedback has been provided. We already had a suggestions forum, a projects forum as well as serverside polls for contentious features before this topic has been created.
  7. Alright, moving this to the suggestions subforum since that doesn't seem to fit into either one of the requirements outlined in the forum description of the projects forum. Generally I do not see an issue with the size of the science department and no need to increase the size of the science department. The same goes for the "lobby". Other departments (medical / security) have a lobby, because a very large part of their work involves interactions with the general crew. Where as in science the interactions with the general crew are severely limited. (Mostly due to Directive 4) If there is no public traffic, there is no need for a lobby. (The same applies to engineering who does not have a lobby accessible to the public either. They do have a break/conference room combination tough) In addition, one of the ooc purposes of the library is (especially with its easy access to a large section of maint tunnels) is to give the crew a area where they can get together while being relatively unsupervised. The proposed size reduction would place the entire library in view of the main hallway and remove that opportunity. The current station is already huge and I believe at the current time it would be better to see how certain things can be condensed to a more compact and efficient approach than to further increase the size. Outright removing the external book database is out of the question and the database would have to be incorporated into whatever rework that is planned. However, that would pretty much require a rewrite of the library code as it is not up to current coding standards. I do not believe you have explained why books should disappear when they are removed from the library. Without further explanation, I do not see any reason why it needs to be this way, especially since there are quite a few reasons why you would want to take the books with you (studying, reference materials, ...)
  8. I believe JB was mostly referring to that part, and I am curious to hear why you think that there is a difference between a virologist that spawns via normal means and a virologist that spawns via the specialist system. (If it is added)
  9. While you have explained that there is an issue, you did not explain what that issue is, or what should be changed in sufficient detail. Please update your post with information about what you would like to see changed.
  10. Legally, yes. Morally, no. Since it has not been released intentionally. Our current policy is that we do not use code that has not been released intentionally.
  11. Bounties are not a wi setting -> They are configured in the codebase. (In relation to cargo only suppliers, categories and items that can be ordered via cargo are configured in the DB)
  12. This statement is incorrect, as cyberplants have currently a 20% chance to replace a standard plant See here
  13. Has been merged. Moving to completed projects.
  14. PR has been merged. Changes are live. Moving this to completed projects
  15. Indeed, the biggest issue with assigning a security officer to a department is, that they have access to that department. It is going to make antaggery so much more difficult if there is a chance that security could walk in on you at any time, in your own department.
  16. Has been merged and is completed.
  17. Has been merged.
  18. Has been implemented
  19. Has been abandoned / discontinued
  20. Has been abandoned.
  21. Has been implemented.
  22. Has been merged and is in game since quite a while by now
  23. Closing the associated PR as each species should have it´s own unique language that can not be used by other species unless they acquire some kind of device that allows them to understand this language. Naturally such a device should be rather expensive and uncommon. The preferred option to implement this would be the aforementioned implants. An acceptable alternative would be to create a intermediate language between sol common and skrell which would grant a partial understanding of sol / skrell if learned by skrell / humans. (Like we have with SiikTau). Feel free to reopen / recreate the PR once either of these options has been implemented.
  24. Yes, the primary goal of antagonists is to drive a story and generate interaction. But as it stands this isn´t strictly enforced either. It is not really possible to enforce "driving a story and generating interaction", because the whole thing is very subjective and it almost every action generates some kind of interaction. Even throwing a ling / vamp into xenobio generates interaction (between the antag, the scientist assigned to study it and possibly security assigned to guard it). Of course command and security should be encouraged to give the antags some wiggle room early in the round and go along with their gimmicks. But this is a two way road. There is a minimum standard those gimmicks and antag stories need to meet. Let´s take a inspection by a governmental body for example. Ofc there is the possibility that such a thing happens and command should go along with it. Unless there are some obvious clues that something is wrong. If those "inspectors" would board the station with combat rigs and weapons, then there is something off and command should not be expected to let them board. There is a minimum burden of believability the antags need to meet aswell. However, quite a few times they fail to do so.
×
×
  • Create New...