<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
 <channel>
  <atom:link href="https://smaugmuds.afkmods.com/index.php?a=rssfeed&amp;t=4768" rel="self" type="application/rss+xml" />
  <title>SmaugMuds - Topic: Replacing levels/trust</title>
  <link>https://smaugmuds.afkmods.com/index.php?a=rssfeed&amp;t=4768</link>
  <description>The largest Smaug community resource site. - Design thoughts</description>
  <language>en</language>
  <generator>SmaugMuds</generator>
  <ttl>60</ttl>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23398#p23398</link>
   <description>There&#039;s no real issue with using bits... I only suggested it because so many OTHER systems in Dikurivative codebases already use it.  You could just as easily make each &amp;quot;bit&amp;quot; a boolean variable in the structures and test against it.  It takes up more RAM, but big whoop... I dunno about your hardware, but my cheapo server has 16G of memory. </description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23398#p23398</guid>
   <pubDate>Tue, 26 Nov 2013 14:28:58 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Quixadhal)</author>
  </item>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23397#p23397</link>
   <description>Heh. Ok. I get what you&#039;re saying. I was trying to avoid doing bitwise manipulation but you do make a strong argument. Meh, maybe I&#039;ll go with a std::bitset. Or even possibly a boost::dynamic_bitset... Could let me, possibly though I&#039;m rather leery of doing so, add and remove the stuff at runtime. Probably not though. Removal would have so many potential issues.</description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23397#p23397</guid>
   <pubDate>Tue, 26 Nov 2013 07:25:57 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Andril)</author>
  </item>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23396#p23396</link>
   <description>I think trying to shoehorn every command into one (and only one) &amp;quot;group&amp;quot; is a mistake.  That&#039;s my feedback. Basic design says every thing has a set of things it IS, and a set of properties it HAS.  A given verb IS a command, or a channel, or a social.  A given channel HAS the properties of being an &amp;quot;IC&amp;quot; or &amp;quot;OOC&amp;quot; channel, and of being restricted to immortals or NOT restricted.  A given command HAS the properties of being a &amp;quot;game&amp;quot; command, or a &amp;quot;info&amp;quot; command.  You see what I&#039;m getting at? T</description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23396#p23396</guid>
   <pubDate>Tue, 26 Nov 2013 07:11:07 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Quixadhal)</author>
  </item>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23395#p23395</link>
   <description>That was the basic idea actually, though I was thinking each command would be part of only one set and players would have a list of what groups they&#039;re members of. That way the ability to use a particular group of commands could be enabled or disabled on a player by player basis. As an example, the basic movement commands could be part of &amp;quot;player_cmds_general&amp;quot; or even a movement specific group, and every player by default would have permission to use the commands in the group but an individua</description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23395#p23395</guid>
   <pubDate>Tue, 26 Nov 2013 03:19:02 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Andril)</author>
  </item>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23394#p23394</link>
   <description>I actually think you&#039;d be better off defining a proper security system for all commands, based on the conditions you want to use as restrictions... rather than trying to divvy them up into multiple lists. Let&#039;s say you define a command structure (pseudocode): [code] struct { char *name, int permission_bits, HELP *help_entry, FUNC *function_pointer, } command; [/code] So, the interesting part is the permission_bits part.  You could, of course, have elements for eac</description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23394#p23394</guid>
   <pubDate>Tue, 26 Nov 2013 01:53:53 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Quixadhal)</author>
  </item>
  <item>
   <title>Replacing levels/trust</title>
   <link>https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23393#p23393</link>
   <description>So I decided, after getting a private message from here, to stick my nose into muds again and seeing as how I am most familiar with SWR I thought I&#039;d stick to that. As of now I&#039;ve mostly concentrated on ripping mud.h apart and getting everything in there moved out to separate header files. While I&#039;m not quite done with that yet I have made considerable headway. In the process of doing so I remembered something I tried to do before and decided to do it again; replace player trust stuff with</description>
   <guid isPermaLink="true">https://smaugmuds.afkmods.com/topic/replacing-levelstrust-4768/&amp;p=23393#p23393</guid>
   <pubDate>Mon, 25 Nov 2013 18:31:27 CST</pubDate>
   <category>SWR FUSS</category>
   <author>nobody@example.com (Andril)</author>
  </item>
 </channel>
</rss>
