Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EEex based Skill Extensions #45

Closed
Grammarsalad opened this issue Aug 1, 2019 · 2 comments
Closed

EEex based Skill Extensions #45

Grammarsalad opened this issue Aug 1, 2019 · 2 comments

Comments

@Grammarsalad
Copy link
Owner

New possible rogue skills:

Climb Walls: Implement via dialog. (athletics???Acrobatis???) Might give AC/spell save bonuses for high values
https://www.d20pfsrd.com/skills/climb
http://www.d20srd.org/srd/skills/climb.htm

	{
--		["stat"] = 25, --Necessary?  Probably.  Maybe use a custom stat (need to check in dialog, etc)
		["name"] = ####, --Strref of the skill's name: Climb Walls (Climb? Athletics? Acrobatics?) 
		["description"] = ####, --Strref of the skill's description.
		["opcode"] = 110, --Will this work?  Empty opcode...
		["visibility"] = 3, --Whether the skill will appear alongside other skills in the character record screen.
						-- 0: Always show
						-- 1: Show if character can put points in skill
						-- 2: Show if skill != 0
						-- 3: Show if skill != 0 and character can put points in skill
						-- 4: Don't show
		["class_include"] = {4, 9, 10, 13, 15}, --All thieves (bards??) 
--		["kit_include"] = {0x4008}, --Any non thief kit???
--		["kit_exclude"] = {0x400C, 0x4021}, --Exclude Barbarian for Dual/multi class (i.e. qdmulit barbs)
--		["stat_exclude"] = {{34, 10, 2}, {38, 9, 2}} --Not nec (str requirement?) 
 --The syntax is similar to a SPLPROT.2DA condition, and it accepts all the relations (0 - 11) that SPLPROT.2DA does.
		                                               
	}

Use Scrolls: How??? That is, how to implement, tie it to the EEex feature? Investigate. Require int of 9 and make it so that thieves can use at least lev 1 if they put 1 point into the skill.
https://www.d20pfsrd.com/skills/use-magic-device
http://www.d20srd.org/srd/skills/useMagicDevice.htm

Likely can tie it to level, so thieves can get access at 10th level:

	{
--		["stat"] = 25, --Necessary?  Probably.  Maybe use a custom stat (need to check for actual scroll use)
		["name"] = ####, --Strref of the skill's name: Use Scrolls
		["description"] = ####, --Strref of the skill's description.
		["opcode"] = 113, --Will this work?  Empty opcode...
		["visibility"] = 3, --Whether the skill will appear alongside other skills in the character record screen.
						-- 0: Always show
						-- 1: Show if character can put points in skill
						-- 2: Show if skill != 0
						-- 3: Show if skill != 0 and character can put points in skill
						-- 4: Don't show
		["class_include"] = {4}, --SC Thief only right now (unsure about stats of multi thieves)  
--		["kit_include"] = {0x4008}, --Any non thief kit???
--		["kit_exclude"] = {0x400C, 0x4021}, --Exclude Barbarian for Dual/multi class (i.e. qdmulit barbs)
		["stat_exclude"] = {{34, 10, 2}, {38, 9, 2}} --First class level less than 10 (I think)--single class only??? Dual Class??? Also, min int of 9 just like a mage.  Maybe require certain lore/read lang levels???
 --The syntax is similar to a SPLPROT.2DA condition, and it accepts all the relations (0 - 11) that SPLPROT.2DA does.
		                                               
	}

Grrr, where are my notes on this? Requires 4 custom stats.

Level 10 stat: Required to put ranks in skill. Set by thieves at level 10.
Mage stat: Stat required to use mage scrolls. Automatically set for mages, sorcerers and bards. Values of 1 allows level 1 scrolls up to 9 allowing level 9 scrolls inclusive. Mages sorcerers and bards (though allow for bards to only have access to up to lev 6 scrolls) have max value. Each 10 points in Use Scroll increments the value of this stat by 1 for thieves (so, 10 points allows lev 1 scrolls, etc.--if zero lev scrolls in game (from magic and spells) then 1 point allows thieves to use those--maybe the values of this should be 0-11 (for poss cantrips and 10th level scrolls).
Priest stat: For cleric spells. Set to max value for clerics (and optionally for paladins). Probably not druids (though, if druid scrolls are added, will need another stat). Increments by 1 for every 15 points in use scroll stat (except gets a value for use with lev 7 scrolls at 99).
Use Scrolls Stat: Sets priest and/or mage stats depending on value.

Optionally, should include priest scroll component from S&M.

Bardic Knowledge: Maybe just lore, and maybe just allow bards to add to it... (can be used instead of various int checks), but also grant a bonus to Lore. Bards should start with a non-zero boni and thieves should be able to use it (because, why not?)
http://www.d20srd.org/srd/classes/bard.htm#bardicKnowledge
http://www.d20pfsrd.com/classes/core-classes/BARD/#TOC-Bardic-Knowledge-Ex-

	{
		["stat"] = 25, --Check in dialog, etc.  (perhaps in place of certain attributes, esp intelligence and wis) 
		["name"] = 9459, --Strref of the skill's name: Lore
		["description"] = ####, --Strref of the skill's description.
		["opcode"] = 21, --The opcode that will be used to modify the skill.
		["visibility"] = 4, --Lore already shows up
						-- 0: Always show
						-- 1: Show if character can put points in skill
						-- 2: Show if skill != 0
						-- 3: Show if skill != 0 and character can put points in skill
						-- 4: Don't show
		["class_include"] = {5}, --Bards only (though, maybe also thieves???)  
--		["kit_include"] = {0x4008}, --Could easily add certain kits...
--     	["kit_exclude"] = {0x400C, 0x4021}, --Prob not necessary (though, there is the Blade)
--		["stat_exclude"] = {{38, 16, 2}, {39, 14, 2}} --Not nec
--The syntax is similar to a SPLPROT.2DA condition, and it accepts all the relations (0 - 11) that SPLPROT.2DA does.
		                                               
	}

Performance: Bard only. Gives access to advanced songs, n stuff
http://www.d20srd.org/srd/classes/bard.htm#bardicMusic
http://www.d20pfsrd.com/classes/core-classes/BARD/#TOC-Bardic-Performance

	{
		["stat"] = ##, --Need to check for change bard song effect (and maybe instrument use) 
		["name"] =####, --Strref of the skill's name: Performance
		["description"] = ####, --Strref of the skill's description.
		["opcode"] = ###, --The opcode that will be used to modify the skill.
		["visibility"] = 3, --Whether the skill will appear alongside other skills in the character record screen.
						-- 0: Always show
						-- 1: Show if character can put points in skill
						-- 2: Show if skill != 0
						-- 3: Show if skill != 0 and character can put points in skill
						-- 4: Don't show
		["class_include"] = {5}, --Bards only 
--		["kit_include"] = {0x4008}, --Could easily add certain kits...
--     	["kit_exclude"] = {0x400C, 0x4021}, --Prob not necessary (though, there is the Blade)
--		["stat_exclude"] = {{38, 16, 2}, {39, 14, 2}} --Not nec
--The syntax is similar to a SPLPROT.2DA condition, and it accepts all the relations (0 - 11) that SPLPROT.2DA does.
		                                               
	}

Read Languages: ??? Maybe Read/Speak languages? Gives a chance to communicate with monstrous creatures?

	{
--		["stat"] = 25, --Necessary?  Yup.  Use a custom stat
		["name"] = ####, --Strref of the skill's name: Read/Speak Languages (Linguistics?)  
		["description"] = ####, --Strref of the skill's description.
		["opcode"] = 118, --Will this work?  Empty opcode...
		["visibility"] = 3, --Whether the skill will appear alongside other skills in the character record screen.
						-- 0: Always show
						-- 1: Show if character can put points in skill
						-- 2: Show if skill != 0
						-- 3: Show if skill != 0 and character can put points in skill
						-- 4: Don't show
		["class_include"] = {4, 5, 9, 10, 13, 15}, --All thieves and bards
--		["kit_include"] = {0x4008}, --Any non thief kit???
--		["kit_exclude"] = {0x400C, 0x4021}, --Exclude Barbarian for Dual/multi class (i.e. qdmulit barbs)
--		["stat_exclude"] = {{34, 10, 2}, {38, 9, 2}} --Not nec (Int requirement?) 
 --The syntax is similar to a SPLPROT.2DA condition, and it accepts all the relations (0 - 11) that SPLPROT.2DA does.
		                                               
	}

Bartering: ???
Can I change prices 'on the fly' through dialog (or lua)? Can I use the stat value as a variable for % to activate a particular response?
Can I make a particular merchant 'remember' a result? Can I make certain merchants harder or easier? (based on wis score or familiarity with PC/reputation?)

Packrat: ????????
Can I do anything with stat 71 Encumbrance? Seems unlikely. Wouldn't adding to that stat just increase encumbrance? And, a negative result would be bad. But, maybe a custom stat could lower encumbrance by a percentage????

What about 47 moralrecoverytime?

@Grammarsalad
Copy link
Owner Author

Other ideas:

Sense evil: paladin sense evil (reset time before it can be used again)

Dispel Magic: casters reset time

Rage: % to enter into rage for barbarian, berserker and (in fnp)the zealot

Use poison: for rogues and blackguards. Chance to poison self for non assassin/blackguards

Survival: track and chance to gather 'special ingredients' in wilderness environments (rangers)

Heal: allows priests and such to have a chance to heal wounds

Herbalism: Chance to treat poison, disease and other ailments

@Grammarsalad
Copy link
Owner Author

Hmm, this belongs in proficiencies rather than b_kits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant