On Fri, Sep 30, 2011 at 11:39:25AM -0700, Adam Perry wrote: > Semi-relatedly, I'm also planning to add a command to expose elemental > resistances for enemies. I'm trying to use > http://hamsterrepublic.com/ohrrpgce/nightly/ohrrpgce-source-nightly.zip, > though, and it doesn't actually have yesterday's changes. (I'd use SVN > directly, but I'm running into proxy issues.)
Maybe using git would bypass the proxy problems? I guess I see no problem with a command to read elemental resitances. As long as it is designed to do exactly that, it will be easy enough to update it when we change the enemy data format. I suggest not adding a command to set elemental resistances. That sounds problematic. > More relatedly, are there plans to change the inner workings of read > enemy data? This doesn't matter too much for a potential "enemy > elemental resist as int" implementation, which can be changed if the > other is, but it might affect my plans for the script I'm working on. Yes, I do want to change read enemy data. tmc's suggestion from last night/this morning was to restrict read enemy data to ONLY work with those 11 constants that are documented, and to remove its ability to read any other arbitrary enemy data. However, I understand why you want to be able to read other data, so if you will document and add constants for the enemy data elements that you know you will need, I will keep backcompat support for those ones too. The idea is that when we change the enemy format to reload, it would be nice if we only have to support a backcompat interface for just a few elements of enemy data, rather than supporting a backcompat interface for the entire 366 ints in the DT1 lump. --- James Paige > On Fri, Sep 30, 2011 at 9:23 AM, Adam Perry <[email protected]> wrote: > > On Fri, Sep 30, 2011 at 8:53 AM, James Paige <[email protected]> > > wrote: > >> On Thu, Sep 29, 2011 at 08:13:10PM -0700, Adam Perry wrote: > >>> On Thu, Sep 29, 2011 at 7:56 PM, Ralph Versteegen <[email protected]> > >>> wrote: > >>> > > >>> > On 30 September 2011 08:34, James Paige <[email protected]> > >>> > wrote: > >>> > > On Thu, Sep 29, 2011 at 11:55:26AM -0700, Adam Perry wrote: > >>> > >> On Thu, Sep 29, 2011 at 11:26 AM, Adam Perry <[email protected]> > >>> > >> wrote: > >>> > >> > I'd like to add in a few more plotscripting commands, but I'm not > >>> > >> > sure > >>> > >> > what files need to be changed. The obvious one is plotscr.hsd, and > >>> > >> > I'm > >>> > >> > sure I can figure out what to do there, but what other files are > >>> > >> > involved? > >>> > >> > > >>> > >> > I'm not looking to do anything complicated; just getters/setters > >>> > >> > for > >>> > >> > things like door position and enemy attacks. > >>> > >> > > >>> > >> > >>> > >> Actually, some research shows that enemy attacks are already exposed > >>> > >> (albeit via the arcane "read enemy data" command). So that's one > >>> > >> down. > >>> > > > >>> > > Yes, the "read enemy data" commands are unfortunately arcane, and will > >>> > > be a backcompat pain in the future. > >>> > > >>> > I had been thinking recently: let's not support read/writeenemydata > >>> > for anything other than the provided constants. If you haven't used > >>> > them, and I haven't used them, and Mogri hasn't used them, then we can > >>> > be nearly sure that noone has. > >>> > > >>> But I just wrote a script using them extensively... > >> > >> Did you use any data index numbers other than the 11 documented in > >> http://hamsterrepublic.com/ohrrpgce/docs/plotdict.xml#about-readenemydata > >> ? > > > > Here's the list of undocumented things I'm using so far: > > 3, attackdata:target class > > 4, attackdata:target setting > > 12, attackdata:chain > > 13, attackdata:chain rate > > I am also likely to use several more since I'm essentially pulling in > > attack data to use in a custom battle system. > > > > I'm okay rewriting this part if you have a somewhat immediate plan for > > exposing attack data. > > > _______________________________________________ > Ohrrpgce mailing list > [email protected] > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org > _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
