[Project] Script-supported charts&values involving balance-related variables

Laosh'RaLaosh'Ra Join Date: 2011-12-09 Member: 137232Members
edited April 2012 in Squad Five
<div class="IPBDescription">as community service or for further use</div>well i don't know anything about basecamp yet, so i'm not sure wether it makes sense to post this here or not...

this is an already existing (but ongoing) project, details are found in the thread: <a href="http://www.unknownworlds.com/ns2/forums/index.php?showtopic=117569" target="_blank">http://www.unknownworlds.com/ns2/forums/in...howtopic=117569</a>

to sum it up:
i've been working on a script to extract all the variables from the balance lua files, organising and processing it, ultimately displaying/creating useful charts which can easily be updated with every new patch (many things are dynamic, including the amount of variables).
example:
there is a chart which tells you how many attacks (or seconds) you need to kill X using Y. this chart is dynamically created from health, armor, damage, damagetype, firedaly, upgrades, etc. as listed directly in the code of the game.

benefits:
overall, it can act as a quick way to provide overview for people who want to look up the mechanics under specific aspects (e.g. one person mentioned he is using the data to keep the wiki up-to-date). if multiple people have this script, the chances of getting an update almost instantly after a patch-release are rather high.

i've direct access to the variables in matlab, calling them by their names: manually adding exceptions or fullfilling specific requests is rather easy.

there is also a framework for different types of outputs, e.g. i can provide a CSV format which could be used for other web-based scripts etc.
i myself have little experience in this field, but maybe there are other people who would like to join this project in order to implement something fancy.

issues:
the script is currently written in matlab (which is more powerful than you might think!) and not very object oriented or very well documented. i've put in some effort to keep most parts as general and dynamic as possible, but it might be better to organise everything in a class hierarchy (or database) in the long run: this really depends on the ways the data would be used.

updates can be a bit delayed as i live in a different time zone, but it only takes ~1 minute to get everything up-to-date once i downloaded the patch (unless there are huge changes in the mechanics, but the last two patches worked just fine for example). to adress this, i could give the script to other people running matlab (or rewrite it in a different language, see previous point).

i reserved the first 4 post in the thread, but i am still at the edge of how much content can be displayed (codeboxes help a lot though).

<i>edit: sorry i forgot the [Project] in the title, please delete the other thread</i>
Sign In or Register to comment.