DCC Buff/medical knowledge needed

[HumiliatedGoblin]

About the pull request

This PR adds in a medical hour requirement for dropship crew chiefs, as they have medical training and should are required to be knowledgeable on medical.
It also adds in the ability for dropship crew to fix their doors with a multitool. Instead of the usual five seconds for engineering trained personnel, dropship crew take eight seconds.
Finally, a tip is added,

"As a Queen, you can unbolt dropship doors open by clicking on them, even if they are unlocked. Pilots, Dropship crew chiefs, Engineers and Synths can repair these doors with a multitool."

And two others are modified.

Explain why it's good for the game

Since Dropship Crew Chiefs have surgery knowledge, they must have a buffer to make sure that people who play Dropship Crew Chief are knowledgeable on medicine. This is the same for medics and doctors.

Next, it seems kinda stupid that Dropship crew aren't able to fix the own doors to their own dropship, and adds to the stigma that transport pilots and DCC's are un-fun to play, ignored and useless. By making it so they can actually repair their own dropships, they can bring a little more usefulness to rounds.

Finally, a tip is added to accommodate this PR, as I'm pretty sure no one even knew you CAN repair queen destroyed doors. I'd like to add a description to broken doors, but I'm not sure if that's possible with doorcode.

Testing Photographs and Procedure

Screenshots & Videos

i tested it and it worked but my medal didnt work so uh take my word for it

Changelog

🆑
add: Adds 1 medical hour for DCC
add: Adds and modifies some tips of the rounds.
balance: Dropship crew chiefs and pilots can now repair dropship doors
/:cl:

[ihatethisengine]

Your intends are wrong and code is working ONLY if you don't have engineering skill

Suggested change

	if(!skillcheck(user, SKILL_PILOT, SKILL_PILOT_TRAINED))
	to_chat(user, SPAN_WARNING("You don't seem to understand how to restore a remote connection to [src]."))
	return
	if(user.action_busy)
	return
	else
	to_chat(user, SPAN_WARNING("You begin to restore the remote connection to [src]."))
	if(!do_after(user, 8 SECONDS, INTERRUPT_ALL, BUSY_ICON_BUILD))
	to_chat(user, SPAN_WARNING("You fail to restore a remote connection to [src]."))
	return
	unlock(TRUE)
	close(FALSE)
	control.status = SHUTTLE_DOOR_UNLOCKED
	to_chat(user, SPAN_WARNING("You successfully restored the remote connection to [src]."))
	return
	if(!skillcheck(user, SKILL_ENGINEER, SKILL_ENGINEER_ENGI) && !skillcheck(user, SKILL_PILOT, SKILL_PILOT_TRAINED))
	to_chat(user, SPAN_WARNING("You don't seem to understand how to restore a remote connection to [src]."))
	return
	if(user.action_busy)
	return
	else
	to_chat(user, SPAN_WARNING("You begin to restore the remote connection to [src]."))
	if(!do_after(user, (skillcheck(user, SKILL_ENGINEER, SKILL_ENGINEER_ENGI) ? 5 SECONDS : 8 SECONDS), INTERRUPT_ALL, BUSY_ICON_BUILD))
	to_chat(user, SPAN_WARNING("You fail to restore a remote connection to [src]."))
	return
	unlock(TRUE)
	close(FALSE)
	control.status = SHUTTLE_DOOR_UNLOCKED
	to_chat(user, SPAN_WARNING("You successfully restored the remote connection to [src]."))
	return

[ihatethisengine]

oh wait you just duplicated the code? Hold on

[HumiliatedGoblin]

going to rework it on another repo since i accidentally did it all on master instead of a branch. i didn't see another way to do the skill checks since you cant have more then 2 skills in a skill check (according to checks anyways)