Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: August 01, 2017, 03:55:46 PM »

One addition:

LANGUAGE_IS - defined as two letters (EN/PT/PO) or four xx_XX IETF language tag (followup EE) in order to mark components as language-dependent and in order to export this extra-logic data from components code into JSON.
I'm not crazy about the concept (possibly for obstinate reasons), but if it does happen, it won't include another way of referring to languages. It would use language strings that would be matched against the language name given in the LANGUAGE statement.
Posted by: AL|EN
« on: July 24, 2017, 07:30:22 PM »

One more keyword: GLOBAL_INSTALL_ORDER/GLOBAL_INSTALL_SEQUENCE discussed here: http://forums.pocketplane.net/index.php/topic,29663.msg338674.html#msg338674

EDIT: We need to re-think GLOBAL_INSTALL_ORDER/GLOBAL_INSTALL_SEQUENCE topic before it can be added as keyword.


INSTALL_ORDER/INSTALL_SEQUENCE won't work - http://forums.pocketplane.net/index.php/topic,29681.new.html
Posted by: AL|EN
« on: July 24, 2017, 08:24:28 AM »

One addition:

LANGUAGE_IS - defined as two letters (EN/PT/PO) or four xx_XX IETF language tag (followup EE) in order to mark components as language-dependent and in order to export this extra-logic data from components code into JSON.
Posted by: AL|EN
« on: July 01, 2017, 04:19:07 AM »

Please add few extra keywords for components:

LANGUAGE_IS (optional but required to replace mod custom code) - defined as two letters (EN/PT/PO) or four xx_XX IETF language tag (followup EE) in order to mark components as language-dependent and in order to export this extra-logic data from components code into JSON.
CATEGORY (optional) - one entry from pre-defined list, it might look's like BWS but I removed disquisition between BG1/SoD/BG2 content

Quote
General
Fixes
Language
Core Rules Modification
Quests
Spells
Items
NPC
NPC-Related
Artificial Intelligence
Tactical Encounters
Tweaks
Kits
Graphic
Portrait
Music
Soundset
Voicepack
UI
Scripts
Other

TAGS (optional) - comma separated list of tags, only letters and numbers, if the component has extra functions/content, tags can provide such info
IMAGE (optional) - direct link to jpg, png or GIFV, disallow obsolete formats like bmp,gif

Examples:
Quote
bg1NPC
CATEGORY NPC-Related
TAGS BG1,ROMANCES ( because it's for NPC who appears in BG1 and provide some sort of romance)

Quote
BG1 NPC Project Music Pack:
CATEGORY Music
TAGS BG1

We can always extend list of acceptable values for CATEGORY