Re: [BTMux-General] General Thoughts

[Kevin S. <ke...@th...>]

Daniel MacGregor wrote:

> Was looking at the btpartslist function that cad came up with and
> realized some issues that I want to solve.
>
> First off there is no way 'currently', atleast as far as I know of, to
> determine a commod from a part. Also
> there is some Ammo mixed in with the cargo table, ammo that is not
> automatically generated like
> Ammo_AC/5 but instead ammo like Ammo_SRM_Inferno or Ammo_LRM_Artemis.
>
> My idea right now is redo the whole item table system, into something
> like this
>
> Weapons
> Generated Ammo
> Special Ammo
> Bombs
> Commods
> Parts
>
> And along with that redefine the IsAmmo (to include both tables) a
> IsCommod, a IsPart and redefine IsCargo as both.
> Also redefine the *_INDEX values stored in mech.h, add some for the
> commods and special ammo.
>
> Now KM has voiced some concerns about this because the part #s would
> change for just about everything.
>
> I guess this is just me being obessive about having things more
> organized then they are right now. What are your guys thoughts on this?
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> BtOnline-Btech-General mailing list
> BtO...@li...
> https://lists.sourceforge.net/lists/listinfo/btonline-btech-general
>
>
IIRC there is in fact a btpartype(). There are quite a few bt*()'s I
added that deal with scode integration of the part systems.

I must strongly voice that you reallllly should read all the code for
the bt*()'s yourself and fidn out which are there and all the options
for each. Even more strongly I suggest working for a long time with the
code before you even touch the part/items/crits/partID/partnames/etc....
code because I did early on before understanding the far reaching
implications of it and caused early problems. There are many layers of
intertwining, the bt*()'s interface to read and work with those to the
scoder are the tip of the iceberg.

If anything, analyze the bt*()'s 'read only' style interface and work
with them somehow with mode options or new segregateed bt*()'s. READ
ONLY. If you go low level liek you're speaking and hit the low level
data storages and Is*() macro's your in for a huge surprise. And I mean
huge one.

Wait till ya look at brand code on top of it all, how it works with
partnames tables... part ID's... and other stuff. :D

I highly suggest leaving the code alone and only working from a
read-only and moded standpoint from bt*()'s integration, delve into
parts, ID's, naming, brands, etc... in /hcode and your looking at a
world of hurt, nto just eyesores but DB corruption, template problems,
display issues, and tons more. :(

Can't stress it more. Ask anyone who has worked with BTMUX for awhile,
the parts/names/brand/etc... code is one hell of a scary topic.

Null


-- 
"A government is a body of people. Usually, notably, ungoverned."
    - Shepherd Book, Firefly, episode "War Stories"