Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] NTSL and Signal Technician #1945

Closed
wants to merge 5 commits into from

Conversation

Kitsunemitsu
Copy link
Collaborator

@Kitsunemitsu Kitsunemitsu commented May 21, 2024

About The Pull Request

Ports in the NTSL coding language and a role to accompany it; Signal Technician.
So this is a port, of a port of a port, let me give the full lineage.

First, credit goes to Yogstation, for the concept of NTSL.
Then, Skyrat in Skyrat-SS13/Skyrat-tg#5095
Then it was ported by yours truly to Bungalow/Quasar in Quasar-13/Quasar-13#133
And finally, Here again by me.

Signal Technician is a role that does 2 main things:
Maintain Telecommunications
Write code in their greasy tcomms den.

TODO:

Why It's Good For The Game

First, this will encourage people to actually know how to fix Tcomms. I have only ever met two people in my over 1000 hrs of SS13 that could fix tcomms.
Tcomms goes down multiple times each shift; and signal technician will hopefully know how to fix it.

Second, NTSL is simply a cool system.
Designing and testing new code on a live "server" (the Tcomms) is interesting and cool.

Changelog

🆑
add: Added NTSL
add: Added Signal Technician
/:cl:

@Kitsunemitsu
Copy link
Collaborator Author

This PR may or may not be fixed.
Both me and @gboster are working on it and it may also just not come to be,

Copy link
Collaborator

@dwasint dwasint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some small things I noticed

@@ -51,6 +51,7 @@
#define LOG_CLONING (1 << 22)
#define LOG_MECHCOMP (1 << 23)
#define LOG_BLACKMARKET (1 << 24)
#define LOG_NTSL (1 << 20)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we already have a 1<<20 needs to be 1<<25

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure I changed this; will fix.

@@ -0,0 +1,3 @@
/proc/log_ntsl(text)
if (CONFIG_GET(flag/log_ntsl))
WRITE_LOG(GLOB.world_ntsl_log, "NTSL: [text]")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should use the new logging system with Logger.Log

var/mob/editingcode
var/mob/lasteditor
var/list/viewingcode = list()
var/obj/machinery/telecomms/server/SelectedServer
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this doesn't appear to be unset in destroy which may lead to hard deletes


//NTSL-related procs
/obj/machinery/telecomms/server/Initialize()
Compiler = new()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these don't appear to be cleared aswell

/*
Class: node
*/
/node
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should just make all these subtypes of datum.

Copy link
Collaborator Author

@Kitsunemitsu Kitsunemitsu May 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried this, it no longer compiled, and everything broke

Revert "Adds datum part 1"

This reverts commit 2d0803d50dd068597d6ecad695234559520888a2.

datumize

Revert "Adds datum part 1"

This reverts commit 76ebdf37543012697dd0ad02d982deb79faa35a4.
@Kitsunemitsu
Copy link
Collaborator Author

Okay, I'm going to need help fixing linters on this.
I've never come across the linter errors of relative typepaths.

@Kitsunemitsu
Copy link
Collaborator Author

Okay so
This PR gives me a damn headache. I've been trying to fix it for like 3 days straight.
It works but every time I touch it it breaks in a new and unique way that I have a hard time fixing.

Gonna put this on the backburner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants