Re: [BTMux-General] Re: What is the biggest obstacle/confusion?

[Wayne S. <way...@ne...>]

Greg Taylor wrote:

> Yes, there actually is now an almost complete list of functions in the 
> softcode section of the wiki. I have not started on the BT functions yet, but 
> those will also be documented in due time.

I have. Started on the bt functions I mean. I figured in that I was 
crawling through the hardcode to figure things out I may as well stick 
my notes in a place that is public. Thus far I've only entered a few - 
btfunctions that I'm 99% sure I understand and so can document properly.

Hopefully more to follow as I improve my understanding.

>>A really amusing one is the fact that the Head Wizard character comes
>>with 30/50 bruise 'out of the box'. I haven't devoted any serious time
>>to 'healing' that character - but off the bat I have no idea where that
>>particular bit of data is stored.
>>
> 
> That's an oversight on my part. I'll fix this in the next release. But to do 
> it yourself:
> 

What a shame - I thought it was a real hoot. <g>


>>Or the intricacies of xcode. How about this one: go into an RB (that's
>>the only bay I've set up at the moment) and try to change the value of
>>mapwidth for it - it seems that @setxcode mapwidth <num> should do the
>>job ... but when I do it I get:
>>
>>Error: No matching xcode value for this type of object found.
>>
>>That's something else I haven't looked into yet. But to someone who's
>>trying to figure things out - that's kinda confusing.
>>
> 
> Actually, you'll want to make a map and put the file in your /maps directory, 
> then:
> 
> loadmap <filename>
> 
> I believe this is case sensitive. If you wanted a larger blank map, make a 
> larger blank map via Thump/Musemap and use that rather than using @setxcode 
> or @setmap.

Ah - but when you create a bay the mapname is default.map (if memory 
serves). Having noted hangar.map in the /maps directory it's almost 
logical to change it via @setxcode. Unless you already know better, I 
assume.


> Documentation is the single biggest obstacle in our development path at 
> present. Even more so since I'm pretty much the only one writing it. 

I sent you a mail a few days back - asking about the documentation 
project. Did you get it?

> It's an extremely easy process for the most part. Just create an account and 
> hit the 'Edit' button for various pages to see how to do things. Read up on 
> the MediaWiki editing documentation and dive right in. There's even a channel 
> on the Frontiers for Documentation cleverly named 'Documentation'.


Speaking off which - I notice that the wiki seems to contain some 
'downgraded' functions and not the newer replacements.

For example - btgetrefxcodevalue, while still present, seems to have 
been superseded by btgetxcodevalue_ref - however the former IS in the 
wiki and the latter is not. How do you want to handle that?

And it's just occurred to me that if we're gonna spend any more messages 
on the topic of doco's the rest of the list probably isn't terribly 
interested ... perhaps we should continue this directly?


Wayne