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...
> > Getters and setters for door position, eh? > > Door setters are quite tricky, since we would want the changes to > persist if you save the map state, like all the other map data. This > involves updating a bunch of map loading and saving stuff, and also > the live previewing system which should also be adjusted to become > aware of script door edits, so it's probably better if I handled it. > > > Yes, plotscr.hsd is where you define the name of the commands and > > allocate the internal command ID numbers for them. the end of the > > scriptmisc() sub in yetmore.bas is the best place to implement them. > > (there are some other places besides scriptmisc where plotscripting > > commands can be implemented, but that is where most commands are. All > > the other places are separated out only for silly historical reasons) > > > > Look at the gam.map.door global for reading the data. > > > > plotdict.xml is the place to document them > > > > I would be glad to help if you have any other questions. > > > > --- > > James > > _______________________________________________ > > 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 _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
