Reply to thread

Message: <blockquote data-quote="GhostBear" data-source="post: 5907650" data-attributes="member: 6667527">Basically. Not a lot of processing power should be needed for this, but a good amount of memory would be helpful. Table data could be cached so constant database lookups (or whatever back end storage you use) aren't required. Even then, modern DBs are really good about caching requests, so probably not worth worrying about too much. Software-wise, you can take a complex string (like a stat block), pass a string into preg_replace_callback() (if using PHP for the project) to replace the tokens, and you're done.One suggestion I would make, though. You might want to namespace table names by username [GhostBear:WeaponList]. That way you'll allow everyone to name their tables whatever they want without chances of conflicts.This project isn't all that complicated in terms of software complexity. With a decent spec even a novice developer should have a pretty easy time developing what you want.Do you plan on hosting the project on something like SourceForge or GitHub and releasing it under an open license?Edit: As far as preventing abuse / accidental infinite loops, you can specify a maximum depth for processing recursion. Just return an error string instead of the table result (and possibly the table path as well) so that someone knows what happened and why.</blockquote>