5 réponses à ce sujet

[kamal_]

A modification of the kc_room_in_party script from SoZ, it allows you to check for specific party sizes. Most useful I guess for detecting if someone is trying to solo or not so you can have them say I/we appropriately. Replace the == with >= and you can detect if the party is above a given size.

//check if party is a given size. Useful for conversations so the player can say I/we appropriately.

int StartingConditional(int nSize)
{
	int nPartySize = 0;

	object oPC = GetFirstPC();
	object oFactionMember = GetFirstFactionMember( oPC, FALSE );
	
	while ( GetIsObjectValid(oFactionMember) )
	{
		if( GetIsRosterMember(oFactionMember) || GetIsOwnedByPlayer(oFactionMember) )
		{
			if (GetIsDead(oFactionMember)!=TRUE)
			{
			nPartySize++;
			}
		}
		oFactionMember = GetNextFactionMember( oPC, FALSE );
	}

		if (nPartySize == nSize)
		{
		return TRUE;
		}
		else
		{
		return FALSE;
		}

}

[Dann-J]

For the singular/plural distinction I'd probably turn it into a GA_ script that sets a custom token. That way you only need the one conversation node. In fact you could define several custom tokens to cover a range of eventualities:

• I'm / We're not intimidated that easily.
• Have you been looking for me / us?
• Who do you think I am / we are ?

Etc.

[Dann-J]

Here's the custom token script I came up with, inspired by this thread. I'm using it in my current module:

 

Spoiler

// Custom singular/plural conversation tokens:
//
// <CUSTOM101>		I'm / We're (uppercase)
// <CUSTOM102>		I'm / we're (lowercase)
// <CUSTOM103>		I am / We are (uppercase)
// <CUSTOM104>		I am / we are (lower case)
// <CUSTOM105>		Am I / Are we (uppercase)
// <CUSTOM106>		am I / are we (lowercase)
// <CUSTOM107>		I / We (uppercase)
// <CUSTOM108>		I / we (lowercase)
// <CUSTOM109>		Me / Us (uppercase)
// <CUSTOM110>		me / us (lowercase)
// <CUSTOM111>		My / Our (uppercase)
// <CUSTOM112>		my / our (lowercase)
// <CUSTOM113>		Mine / Ours (uppercase)
// <CUSTOM114>		mine / Ours (lowercase)
// <CUSTOM115>		Myself / Ourselves (uppercase)
// <CUSTOM116>		myself / ourselves (lowercase)

void main()
{
object oPC = GetPCSpeaker();
object oPMember = GetFirstFactionMember(oPC, TRUE);
oPMember = GetNextFactionMember(oPC, FALSE);

string s101 = "I'm";
string s102 = "I'm";
string s103 = "I am";
string s104 = "I am";
string s105 = "Am I";
string s106 = "am I";
string s107 = "I";
string s108 = "I";
string s109 = "Me";
string s110 = "me";
string s111 = "My";
string s112 = "my";
string s113 = "Mine";
string s114 = "mine";
string s115 = "Myself";
string s116 = "myself";

if ( GetIsObjectValid(oPMember) )
	{
	s101 = "We're";
	s102 = "we're";
	s103 = "We are";	
	s104 = "we are";
	s105 = "Are we";
	s106 = "are we";
	s107 = "We";
	s108 = "we";
	s109 = "Us";
	s110 = "us";
	s111 = "Our";
	s112 = "our";
	s113 = "Ours";
	s114 = "ours";
	s115 = "Ourselves";
	s116 = "ourselves";
	}

SetCustomToken(101, s101);
SetCustomToken(102, s102);
SetCustomToken(103, s103);
SetCustomToken(104, s104);
SetCustomToken(105, s105);
SetCustomToken(106, s106);
SetCustomToken(107, s107);
SetCustomToken(108, s108);
SetCustomToken(109, s109);
SetCustomToken(110, s110);
SetCustomToken(111, s111);
SetCustomToken(112, s112);
SetCustomToken(113, s113);
SetCustomToken(114, s114);
SetCustomToken(115, s115);
SetCustomToken(116, s116);
}

 

Here are some example conversation nodes using the system:

• <CUSTOM101> your worst nightmare.
• It seems that <CUSTOM102> late.
• <CUSTOM103> not amused.
• Do you know who <CUSTOM104>?
• <CUSTOM105> in the right place?
• Where <CUSTOM106>?
• <CUSTOM107>'ll be going now.
• Where can <CUSTOM108> find a merchant?
• <CUSTOM109>? What have <CUSTOM108> done?
• Are you looking for <CUSTOM110>?
• <CUSTOM111> patience is wearing thin.
• Get yours hands off <CUSTOM112> treasure.
• <CUSTOM113> is a vengeance best avoided.
• What's <CUSTOM114> is yours.
• <CUSTOM107>'ll do it <CUSTOM116>.

[kamal_]

 

Here's the custom token script I came up with, inspired by this thread. I'm using it in my current module:

 

Spoiler

// Custom singular/plural conversation tokens:
//
// <CUSTOM101>		I'm / We're (uppercase)
// <CUSTOM102>		I'm / we're (lowercase)
// <CUSTOM103>		I am / We are (uppercase)
// <CUSTOM104>		I am / we are (lower case)
// <CUSTOM105>		Am I / Are we (uppercase)
// <CUSTOM106>		am I / are we (lowercase)
// <CUSTOM107>		I / We (uppercase)
// <CUSTOM108>		I / we (lowercase)
// <CUSTOM109>		Me / Us (uppercase)
// <CUSTOM110>		me / us (lowercase)
// <CUSTOM111>		My / Our (uppercase)
// <CUSTOM112>		my / our (lowercase)
// <CUSTOM113>		Mine / Ours (uppercase)
// <CUSTOM114>		mine / Ours (lowercase)
// <CUSTOM115>		Myself / Ourselves (uppercase)
// <CUSTOM116>		myself / ourselves (lowercase)

void main()
{
object oPC = GetPCSpeaker();
object oPMember = GetFirstFactionMember(oPC, TRUE);
oPMember = GetNextFactionMember(oPC, FALSE);

string s101 = "I'm";
string s102 = "I'm";
string s103 = "I am";
string s104 = "I am";
string s105 = "Am I";
string s106 = "am I";
string s107 = "I";
string s108 = "I";
string s109 = "Me";
string s110 = "me";
string s111 = "My";
string s112 = "my";
string s113 = "Mine";
string s114 = "mine";
string s115 = "Myself";
string s116 = "myself";

if ( GetIsObjectValid(oPMember) )
	{
	s101 = "We're";
	s102 = "we're";
	s103 = "We are";	
	s104 = "we are";
	s105 = "Are we";
	s106 = "are we";
	s107 = "We";
	s108 = "we";
	s109 = "Us";
	s110 = "us";
	s111 = "Our";
	s112 = "our";
	s113 = "Ours";
	s114 = "ours";
	s115 = "Ourselves";
	s116 = "ourselves";
	}

SetCustomToken(101, s101);
SetCustomToken(102, s102);
SetCustomToken(103, s103);
SetCustomToken(104, s104);
SetCustomToken(105, s105);
SetCustomToken(106, s106);
SetCustomToken(107, s107);
SetCustomToken(108, s108);
SetCustomToken(109, s109);
SetCustomToken(110, s110);
SetCustomToken(111, s111);
SetCustomToken(112, s112);
SetCustomToken(113, s113);
SetCustomToken(114, s114);
SetCustomToken(115, s115);
SetCustomToken(116, s116);
}

 

It seems the tokens are global, so one would only need to include that stuff in the module load. Is that correct? If so that's far superior to my system.

[Tchos]

I might have used a system like this in mine.  I instead settled for the less than optimal approach of always referring to the PC as plural, with the justification that I designed the thing with a party in mind.

[Dann-J]

I might have used a system like this in mine.  I instead settled for the less than optimal approach of always referring to the PC as plural, with the justification that I designed the thing with a party in mind.

 

I had also made the assumption that the player would always have companions with them, and so used plurals in most cases. However it looked strange when I tested the module with a lone character, and there's always the possibility of people wanting to solo it. Now I've got the best of both worlds; correct singular/plural distinctions without the need to duplicate lots of conversation nodes.

 

 

It seems the tokens are global, so one would only need to include that stuff in the module load. Is that correct? If so that's far superior to my system.

 

The script would need to be included in the first node of any conversation that uses it, to update the singular/plural distinctions to reflect the current party size. It would also need to be called again in any conversation where companions can be added or removed at anything other than an end node.