getting_started
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | getting_started [2018/06/23 00:30] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Getting Started with CobraMUSH ====== | ||
+ | FIXME This guide is nowhere near complete. | ||
+ | First you must retrieve a copy of [[About | CobraMUSH]] which is explained in [[About# | ||
+ | |||
+ | Depending on how you retrieved [[About | CobraMUSH]], | ||
+ | |||
+ | ==== Get CobraMUSH ==== | ||
+ | === Retrieve CobraMUSH from ftp server === | ||
+ | wget http:// | ||
+ | |||
+ | === Extract CobraMUSH from ftp server and switch to working directory === | ||
+ | tar -xzf cobramush-0.72p3.tar.gz | ||
+ | cd cobramush | ||
+ | |||
+ | ==== Configure and Compile CobraMUSH ==== | ||
+ | === Configure CobraMUSH for your server === | ||
+ | ./Configure -d | ||
+ | This will automatically detect the best options suitable for your server when supplying the -d option. | ||
+ | cd game/txt/ | ||
+ | ruby genchanges.rb | ||
+ | cd ../.. | ||
+ | That will succesfully generate you [[changes.txt]] file for use with the distribution. | ||
+ | |||
+ | === Run make update === | ||
+ | This script will go through several customizeable compile options specific to a certain behavior how you would like your particular [[About | CobraMUSH]] server to run. In many cases, the defaults work just fine and you can just press enter all the way through. | ||
+ | make update | ||
+ | |||
+ | === Run make install === | ||
+ | This step finishes the particular compile options you may wish to go through. | ||
+ | make install | ||
+ | .....wait..... | ||
+ | |||
+ | ==== Database Setup ==== | ||
+ | The actual precise database setup, as to what dbref is this, and what dbref is that doesn' | ||
+ | |||
+ | ^ Dbref ^ Description ^ | ||
+ | | #0 | The room every new player is created in , connects in, and their first home location is set to. | | ||
+ | | #1 | The ' | ||
+ | | #2 | The ' | ||
+ | | #3 | The ' | ||
+ | |||
+ | #0 is generally the value for the [[mush.cnf: | ||
+ | |||
+ | === Readying your Master Division For Use === | ||
+ | In order for people to be able to achieve a level normally in CobraMUSH, receives powers, powergroups etc.. Your Division' | ||
+ | setup properely. | ||
+ | @level #3=29 | ||
+ | @empower # | ||
+ | |||
+ | Do not follow these exacts steps for your other divisions, we're just doing this for the Master Division as everything should be possible from it. Instead assign particular powergroups to its child divisions, or assign a select set of powers you wish for objects in that division to have. And of course the level set as appropriate, | ||
+ | === Create the Powerless Object === | ||
+ | |||
+ | Along with these pre-generated objects in your database you will need to create one extra object strictly for security purposes in the CobraMUSH model. | ||
+ | @pcreate Powerless=SomeRandomPassword | ||
+ | Then open up your [[mush.cnf: | mush.cnf]] configuration file and search for the powerless configuration option and set it to whatever dbref is assosciated with that newly created player. | ||
+ | |||
+ | === Setup your first System Director === | ||
+ | This is pretty straight forward. | ||
+ | So Create Your guy | ||
+ | @pcreate DirectorGuy=tikibar | ||
+ | Assign him to the Master Division | ||
+ | @division *DirectorGuy=# | ||
+ | Assign him to the System Director level.. Do not use level 30 for this guy. | ||
+ | @level *DirectorGuy=29 | ||
+ | Then grant him the Director powergroup. | ||
+ | @powergroup *DirectorGuy=Director | ||
+ | Although the [[softcode: | ||
+ | @empower *DirectorGuy=[pgpowers(Director, | ||
+ | At this point. | ||
+ | @su DirectorGuy | ||
+ | |||
+ | |||
+ | |||
+ | ==== Porting PennMUSH Softcode to CobraMUSH ==== | ||
+ | Porting PennMUSH Softcode to CobraMUSH is easy. The other way around, not so however. | ||
+ | \\ | ||
+ | [[:About | CobraMUSH]] on the other hand does its security checks by powers, levels and what not. A common quick replacement of the hasflag(*, | ||
+ | == Director Level Check == | ||
+ | gte(level(< | ||
+ | Thats a common cheap was to check, as that is the standard level assigned to ' | ||
+ | == Director Powergroup Check == | ||
+ | haspowergroup(< | ||
+ | This would probably be a more precise way to check it accurately. | ||
+ | \\ | ||
+ | |||
+ | |||
+ | \\ | ||
+ | A way we usually replace royalty type checks in code of the type hasflag(*, | ||
+ | |||
+ | === Other Tips on Coding === | ||
+ | To really fine tune your code, you'll take advantage of the massive powers allowed to hold in CobraMUSH and assign a particular power for use with that system. | ||
+ | \\ | ||
+ | First such way we'll give an example is the simple check to make sure they have the power.. Sameway as in PennMUSH. | ||
+ | haspower(< | ||
+ | However CobraMUSH brings powers to a whole new level. | ||
+ | powover(< |
getting_started.txt · Last modified: 2018/06/23 00:30 by 127.0.0.1