09-27-2016, 09:08 AM
(This post was last modified: 09-27-2016, 09:11 AM by Wire. Edited 1 time in total.)
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.
Basically I see this as non-trivial, but do-able.
Edit: Note that this isn't me volunteering to actually do any of this.