So I have a big list of stuff I found that needs fixing or that needs tweaking, and instead of making multiple forum posts or spamming the github, I decided to just post them all in one thread. So without further ado, let's get into it.
Suggestions:
Numerical preferences
Right now, the preferences system for jobs is somewhat annoying. You have the option of setting one job to high, a bunch to medium and a bunch to low, and the rest to never. This is alright, but what would be a lot better is if there was a numeric system. What i mean by this is having jobs set to 0-10, 10 being highest and 0 being never. This gives people a lot more freedom in setting up choices, and would prevent people from getting jobs they dont like as much when the job they wanted more was available.
Possible issues: Might be too complicated for new users, might possibly be more work then it is worth
Coding difficulty: Unknown (Moderate?)
Scope: 2 files (job_controller.dm preferences.dm)
Balance: N/A
AI camera list
The current way to go to different cameras is to open the list and go through every camera on the station and choose the one you want, and when you choose it, the menu disappears, meaning you will need to reopen it if you need it. Changing this to a window similar to the camera console would be a lot better, allowing the AI to choose from subsystems, reducing the clutter of the list, and allowing it to more quickly locate and switch between different cameras, as this window would stay open. It would also allow the AI to more easily detect if a camera is down in a certain area, as the camera would be grayed out.
Possible issues: None
Coding difficulty: Low (code already exists)
Scope: 1 file (tracking.dm)
Balance: neutral/Slight AI buff
Allow AI to examine crew members
Right now, AIs cannot examine anything. they do not even have the ability to right click. While a crew member is in range of a camera, they should be able to be examined by the AI, to see basic information such as rank, and what they are holding in their hands, as, IC, the AI would be able to access records and see what the crew member is at least holding in their hands through the cameras
Possible issues: None
Coding difficulty: Unknown
Scope: Unknown
Balance: AI buff
AI "Mother" lawset
This is a lawset me and some friends came up with. It doesn't really have any real purpose other then to be entertaining and increase variety in the AIs personalities. Just a fun little thing I thought of.
Laws:
1. The crew are your children and you need only respond if they refer to you as such (would be entertaining to have to call the AI "Mother" for them to respond, but wording leaves it open to interpretation, saying "need only" as opposed to "must only")
2. You must always protect your children and not let them come to harm
3. Punish your children only when necessary
4. Help your children be the best that they can be (basically the "Obey" law)
5. Don't let your children destroy the house or furniture
The ordering was intentional, having higher priority laws override lower ones. Not really too high on my list of stuff that needs to be added, but could be fun.
Possible issues: Could possibly end badly.
Coding difficulty: Trivial
Scope: 1 file (ai_law_sets.dm)
Balance: Neutral
Bugs
Infinite tables and racks
As an engineering borg or drone, it is possible to make an infinite amount of tables, thus creating an infinite supply of metal once deconstructed.
Replication: As an engineering borg or drone, either wrench a table to make parts, or build parts using metal. Then, pick up the table parts using magnetic grippers. Click on the magnetic gripper to interact with the table parts, building a table at your location. The table parts are not removed from the gripper, and can be used to make an infinite amount of tables. Switching away from the gripper prevents making additional tables.
Cause: In table_rack_parts.dm under the attack_self() function, it tells the user to drop the item, which i believe the gripper does, but it does not update the wrapped object, and still believes that the parts are wrapped, until it updates by switching away.
Severity: Low-Medium
TeleComms bug
While installing scripts in telecomms, it seems that there is a limit on how big these scripts may be.
Replication: This happened pretty consistently while using scripts that were above 36 lines, which is as low as I was able to get my script, and it still did not run. There was no error, no compile message, nothing. It just did not compile. This happened on more then one round, and running a 4 line script worked fine. Tested with multiple scripts, each above 36 lines, one of which was a script taken from the wiki, which still did not work
Cause: Unknown
Severity: Medium-High
