Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 13,213
|
I apologize, but I'm hoping to have a release for Shadowrun finished by the end of this week, but that's going to take a lot of my time this week, so I won't get a chance to study these issues in detail until next week, but the error message in your screenshot is something to do with the statblock. sbtraits is a procedure that a lot of different things in the statblock call, so just looking at line 9 may not be useful - if I remember correctly, that procedure uses a foreach to search a list of things. So what it looks like is happening here is that the procedure is finding things that it hasn't been set up to handle yet.
|
#31 |
Member
Join Date: Aug 2013
Location: CA
Posts: 42
|
It's not causing a compiling error, so I will just click through the popup warning for the time being.
|
#32 |
Member
Join Date: Aug 2013
Location: CA
Posts: 42
|
Dead in the water. I said I would push on but then this happened...
Character Creation Logic (Savage) http://hlkitwiki.wolflair.com/index...._Logic_(Savage) Attribute Points Code:
<eval index="2" phase="Traits" priority="10000"> <before name="Calc resLeft"/> <after name="Bound trtUser"/><![CDATA[ ~since the base starting value for each attribute is two, we add only the extras perform #resspent[resAttrib,+,field[trtUser].value - 2,field[name].text] ]]></eval> Code:
<scriptmacro name="resspent" param1="resource" result="hero.child[#resource].field[resSpent].value"/> Code:
<scriptmacro name="resspent" param1="resource" param2="oper" param3="value" param4="text" result="hero.child[#resource].field[resSpent].modify[#oper,#value,#text]"/> Last edited by Goreshade; September 7th, 2016 at 02:32 AM. |
#33 |
Member
Join Date: Aug 2013
Location: CA
Posts: 42
|
Decided to get some sleep and come back at the macro problem today today. What to do when a macro doesn't work? When in doubt, tear the macro out...
Code:
hero.child[resAttrib].field[resSpent].value += (field[trtUser].value - 2) |
#34 |
Junior Member
Join Date: Dec 2016
Location: Houston
Posts: 8
|
I really wish I had read this thread before purchasing. Sadly, neither this thread, nor the wiki is current. The offline PDF links do mention that the PDFs may be out of date with the wiki, but there is a reasoned, entry-level presumption that the wiki would not also be profoundly (half a decade) stale.
Had I done my due-diligence and not assumed maturity in the documentation, it is highly unlikely that I would have purchased -- and, having experienced this buyer's remorse, I feel obligated to caution others and coach the leadership team. The ability to customize is one of (if not the) flagship cornerstone(s) of this product. The fact that there is a significant barrier to entry that is self-inflicted by Lone Wolf Development is disappointing. Documentation is as important as the product itself. The amount of focus upon and the investment in product documentation that is meaningful and actionable is a direct reflection of management commitment to providing a satisfying customer experience. Quote:
There is no forward looking initiative, burn-down, or deadline that should ever stand between development and documentation. While the "business case" for mature documentation is often obfuscated by myopic, short-term interests, the business case for responsible documenting exists and is compelling. A product is only as complete as is its documentation. A stupidly silly example that makes my point spectacularly, on the front page (http://hlkitwiki.wolflair.com/index.php5?title=Home): Quote:
Details matter! Either you want to best-in-class or you do not. Or to be crude, "defecate or perform egress from the evacuation station." Half-measures avail nothing. Make no further excuses. Apologize and make to do better. Or not; it's your brand. While I'm in for a penny, I can be thankful that the method of entry (store setup) only allows a single initial purchase. As it is, a couple 10'ers is largely well within my pain tolerance [EDIT] for a boondoggle. That said, despite my dissatisfaction with Hero Lab, I am enamored with Realm Works. The alleged synergy between HL/RW intimated potential time savings; therefore, I had hoped to leverage both tools to uplift my game. Unfortunately, to make use of Hero Lab requires an investment of time in reverse-engineering that steals time away from the actual creative process of story design and gaming. I don't disparage those for whom meta-gaming brings great joy. I simply would rather game than meta-game. There are suitable substitutes in the market for custom character and npc management that are more closely aligned to my requirements. I'm profoundly grateful that I discovered the tragic state of the dilapidated documentation before investing further.[/EDIT] Despite my assertive tone, I am not angry. I would not have taken the time to be explicit if I did not have some belief that you can do better. I simply don't know if you want to do better. Z Last edited by Zortek; January 12th, 2017 at 05:19 PM. Reason: Clarifying my associating Realm Works comment. |
||
#35 |
Senior Member
|
I'm confused what the authoring kit has to do with Realm Works?
Oh, and since this is your first post, welcome to the forums. When I was creating the ruleset for Castles & Crusades, these forums were priceless. Dave Castles & Crusades Ruleset for Hero Lab Hero Lab (5E D&D) -> Fantasy Grounds Character Converter |
#36 |
Junior Member
Join Date: Dec 2016
Location: Houston
Posts: 8
|
The non sequitur and your confusion not withstanding, I deeply appreciate such a lovely welcome.
|
#37 |
Member
Join Date: Aug 2013
Location: CA
Posts: 42
|
Glad my thread could be of assistance, I suppose.
I feel Hero Lab author kit at this point was a bit of a waste of time and money (way more time, than money). It takes so long to work thru the horribly out of date and broken tutorials while trying to imagine how to apply it to your own projects if and when you ever reach the finish line of the wiki. Reverse-engineering is quite apt in describing the experience, and while you can come to these forums for help most of the time your ignored or put on the back burner because some new module needs to be released. Eventually other things and projects must be attended to in your life and the lack of support for the authoring kit makes it easy to put aside for another year until you get the urge to try again. Then, of course, you come back to it and find that instructions are STILL older than Sanford and Sons scrap yard. Every time I look at that wiki I can hear the theme song. |
#38 |
Junior Member
Join Date: Dec 2016
Location: Houston
Posts: 8
|
Quote:
The time and effort needed to work with Hero Lab Authoring Kit is better served actually learning C# or Java and/or going bespoke. All the eye candy is worthless (if not an actual drain and distraction on game design) if it one can not efficiently achieve meaningful and actionable results that contribute in a meaningful and actionable way to game play. |
|
#39 |
Thread Tools | |
Display Modes | |
|
|