I'm thinking that the playsoundcont and playsoundrand script triggers are scanned for over the visible map area "plus a bit". Any new ones not seen before are added to a "playlist" (a type), and any on the playlist that are no longer in the scanned area get removed (although it may be neatest to remove them after a short period of them not being visible to avoid funny clipping when walking diagonally, etc). Once that's done, you work through the playlist and determine whether it's a continuous sound; if it is and isn't playing, make it play. If it's not, decide whether to play it again, either after a fixed period or after a random period between N and M seconds.
I suspect that your sound engine can handle a fair bit of that, but I haven't thought beyond the above at all (and even then, the above is largely off the top of my head!), or delved in the appropriate bits of code to know whether I'm talking crap or sense!
Hopefully once we have something like a real game structure in place we can garner some more interest and pimp it some more - more standalone activities can be taken on by people new to it, e.g. designing levels; designing puzzles / scenarios within levels; creating art / tiles; creating mini games; all those neat bits that we'd love to do but need to get the core sorted first!
I suspect that your sound engine can handle a fair bit of that, but I haven't thought beyond the above at all (and even then, the above is largely off the top of my head!), or delved in the appropriate bits of code to know whether I'm talking crap or sense!
However, this CP appears to have lost the interest of the community!
Hopefully once we have something like a real game structure in place we can garner some more interest and pimp it some more - more standalone activities can be taken on by people new to it, e.g. designing levels; designing puzzles / scenarios within levels; creating art / tiles; creating mini games; all those neat bits that we'd love to do but need to get the core sorted first!