Nofew

Untitled

Dec 17th, 2015
397
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.61 KB | None | 0 0
  1. Mucker Levels:
  2. There are 8 permissions levels in ProtoMUCK. Level zero is a non-bitted
  3. player, and has no ability to use any code on the MUCK, be it MPI or MUF.
  4. A player set = M is a MEEPER, and may use MPI, but no MUF. Levels M1 to
  5. W4 have access to the MUF editor, and may program MUF code.
  6.  
  7. The MUCKER level permissions that a program runs at is its owner's
  8. level. If it is owned by a player who is M2, the MUF runs at a M2 level.
  9. Programs owned by W2's and higher are considered W-bitted MUFs, and will
  10. run at that permission level, regardless the bit set on the program itself.
  11.  
  12. The mucker levels available with the man command are: (ie, type man M1)
  13. M1 M2 M3 W1 W2 W3 W4 (Mucker 1-3 and Wizard 1-4)
  14. Note that the manual entries deal only with how a M/W bit affects MUF, not
  15. other in-server restrictions.
  16. MUCKER1 - Apprentice
  17.  
  18. Level one MUCKER's are apprentices, and although the M1 bit is
  19. considered a 'Learner's Bit', there is still a lot that can be done
  20. with them, so their distribution should still be done with some
  21. consideration. M1 programs always run as if they are SETUID. Any
  22. notifying prim, like NOTIFY and NOTIFY_EXCEPT will automatically
  23. prepend the M1 user's name to the beginning of the message, though
  24. this can be toggled as an @tune parameter. M1 programs have an
  25. absolute instruction level that is equal to the @tuned PREEMPT
  26. instruction limit, typically around 20k instructions.
  27. M1s may use any non-restricted prim (prims that have no minimum level),
  28. though other prims may have additional restrictions.
  29.  
  30. See: M2, MUCKER LEVELS
  31. MUCKER2-Journeyman
  32.  
  33. M2 programmers have access to a whole new level of prims, and are
  34. given a much higher instruction count limit, roughly 4 times the
  35. @tune PREEMPT limit, or around 80k instructions.
  36. It is recommended that only trusted players be given M2, and only
  37. if they are able to demonstrate some competence in MUF.
  38.  
  39. See: M2 PRIMS, M3
  40. MUCKER3-Master
  41.  
  42. M3s can use some of the connection related prims, and have fewer
  43. restrictions with other prims as well, such as moveto. Refer to the
  44. documentation on individual prims to see what M3's are able to do
  45. that an M1 or M2 cannot. Their instruction count limit is roughly
  46. twelve times the @tuned PREEMPT limit, typically around 320k.
  47. M3's do have quite a bit of flexability and power with their use of MUF.
  48. It is important to only give M3s to non-staff members who are highly
  49. trusted.
  50.  
  51. See: M3 PRIMS, W1
  52. WIZARD1-MAGE
  53.  
  54. W1 is given more power over information retrieving prims, such as
  55. conhost, and others. They also have way fewer restrictions with the prims,
  56. such as the building prims. They still cannot write to restricted props
  57. on objects they do not own, nor use setown to change ownership of objects
  58. to other players. W1s have no instruction count limit. W1s can also
  59. delete macro definitions, set their programs to run AUTOSTART,
  60. and set programs = S & H to run with caller privleges.
  61. It is recommended that W1 bits be given to coders of a MUCK's staff.
  62. They should not be generally given to non-staff members.
  63.  
  64. See: W1 PRIMS, W2
  65. WIZARD2-Wizard
  66.  
  67. W2 is technically the first 'wizbit' level, in terms of MUF. At
  68. this level, almost all prim restrictions are ignored, programs
  69. can change restricted props on objects they do not own except for
  70. @ props, use setown, and many other higher level prims. There are
  71. no limits on instruction counts, not even with programs running
  72. in PREEMPT mode.
  73. It is recommended that W2 be given to admin level coders, as the
  74. lack of restrictions on W2 programs make them very powerful.
  75.  
  76. See: W2 PRIMS, W3
  77. WIZARD3-ArchWizard
  78.  
  79. W3 level programs have almost no restrictions whatsoever. Only
  80. the file prims are unavailable to W3s. No instruction limits on
  81. any program, and the ability to read/write @ props, which are
  82. unavailable to W2s.
  83. It is recommended that W3s be given to only the MUCK's MUF wiz
  84. or wizzes, as the lack of any restrictions requires that players
  85. who have W3 permissions be highly trustworthy.
  86.  
  87. See: W3 PRIMS, W4
  88. WIZARD4-Boy
  89.  
  90. W4 is almost the same as W3 in terms of permissions, the only
  91. noteable difference being the access to the file prims that W3's
  92. do not have.
  93. Under most conditions, there is little need for any coder to have
  94. a W4, unless the file prims are specifically required.
  95.  
  96. See: W4 PRIMS
  97. There is no help for "w5"
  98. There is no help for "m1 prims"
  99. The following prims become available at the level of M2, though
  100. they still may have some uses reserved for higher permission levels:
  101.  
  102. addpennies ( d i -- )
  103. movepennies ( d1 d2 i -- )
  104. timestamps ( d -- i i2 i3 i4 )
  105. newroom (d1 s -- d2)
  106. newobject (d1 s -- d2)
  107. contime (i1 -- i2)
  108. conidle (i1 -- i2)
  109. nextprop (d s1 -- s2)
  110. propdir? (d s -- i)
  111. descridle ( i -- i )
  112. descrtime ( i -- i )
  113. findnext ( d1 d2 s1 s2 -- d3 )
  114.  
  115. See: M2, MUCKER LEVELS, invididual prim entries for more details
  116. The following prims become available at the level of M3, though
  117. they still may have some uses reserved for higher permission levels:
  118.  
  119. online ( -- d ... i )
  120. condbref (i -- d)
  121. connotify (i s -- )
  122. stats ( d -- total rooms exits things programs players garbage )
  123. recycle (d -- )
  124. condescr ( i -- i )
  125. descrcon ( i -- i )
  126. descriptors ( d -- ix...i1 i )
  127. queue ( i d s -- i )
  128. parseprop ( d s s i -- s )
  129. parsepropex ( d s1 dict i -- dict s )
  130. nextplayer ( d -- d' )
  131. descr_array ( d -- a )
  132. online_array ( -- a )
  133. descrflush ( i -- )
  134. descr_html? ( i -- i )
  135. descr_pueblo? ( i -- i )
  136. descr_welcome_user ( i -- )
  137. descr? ( i -- i )
  138. event_send ( i s ? -- )
  139. motd_notify ( d -- )
  140. nextprogram ( d -- d )
  141. nextexit ( d -- d )
  142. nextroom ( d -- d )
  143. nextthing ( d -- d )
  144. descrdbref ( i -- d )
  145. watchpid ( i -- )
  146. getobjinfo ( d -- dict )
  147. descrbufsize ( d -- i )
  148.  
  149. See: M3, MUCKER LEVELS, individual prim entries for more details
  150. The following prims become available at the level of W1, though
  151. they still may have some uses reserved for higher permission levels:
  152.  
  153. newexit (d1 s -- d2)
  154. conhost (i -- s)
  155. conipnum (i -- s)
  156. nextdescr (i1 -- i2)
  157. fork ( -- i)
  158. nextowned ( d -- d' )
  159. notify_descriptor ( i s -- )
  160. ansi_notify_descriptor ( i s -- )
  161. setpassword ( d s1 s2 -- )
  162. next_flag ( d s -- d )
  163. nextowned_flag ( d s -- d )
  164. nextplayer_flag ( d s -- d )
  165. nextthing_flag ( d s -- d )
  166. nextplayer_power ( d s -- d )
  167. nextentrance ( d d -- d )
  168. descrhost ( i -- s )
  169. descripnum ( i -- s )
  170. firstdescr ( d -- i )
  171. lastdescr ( d -- i )
  172. descr_flag? ( i s -- i )
  173. notify_descriptor_char ( i i -- )
  174. bandwidth ( -- i i i )
  175. get_macros_array ( -- dict )
  176.  
  177. See: W1, MUCKER LEVELS, individual prim entries for more details
  178.  
  179. The following prims become available at the level of W2, in
  180. addition, W2's are no longer restricted by having to own an
  181. object in order to make changes to it. There is little a W3
  182. can do with these prims that a W2 cannot do.
  183.  
  184. conboot (i -- )
  185. parsempi ( d s1 s2 i -- s3 )
  186. descr_setuser ( i1 d s -- i2 )
  187. program_getlines ( d i i -- arr )
  188. program_linecount ( d -- i )
  189. insert_macro ( s s -- i )
  190. kill_macro ( s -- i )
  191.  
  192. See: W2, MUCKER LEVELS, individual prim entries for more details
  193.  
  194. The following prims become available at the level of W3, in
  195. addition W3's are able to manipulate the @ props that W2 and
  196. below are unable to. There is almost nothing a W4 can do with
  197. these prims that a W3 cannot do.
  198.  
  199. conuser (i -- s)
  200. conport (i -- s)
  201. force (d s -- )
  202. setsysparm ( s1 s2 -- )
  203. checkpassword ( d s -- i )
  204. newplayer ( s1 s2 -- d )
  205. copyplayer ( d1 s1 s2 -- d2 )
  206. toadplayer ( d1 d2 -- )
  207. logstatus ( s -- )
  208. sockopen ( s1 i -- socket s2 )
  209. socksend ( socket s -- i )
  210. sockrecv ( socket -- s )
  211. sockclose ( socket -- i )
  212. nbsockopen ( s1 i -- socket s2 )
  213. get_sockinfo ( socket -- dict )
  214. sockcheck ( socket -- i )
  215. socket_setuser ( socket d s -- i )
  216. set_sockopt ( socket i -- i )
  217. socktodescr ( socket -- i )
  218. propqueue ( d1 s1 d2 s2 -- )
  219. envpropqueue ( d1 s1 d2 s2 -- )
  220. newpassword ( d s -- )
  221. descr_logout ( i -- )
  222. descruser ( i -- s )
  223. descrport ( i -- s )
  224. descrconport ( i -- i )
  225. getpids ( d -- arr )
  226. getpidinfo ( i -- dict )
  227. getdescrinfo ( i -- dict )
  228. descrboot ( i -- )
  229. descr_set ( i s -- )
  230. dump ( -- )
  231. delta ( -- )
  232. sqlclose ( sql -- )
  233. sqlping ( sql -- i )
  234. sqlquery ( sql s -- dict ... dictn n arr )
  235. sqlconnect ( s s s s i -- sql i )
  236. copyprops ( d s d s i -- i )
  237. sockshutdown ( socket i -- i )
  238.  
  239. See: W3, MUCKER LEVELS, individual prim entries for details
  240. Every prim in MUF can be used by W4, with every permissions check
  241. cleared. In addition, they have access to the file prims listed
  242. below:
  243.  
  244. fwrite ( s1 s2 i1 -- i2 )
  245. fappend ( s1 s2 -- i )
  246. fread ( s1 i -- s2 )
  247. freadn ( s1 i1 i2 -- s2 )
  248. freadto ( s1 i1 s2 -- i2 s3 )
  249. fpublish ( s -- i )
  250. fcr ( s -- i )
  251. bread ( s1 i1 -- i2 )
  252. bwrite ( i1 s i2 -- i3 )
  253. bappend ( i1 s -- i2 )
  254. fsinfo ( -- i1 .. i8 )
  255. curid ( -- i1 i2 )
  256. fstats ( s -- i1 ... i6 )
  257. fsize ( s -- i )
  258. frm ( s -- i )
  259. fren ( s1 s2 -- i )
  260. getdir ( s -- arr )
  261. mkdir ( s -- i )
  262. rmdir ( s -- i )
  263. newprogram ( s -- d )
  264. compile ( d i -- i )
  265. uncompile ( d -- )
  266. lsockopen ( i i -- lsocket s )
  267. sockaccept ( lsocket -- socket )
  268. armageddon ( s -- )
  269. shutdown ( s -- )
  270. restart ( s -- )
  271. program_insertlines ( d i1 arr -- i2 )
  272. program_deletelines ( d i1 i2 -- i3 )
  273.  
  274. See: W4, MUCKER LEVELS, individual prim entries for more details.
  275. There is no help for "w5 prims"
Advertisement
Add Comment
Please, Sign In to add comment