{"id":565,"date":"2010-09-07T18:28:47","date_gmt":"2010-09-07T22:28:47","guid":{"rendered":"https:\/\/www.caskeys.com\/dc\/?p=565"},"modified":"2020-07-10T11:40:21","modified_gmt":"2020-07-10T15:40:21","slug":"565","status":"publish","type":"post","link":"https:\/\/www.caskeys.com\/dc\/565\/","title":{"rendered":"Runtime Grapple Editor"},"content":{"rendered":"

Please note: The scripts in this post are depreciated and no longer supported. My grapple functionality is now handled by the DC Elmers<\/a> library.<\/span><\/strong><\/p>\n

\"\"OpenBOR is an extraordinarily powerful game engine, but one severe design flaw is the lack of any reasonable grappling support. Holding strikes and a horribly animated back toss are all it can really do out of the box.<\/p>\n

Fortunately script support alleviates this problem, as one can simply script a throwing system for themselves. Quite some time ago I did just that and am pretty proud of it. It supports everything from simple hurling all the way up to multi part chain slams ala Tekken. It even supports one character grappling several opponents at once and\/or tag team throws. The best part is by use of careful standardization, the defender does not need any additions beyond a standard set of animations given at creation time. Thus adding grappling moves to a character requires only modifications to that one character as opposed to every other entity in the game.<\/p>\n

Even with those conveniences, adding a throw was still prohibitively time consuming. It required countless starting and restarting of the engine while tweaking the bind settings pixel by pixel. Creating a single simple throw could take a day or more. So even though I dreaded dealing with menu codes again, I decided to create an on the fly throw editing system.<\/p>\n

\"Throw<\/p>\n

The premise is simple: Edit the grappling poses at run time, record the resulting parameters, and copy\/paste them into the model text. The code is such a mess I’m almost embarrassed to post it here, but ahh well. It desperately needs some cleanup, but from a functionality and stability standpoint works just as I had hoped:<\/p>\n