PocketBuddies!

[atomic1fire]

I'm okay with basic responses.

I still want emagged pocket buddy to be a jerk though. I'm the nerd who wrote "Ha ha, cripple" for the delimbed response, but that might be too ableist, but it fit with my idea of emagged pocket buddy being the worst companion ever.

---

Code notes: An overarching event messaging datum is probably a good idea for this (generic for global usage, with pocket buddy shit as a child datum). Pocketbuddy datum would ideally read from a dict file (list? file2list() parsed on world new?) for easy message tweaking in one place. Actual event firing would probably have to be a mix of specific procs (e.g. gib() on owner) and controller loops (e.g. checking for crit on owner), as such a separate loop handler might be an idea. The pocket buddy obj itself would also need to have a shit load of unique tracking vars to keep state correctly.

Basically I see this as non-trivial, but do-able.

Edit: Note that this isn't me volunteering to actually do any of this.

Getting a list out of a dictionary file actually sounds pretty easy.

var/list/PocketBuddy = dd_file2list("strings/PocketBuddy.txt")

Basically an exact copy of every other dialog text.

I imagine other stuff like emagged could just be it's own distinct list and text file.

Of course I don't know if copy and pasting the NT code is a good way of handling dialogue.

https://github.com/goonstation/goonstati.../nt.dm#L10

Now that I think about it, using line number to get a specific location might break things if somebody removes a line later.