Menu
▾
▴
[Pcgen-trackers_Docs] [ pcgen-Documentation Bugs-1783016 ] [OS]Undocumented features for EQTYPE
|
From: SourceForge.net <no...@so...> - 2007-11-19 04:11:55
|
Documentation Bugs item #1783016, was opened at 2007-08-27 22:01 Message generated for change (Comment added) made by maredudd800 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=748234&aid=1783016&group_id=25576 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Clarification Group: For 5.14 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: LegacyKing (amaitland) >Assigned to: Maredudd (maredudd800) Summary: [OS]Undocumented features for EQTYPE Initial Comment: Looks like it's acting exactly as it always has. What you want is EQTYPE.MERGE.NONE which it should do what you want. EQTYPE will merge everything with the same name regardless of how or where it is equipped. Yes, it's not documented, but it's how it works. Chuck OS Chimp ---------------------------------------------------------------------- >Comment By: Maredudd (maredudd800) Date: 2007-11-18 23:12 Message: Logged In: YES user_id=1569765 Originator: NO Docs updated. svn #2426 Tracker to be closed. ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-10-17 00:08 Message: Logged In: YES user_id=1569765 Originator: NO Chuck, Can you take a look at what I've done in the OS docs for this tracker and provide feedback? ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-10-15 22:39 Message: Logged In: YES user_id=1569765 Originator: NO I've tweeked a few things and I believe this tracker is complete. I need an OS Chimp to review what I've done to verify its correct. As stated before I've combined the EQTYPE and the EQTYPE.MERGE entries. Once I get confirmation that things are correct, I'll remove the original entries and fix the nav list. svn #4289 & 4290 ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-10-15 22:37 Message: Logged In: YES user_id=1569765 Originator: NO I've tweeked a few things and I believe this tracker is complete. I need an OS Chimp to review what I've done to verify its correct. As stated before I've combined the EQTYPE and the EQTYPE.MERGE entries. Once I get confirmation that things are correct, I'll remove the original entries and fix the nav list. svn #4289 & 4290 ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-10-15 16:34 Message: Logged In: YES user_id=1569765 Originator: NO I've got a prliminary doc entry for this tracker. Can someone look at it and tell me if I've captured every thing? Or otherwise confused it even more? I added an entry combining the EQTYPE and EQTYPE.MERGE tags, though not exactly the way Tir suggested. I left the original entries in the docs. Once the new entry is up to snuff, I'll pull the other entires and then update the nav list. ---------------------------------------------------------------------- Comment By: Andrew McDougall (tir-gwaith) Date: 2007-10-09 18:21 Message: Logged In: YES user_id=208239 Originator: NO .MERGE. is an optional part of the EQTYPE token, which happens to change how the token is looked at (I personally would change x and y in the MERGE one, so that the actual TYPE referenced is always in the same location, but that's old tags for you). I think at least mentioning the other token would be good in each entry. The two entries should make it clear when to use MERGE and when to not (MERGE is backwards - you use it when you _don't_ want to Merge like items.) The two entries show some slightly different information, all of which is good, from my understanding. Some options don't make sense together, but that's the price of flexibility. :p Here's an idea: make it one entry, like this: EQTYPE.MERGE.a.x.b.z a is only used with .MERGE, and isn't even required (the .x in the MERGE entry) x is the equipment TYPE being referenced b is location number - not used when MERGE is used (MERGE and b are mutually exclusive and will cause errors) - more below. b also has the option of .NOTE, which will print out a user added note about an item. z is the .IS. extra stuff about adding TYPEs and such If my memory serves, MERGE is default, and can be turned off by MERGE.NONE, or by adding the <b> location. Does that make sense? ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-10-09 16:52 Message: Logged In: YES user_id=1569765 Originator: NO Ok, I understand this one better. I'll get to it shortly. Re: [BUG] |FOR,%weap,0,COUNT[EQTYPE.WEAPON]-1,1,1| --- In pc...@ya..., "Frank Kliewe" <fkliewe@...> wrote: > > On 8/28/07, David <Papa-DRB@...> wrote: > > > > It is either a bug, or I just do not understand what the > > COUNT[EQTYPE.WEAPON] is supposed to return. > > > > I have a home brew html output sheet that lists each weapon, attack, > > damage, threat, reach, range, and hand. > > > > Example: Ranger 1, strength 14, dexterity 17. > > > > Case 1: Long sword(p) > > Prints it with all the correct values > > > > Case 2: Long sword(p), short sword(oh) > > Prints both with all the correct values including handedness > > > > Case 3: Long sword(p), long sword(oh) > > Only prints ONE. And it chooses whichever one was equipped first, so > > if the off-hand one was equipped first the numbers are for that one. > > The numbers are correct. > > > > FYI, I did Case 3 with 2 masterwork longswords, or 2 +1 longswords, > > and it exhibited the same behavior, ie. only printed one when the two > > equipped weapons were identical. > > > > Is this how the token is supposed to work or is it a bug? > > > > -- david > > Papa-DRB > > > > Looks like a bug to me. To make sure that it's not some other problem > in your sheet, could you please test if you see both swords when using > one of the Fantasy statblock sheets? They use COUNT[EQTYPE.WEAPON] as > well. > Looks like it's acting exactly as it always has. What you want is EQTYPE.MERGE.NONE which it should do what you want. EQTYPE will merge everything with the same name regardless of how or where it is equipped. Yes, it's not documented, but it's how it works. Chuck OS Chimp ---------------------------------------------------------------------- Comment By: Maredudd (maredudd800) Date: 2007-09-28 08:03 Message: Logged In: YES user_id=1569765 Originator: NO It isn't clear from the detail above what needs to be done here. Chuck, can you help me understand? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=748234&aid=1783016&group_id=25576 |