* Store Cargo Load Errors in the DB
* Bump SQL Version number
* Remove displaying db save errors (Already handled by Execute)
Co-authored-by: Werner <Arrow768@users.noreply.github.com>
* Further CCIA Adaptations
Changes the CCIA Recorder to ask if there was Antag Involvement in the Incident and adds additional db changes.
* Implements Review Changes
* Recorder Interaction Changes
Changes the recorder click interaction for agents and adds the options to reset the recorder
* Displays the report topics
Shows the internal topic to the interviewing agent upon selection of the IR
Shows the public topic to the interviewee upon scanning of the fingerprint
* Update the status of the report if a user claims antag involvement.
* Asks the char how the antags influenced them.
* Fixes SQL Migration Error
* Fix SQL Migration and Query Bug
* Fixes a issue with the report selection and the query saving
* More sanitization
* Cleans up the Database.
Changes the charset to utf8mb4
Changes the collation to utf8mb4_unicode_ci
Adds foreign keys to various tables that use the ckey
Cleans up various inconsistencies (key used in a ckey field, wrong dates, ...)
Changes the columns in ss13_cargo_items that hold json to JSON
* Corrects Migration Number
* Only drop tables if they exist.
* Attempts to please travis
* Moves another comment
* Moves the sol swords out of energy and into misc
Loads custom synths from json or SQL as opposed to a txt file. Adds support for multiple borg sprites, ai chassis and custom ai hologram sprites as opposed to one sprite per player. Adds the ability to use custom pai sprites
view duty log verb and changes the way their recorder works.
CCIA recordings are now written to the database once the interview is complete (if enabled) and printed out.
Intent of this PR: make factions actually matter.
How we're going to do this:
Make factions limit job choices.
Make factions have alternative loadouts that override job uniforms
Make factions be visible in the employment records.
Revert existing faction loadout options or put them behind a preference, in favour of new shit.
Adds SSDocs, which manages randomly spawned documents.
These documents can be specified in a json file or in a database.
Adds /obj/random/document and adds /obj/random/document to the loot pool of /obj/random/loot.
Actually adding the notes to spawn is up to loredevs. If there are no notes to choose from, /obj/random/document will leave a blank sheet.
The notes can have HTML in them, meaning custom CSS and images. We're giving the loredevs a good bit of responsibility here.
This PR moves the tracking of the antagonists from the char spawn to the assignment and removal of the antag status.
It should properly account for all antags that are added/removed via the add_antagonist / remove_antagonist verbs
Fixes#3410
Ranged hostile mob stop if they are in range of fire, instead of keep going to point blank range. They also try to get to person within 6 tiles, not point blank.
Hostile mobs also check if their target is in the view or not.
Fixes#4468Fixes#2867Fixes#2721Fixes#2678
Character input limit in Security/Medecal records was increased from 1024 to 3027 for all fields, to keep it consistent with character setup records. Fixes#5766
Fixes Energy net turret sprites. Updates spawned ionrifle turret to allow for two modes, adds lethal turret sprite for ionrifle.
* Adds the ability to announce a fax only if someone doesnt have their PDA linked,
* Added SQL migration of expansion of do injunctions
* Changes "warning" to "reprimand"
This UI is going to be more integrated with BYOND host objects. It's update principal is very different from nanoui's. It is based around state that is being synchronized with server and client (browser). Such synchronization has it's problems, like it can't handle rapid changes, what could cause client and server to become out of sync and client state to be discard.
Converts the news network into a subsystem
Loads news from a database at the start of the round
No longer ties the PDAs to the tcoms system to access the news (which was broken anyway)
Removes the trivial news event
Adds the already existing virology / xenobiology containment events to the rotation
Expands the cargo table to require the approval of items before they are displayed on the server, enabling the creation of a module in the web interface.
This PR implements a system for manipulating a client's color safely and also ports a prioritization system for sorting client color from /tg/. Currently this PR also implements client coloration in the form of color blindness, namely:
Monochromacy
Deuteranopia
Tritanopia
Protanopia
DTP are mild brain traumas, whereas monocrhomacy is a severe brain trauma.
Furthermore, this PR removes the Needs Glasses prompt in character creation, and replaces it with a disability selector, allowing people to more closely refine their special little snowflakes.
Current disabilities available:
Nervousness
Nearsightedness
Deuteranopia
Tritanopia
Protanopia
Deafness
Muteness
Implements #4434
The reason for the order can now be viewed in the cargo control application
Calculate the shuttle fee per order
It is now possible to pay for orders that have been approved by cargo before they are shipped to the station
A mainfest spawns in the crates
Schema Changes:
The supplier, path and amount columns have been retired and are no longer used
Instead the following columns will be used:
supplier - the short name of the supplier that will be used
price - the price for the items
items - the items and their variables
If you are storing the cargo items in the SQL DB, then you dont have to do anything.
They will be migrated automatically to the new format
If you are storing the cargo items in JSON Files then you have to rewrite the files to adhere to the new format.
A example file of the new format is included
Adds some features and fixes some shit:
Closing of tickets sent to Discord will now alert discord as well.
Adds a reminder period for tickets which starts after they're opened. It's intended to remind staff to close their tickets. Say, something like 10 minutes since opening sounds like a solid idea. If the staff who claimed it is offline, then all staff are reminded of it.
Adds the logging of all tickets to the database at the end of round. Sortable by staff closing, person opening, time opened, time closed, and round ID. This is primarily for Aboshehab.
