qbfreak / solarwindsmare Goto Github PK

Some parents have odd names left over from previous designs of space to include larger units than sectors. All references to Sector x Parent should probably be dropped in favor of Space x Parent.

Existing Parent names:

• Generic Function Parent(#4bh)
• Cron Parent(#5Vbh)
• TinyFugue Textencode Decoder Parent(#6bh)
• Communication Coordination Server Parent(#12Vbh)
• Communication Coordination Client Parent(#13Vbh)
• System Function Parent(#29h)
• Sector Exit Parent(#45h)
• Station Zone Parent(#46h)
• Airlock Parent(#47h)
• Docking Collar Parent(#48h)
• Ship Parent(#50h)
• Ship Zone Parent(#59h)
• Motd Parent(#66)
• Who Parent(#67)
• Player Character Parent(#68h)
• PlusCom Parent(#71)
• Apartment Parent(#92h)
• Apartment Bot Parent(#93h)
• Apartment Zone Parent(#96h)
• Station Parent(#99h)
• Station Control Console Parent(#102h)
• Apartment Exit Parent(#104)
• Sector Zone Parent(#110h)
• Sector Parent(#114h)
• ID List Parent(#115h)
• ID List Manager Parent(#116h)
• Age Limited List Parent(#118h)
• ComCname Parent(#119h)
• Text Formatting Parent(#120)
• Player Command Parent(#121h)
• Space Object Parent(#124h)
• Planet Parent(#125h)
• Star Parent(#126)
• Moon Parent(#143)
• Asteroid Field Parent(#146)
• Command Help Parent(#148h)
• Enterable Space Object Parent(#149h)
• Todo List Parent V2(#156Vbh)
• Com Shortcut Parent(#160)
• Planet Exit Parent(#161h)
• Planet Zone Parent(#165h)
• 2D Coordinate System Parent(#170h)
• Planet Function Parent(#175h)
• Planet Room Parent(#180h)
• Comtitle Manager Parent(#188h)
• 2D Exit Parent(#201h)
• ID List Manager Parent(#216)

Various UZO commands need to be moved to appropriate (new) parents, and @addparented back to the UZO. Any parents not specific to SolarWindsMARE need to be moved out of the repo.

Test the 2D Exit Parent (2dexit.mare), which at the same time will test the 2D Coordinate System Parent (2dcoordp.mare)

Airlock Parent - airlock.mare

• The Airlock Parent links to the center of a sector, not to the current location of a station.
• The Airlock Parent is poorly named, and should probably be something like Station Airlock Parent

In order to attract Builders running their clients on Windows, it is ideal to provide them with a way to use the current code files in their existing form. A script needs to be written to perform the same function as utils/mupdate.tf does for TinyFugue:

• When #mupdate on is encountered, begin stripping line endings and white space and place the growing string into a buffer
• Between the #mupdate tags, when encountering a line with only a single period, send the buffer
• When #mupdate off is encountered, return to sending lines one at a time

The Station Airlock Parent @vlink links to the station's location, but at sector 0.0.0, NOT the sector of the station. This needs to be fixed. While correcting this, ::1 Station needs to have it's station object (#100) moved to space and have the place holder located at 0.0.0 removed.

The Apartment Bot (See apbot.mare) is not complete. It needs to be able to do the following:

• Path to a player's apartment entrance
• The fix lock command needs to update the @lockid in the apartment to point to the #dbref of the exit entering the apartment
• Issue and create new apartments for players that do not have one yet

While doing all of this, the Apartment Bot should never leave the Apartment zone. @llock the zone against the bot?

Right now the Ship Parent doesn't have an @Succverb set. When it moves between rooms the game uses the default, which is walk. A little odd to see a ship walking in space.

The 3D and 2D planar exit parents use identical methods for determining an exit's direction when calculating @vlink, and the same for @vlock. In both cases, the method differs between @vlink (alias) and @vlock (name). This should be corrected such that both @vlink and @vlock use as similar methods as possible. Whether that uses the alias or the name has not been determined at this point.

2D Exit Parent 2dexit.mare
Sector Exit Parent sectorexit.mare (Needs to be renamed per #1 )

The Sector Parent uses createtime(me) to seed the color and cname. This means that short of overwriting the @color and @cname attributes of a new Space room, it will not be possible to duplicate a Space room's color with the same seed.

The file names are a bit random and ought to be standardized. See the file names for the Planet series of parents for an example. This is contingent on getting the Parent names sorted out first. See #1.

Filenames:

• 2dcoordp.mare
• 2dexit.mare
• 3dcoordp.mare
• apartment.mare
• apbot.mare
• apexit.mare
• apzone.mare
• asteroidfp.mare
• claimcomp.mare
• claimmkr.mare
• claimzone.mare
• cube.mare
• docking.mare
• drd.mare
• espaceobj.mare
• limbo.mare
• maxims.mare
• moonp.mare
• ncp.mare
• pexit.mare
• pfunc.mare
• planetnuke.mare
• planetp.mare
• proom.mare
• pzone.mare
• qbfreak.mare
• sector.mare
• sectorexit.mare
• sectorzone.mare
• ship.mare
• shipzone.mare
• spaceobj.mare
• staairlockp.mare
• starp.mare
• station.mare
• stationcon.mare
• stationzone.mare
• terrainp.mare
• uzo.mare
• uzo_admin.mare
• uzo_administrative.mare
• viewscreen.mare

This is a two-part issue:

• The sectorcolor() functions need to be renamed to something like spacecolor() as related to #1. Check and see what the function was named for planet rooms and use it as a template.
• In addition the sectorcolor() function and it's successor should not be located on the System Function Parent, but on a parent for the Space room. If a Space Room Parent does not exist, create it.

Please note this assumes that #1 renames all of the sector related parents to focus on Space, as it is the name of the room that holds the sectors. Please see what decision has been reached on #1 before renaming sectorcolor() or creating a Space Parent.