Subject: "Actually" Previous topic | Next topic
Printer-friendly copy Email this topic to a friend CF Website
Top General Discussions Gameplay Topic #17084
Show all folders

DwoggurdMon 19-Mar-07 03:19 PM
Member since 20th Jan 2004
668 posts
Click to send email to this author Click to send private message to this author Click to add this author to your buddy list
#17163, "Actually"
Edited on Mon 19-Mar-07 03:21 PM

          

My "wield" is much simplier than the current version.
Command description is rather short and logically is not very hard to understand.
My post is long because I tried to point out at the details as well as the main idea.
If you get away giant + two-handed stuff from my description it will be very simply. (that kind of stuff adds some complexity, though once you get how it is working it sholdn't be a problem)
Should carefully read my post, I don't think you will find my idea overcomplicated. (Compared with current version)

If you will try to describe how exactly the current wield is working I doubt it will take less than several pages and I'm sure it will be much harder to fully define than in my version. I challenge you
You will have to describe various situation for weapons, held items, shields, two-handed weapons separately, because they aren't processed using the same algorithm.
For example: what happens when you wield a heavy weapon?
I can think of several outcomes:
- both weapons are removed, and the new weapon is wielded.
- both weapons are removed and nothing is wielded.
- offhand is replaced.
- primary is replaced.
- if one of your weapons is cursed you may end up with a failure even if you tried to wield that weapon into the other slot and your second weapon may be removed or may be not.
- if you have held items/shield, the behavior of wield will be different.
- and so on.
In the current system I had to find out the result from experiments mostly. And it is very inconvenient when you have several weapons (or die often and thus have to change your weapon set).

I posted my idea when I realized how complicated and "random" is the current system and Gabe just made a clever remark (I bet without even thinking about that stuff I pointed here).

The key points of my idea is well defined result of commands.
If you wield to primary, exactly your primary slot will be processed.
Basically wield commands for slots are strictly defined.

Another good feature of my proposal is "remove" command without arguments.
You don't have to remember what exactly you are wielding. If you want to make your offhand slot empty, you just type "remoffhand" (or whatever syntax that will be). In the curent implementation you have to look what are you wielding. Moreover, if you wield similar weapons in your hands you may have real troubles to remove exactly what you want.
For example, when you have dualed a black sword + white sword, if you type "remove sword" which sword will be removed? If you try something like "remove black" you may end up with removing your pitch-black rings instead (happened to me). Sure, you can try longer descriptions, but the problem will still remain if you are wielding exactly the same weapons in both hands. I had similar problems in the past and often I had to use tricks like dropping my offhand weapon and picking it back, so it would be first in my inventory list and processed first.

  

Alert | IP Printer Friendly copy | Reply | Reply with quote

HOT TopicHow do you want wield to react? [View all] , Zulghinlour, Wed 14-Mar-07 10:41 PM
Reply Dual wield helpfile looks outdated, DurNominator, 21-Mar-07 06:46 AM, #31
Reply Has this gone live?, Tac, 20-Mar-07 08:13 AM, #24
Reply No, it has not., Zulghinlour, 20-Mar-07 10:39 AM, #25
     Reply FNCR, Zulghinlour, 20-Mar-07 08:43 PM, #26
          Reply Cool thanks! nt, Tac, 20-Mar-07 09:01 PM, #27
          Reply RE: FNCR, Isildur, 20-Mar-07 11:52 PM, #29
Reply Wield command ANSI standard, Dwoggurd, 17-Mar-07 02:59 PM, #11
Reply RE: Wield command ANSI standard, Gabe, 19-Mar-07 10:13 AM, #12
Reply Heh, Dwoggurd, 19-Mar-07 12:15 PM, #13
     Reply RE: Heh, Gabe, 19-Mar-07 12:20 PM, #14
     Reply Problem is, Dwoggurd, 19-Mar-07 03:30 PM, #17
          Reply RE: Problem is, Gabe, 19-Mar-07 08:43 PM, #19
               Reply You may notice, Dwoggurd, 20-Mar-07 03:35 AM, #22
     Reply RE: Heh, Valguarnera, 19-Mar-07 01:07 PM, #15
          Reply Actually, Dwoggurd, 19-Mar-07 03:21 PM #16
          Reply Some implementaion notes, Dwoggurd, 19-Mar-07 03:39 PM, #18
Reply Nice idea, however it needs one more additional command..., DurNominator, 20-Mar-07 01:31 AM, #20
Reply Answers, Dwoggurd, 20-Mar-07 03:33 AM, #21
Reply Clarification, Dwoggurd, 20-Mar-07 04:26 AM, #23
     Reply RE: Clarification, Zulghinlour, 20-Mar-07 09:35 PM, #28
          Reply Re, Dwoggurd, 21-Mar-07 05:05 AM, #30
Reply I would prefer, Dwoggurd, 15-Mar-07 11:30 AM, #3
Reply RE: I would prefer, Zulghinlour, 15-Mar-07 05:08 PM, #4
     Reply Re, Dwoggurd, 16-Mar-07 05:34 AM, #5
          Reply While a stochastic dual wield function would be fun,, Marcus_, 16-Mar-07 07:19 AM, #6
          Reply RE: Re, Isildur, 16-Mar-07 10:34 AM, #7
               Reply Say no to AI, Dwoggurd, 16-Mar-07 11:51 AM, #8
                    Reply RE: Say no to AI, Isildur, 16-Mar-07 01:17 PM, #9
                         Reply yes, Dwoggurd, 16-Mar-07 01:42 PM, #10
Reply RE: How do you want wield to react?, Isildur, 14-Mar-07 11:56 PM, #1
     Reply I don't care either way, Zulghinlour, 15-Mar-07 10:27 AM, #2
Top General Discussions Gameplay Topic #17084 Previous topic | Next topic