Difference between revisions of "User:Inutt/CodingIdeas"

Revision as of 22:55, 21 August 2019

Coding ideas

☐ ☑ ☒

• ☑ Make indentation consistent [Happening as I edit code]

- It just makes code easier to read, enables code folding, and lining up corresponding if/then statements makes the code vastly easier to parse! (Yes, I know two of those points are the same, but it's an important one)

• ☐ Add prop to players that have womb/other private rooms so they can be found without looping through all room objects - it would just make more sense and improve efficiency
• ☐ Write a parameter checking function - basically an improved checkargs to highlight more clearly when incorrect parameters are passed
  • Check number of supplied parameters is actually on the stack
  • Check type of arguments
  • Something like "str:foo int:bar dbref:baz any:qux" checkparams
    • Check stack depth
    • Split on ' ' and foreach in reverse order
    • Split on ':' into type,name
    • If top of stack matches type, add to dict of parameters by name
• ☐ Unify use and +use
• ☐ Merge/replace hasBoxItem with findBoxItem - they both seem to do the same thing
  • hasBoxItem returns 0 or 1
  • findBoxItem returns the slot the item is found in or 0
  • findBoxItem could therefore be used for any binary checks that hasBoxItem is currently used for
  • hasBoxItem has caching due to many calls from combat code, so that would need considering if merging the functions
• ☐ Find the various places the bodypart list ({ "arms" "ass" "legs" "cock" "head" "torso" "skin" }) is referenced and centralise it.
• Add more RP details
  • Chastity belt affects player sex too not just NPCs?
  • Scent always comes from skin, even if all other mutations are another species - maybe switch scent to the majority infection as per the new glance code