(shareware, 567kb ~4.0 minutes)
Kingdoms 2.23:
Kingdoms is a multi user online game with InterBBS capability. It will run under all BBS systems that support the standard DORINFO1.DEF, DORINFOx.DEF or DOOR.SYS drop file formats, or for which these file can be generated.
Other games have purported to be InterBBS, but they merely offer the user the ability to play on one BBS and send forays to others which must return to their home BBS. This is really just an extension of a local BBS game and does not offer true Inter-BBS functionality. Kingdoms does. :-)
Under Kingdoms, players have a ‘Home’ BBS, which is the one they logon to most frequently. On that BBS, they own a Castle which can be fortified in a number of ways, they can attack other players either on the local BBS or on another, send messages between them, etc. As far as Inter-BBS goes it’s all good fun, there is nothing really new here.
What is new, and what makes Kingdoms truly unique is that players in Kingdoms can purchase castles on other BBS’s in their net. They can hire an ‘Agent’ to run the castle for them, fortify that castle, store gold in it, send attacks from it and much more, all by remote command from their Home BBS. If they have created a remote castle, they can also directly logon to the remote and they will be recognised as a ‘Visiting Lord’ (or Lady!), owner of the castle there and operate it directly.
The possibilities for strategic play, multiple alliances and subterfuge here are enormous. It is not the purpose of this document to discuss the game itself in depth, so if you would like to know more, please read the Player documentation.
I hope you and your users enjoy the game!
Section 3 - Kingdoms Files
The following files should be in your Kingdoms Archive and are required to operate Kingdoms on your BBS. If any are missing, the latest version and archive can be FREQ’d from the Web BBS at the addresses provided in the Support section of this documentation.
3.1 Executable Files
3.1.1. KINGDOM.EXE
This program is the one that is executed when shelling from a BBS or in local mode by using the /L command line parameter.
3.1.2. KM.EXE
This is the Kingdoms Manager. When you’ve unpacked your Kingdoms archive, this should be the first program you run. A full description of KM.EXE is provided in the accompanying document, KM.DOC.
3.1.3. KNETIN.EXE
KNetIn processes Kingdom inbound files from other Realms on your Kingdoms Net. These inbounds could be messages, gold or monster transfer, Castle fortifications or a number of other Kingdom transit data. It will search for files named KNET*.* and process them from your inbound files directory as defined in KM.EXE. Please note that you should NEVER edit this file. Information in it is check summed and very strange things can happen to your inbound processing if the file data does not correspond to the file and record checksums.
3.1.4. KNETOUT.EXE
KNetOut processes the file KTransit.Dat. KTransit is the file which holds outbound information and data, some generated by Kingdoms itself, most generated by InterBBS activities of the players on your BBS. Please note that you should NEVER edit this file. Information in it is check summed and very strange things can happen to your outbound Transit file data does not correspond to the file and record checksums.
3.1.5. KMNT.EXE
KMNT is the Kingdoms Maintenance program. It should be run once daily. I suggest you put it in your nightly maintenance. It updates the player records, brings dead players back to life, packs the news files to manageable lengths and does other assorted housekeeping. It is also the means by which you can regularly poll other Kingdom nodes for net statistic information. It will not, unless you specifically request it, run more than once per day. Further information about KMNT is provided in the Kingdoms Installation section.