Printable View
The adventure that comes with the Core Rulebook purchase is not located within the Core Rulebook module. The Rescue At Xerxes is a separate module and is unlocked per the guidelines of adventures we provide. I opened and verified this myself when checking into your reports. If you are seeing something differently with Rescue At Xerxes, we might need to see what you are seeing to help get this resolved.Quote:
Originally Posted by enrious
Unforseen Circumstances hotfixed so it is unlocked.
Looks like Vicious on the Ushaan-Tor does not seem to be applying
Pushed an update to resolve this report.
Hello Folks
I starting my first campaign in STA official, and for some reason the only assets (in all 4 choices under the tab) are the token badges. Even when I add to the images folder, nothing new appears in the assets tab, I don't even get any new download from the Forge that I purchase. Nothing existing from the my images folder shows either. I have been running 5e and Savage Worlds adventures for a couple of years now and I did not have this problem. I have also hit the folder update button.
Ty in advance.
Ted
I'm not sure if this is a bug or something unintentionally working as intended. I've added a few species and talents from the books, and the capitilization is a bit weird. The three I've noted so far are "Ferengi (DS9 Character Pack)", "Warrior's Strike", and "Silverblood (Mimetic Doppelgänger)". As far as I can edit, they appear as they just did. However, when I create a character in the lifepath steps creator option, they appear as: "Ferengi (Ds9 Character Pack)", "Warrior'S Strike", and "Silverblood (Mimetic DoppelgäNger)". It appears to me that something is forcing them to appear as Title Case, and interpreting certain characters as part of a word (DS9 >Ds9), or as the end of a word (än > äN, apparently an apostrophe counts as well). The apostrophe was fixed by changing the ’ (right apostrophe) to a ' (straight apostrophe), but I'm not sure how to "fix" the other items. The db.xml hasso I assume it's the "string" type that is forcing title case, but I have no idea.Code:name type="string"
Not a bug, it is working as it was intended to. The code needs to parse the text and supply automation. So all those strings tend to get lowered and then when finished with the automation needs, then made into title case for output.
So is there a way to make things display as they're intended to? Why does an ä, which should be a normal letter, signify the end of a word?Quote:
Originally Posted by superteddy57
You can view the StringManager.titleCase script in CoreRPG. This is the function that gets called. The only place I see it using this within Star Trek is when it's setting the text for the buttons. When it sets the data to the character sheet it copies the record or sets the data from the record itself. So, are you saying the text is not appearing on the character sheet the same as the record?
No, it appears to be in things like buttons, so I suppose working as "intended". I only saw it in the Character Creator process, on buttons for species and tlanets, but also on the left side once the species was chosen.
Since the STA ruleset is inaccessible, how can we know what parts of the CoreRPG set are being used or where? Or how can we build extensions or whatever that correctly call things like attributes or disciplines, that aren't in the Core set?
You unfortunately can't know specifically. The publisher decides if a ruleset is vaulted and the code not available to the public.
When selecting a training (in the ruleset, command, operations, and sciences track), each one gives an option of two disciplines to have as your 'major', which is increased by two. This works properly. However, the rules as written say that after picking that major, you increase any other two disciplines by one—the ruleset doesn't allow you to choose the other major discipline choice as one of the minors.
So if you choose command track in the character creator, and select command as the 'major' discipline, you can't select conn as a minor. This occurs regardless of whether a discipline is at the limit for this step of 4 or not.
The ruleset is currently in lockdown and may be some time till you see the update. The next update will remove the gate keeping on trainings. The ruleset won't hinder selection moving forward when a new update is pushed. So it will be up to the player to ensure they follow the not exceeding 4 at that stage. This will ensure those selections are available.
Career events are allowing any discipline to be chosen, even though most of them have a specific discipline named in the description, and chosen in the details.
MOD: Merged your previous post with the Bug Report thread. As I mentioned in my previous post a fix will be made available when the ruleset is no longer on lockdown.
The "blade" item has the "heavy blade" item's examples; it should have "(Sword, Mek’leth, etc)".
Ok, sorry, I thought the Trainings issue was a significant enough bug to warrant its own thread. Should ALL bug reports go here?Quote:
Originally Posted by superteddy57
Additionally, I don't know what "on lockdown" means. Should we not report bugs until it ends?
Yes, it's what we recommend all developers to monitor. So other developers for modules will be looking this thread for issues. Lockdown means that no updates will be pushed till the current Beta is released LIVE. So all those updates will be pushed to the TEST server or held till the rulesets are released from Lockdown status.
Torpedoes appear to be adding the ships security *and scale* to their damage dice. For torpedoes, it should only be the torpedo type's base damage + the ship's security. Pages 254-255 of the core book are where that appears.
(There also isn't a way to manually change anything about that.)
Well you could use the misc box to adjust. I however thought the system in place was a bit of a headache and decided to expand the entry line with editor window details instead. So creating a weapon is done there now. The ruleset however is in lockdown and a push LIVE will be done once this current BETA goes live. When it is pushed to the TEST server, you may test it out there if you would like.
I am not sure if this is the correct place to report this but I hit the following error in STA as the GM. No custom content.
[11/30/2023 8:47:39 PM] [ERROR] Script execution error: [string "..rek Adventures 2d20:..ts/manager_char.lua"]:1337: bad argument #1 to 'concat' (table expected, got nil)
This happens when rolling damage from the combat tab with in any character sheet. Some players were encountering the some issue. For same a relaunching FG seemed to fix the issue but for others it did not.
Any thoughts on what could be causing the issue and how to fix it?
I was able to locate the issue and a fix will be pushed to the TEST server once it's been reviewed.
Hiding the ID of NPC ships doesn't seem to work. The "ID" button is not on the top right corner in the combat tracker, and clicking the toggle on the character sheet still shows the regular name, not the Non-ID Name, to players.
I don't believe that system is hooked up for ships. Will have to have a deeper look on Monday.
I looked this over early and found the issue and pushed a new build to the TEST server that should fix the ID issue.
I updated Fantasy Grounds, and went to an STA campaign. I got an error message (below), and the party sheet now looks like a traditional fantasy rpg party sheet. The ships are gone, and there's only an inventory and an order tab.
Edit: A whole bunch of other errors popped up when I opened a charcater sheet, but it at least visually looks fine.Code:[12/18/2023 6:00:36 PM] CAMPAIGN: KDF1shot_development
[12/18/2023 6:00:36 PM] RULESET: Star Trek Adventures 2d20
[12/18/2023 6:00:36 PM] NETWORK STATUS: [Server] [Connected]
[Server Type - CLOUD - PUBLIC]
[12/18/2023 6:00:36 PM] Match successfully created on lobby.
[12/18/2023 6:00:38 PM] [WARNING] windowclass: Window class (ps_xp_quests) defined with merge attribute, but asset name does not match existing asset. [Star Trek Adventures 2d20] [ps/ps_xp.xml]
[12/18/2023 6:00:38 PM] [WARNING] windowclass: Window class (ps_xp_questentry) defined with merge attribute, but asset name does not match existing asset. [Star Trek Adventures 2d20] [ps/ps_xp.xml]
[12/18/2023 6:00:38 PM] MEASURE: RULESETS LOAD - 1.4362156 - Star Trek Adventures 2d20
[12/18/2023 6:00:38 PM] MEASURE: EXTENSIONS LOAD - 0 - 0
[12/18/2023 6:00:38 PM] MEASURE: MODULE LIST BUILD - 0.2396391 - 40
[12/18/2023 6:00:38 PM] MEASURE: REFRESH IMAGE ASSETS - 0.0239266
[12/18/2023 6:00:38 PM] MEASURE: REFRESH PORTRAIT ASSETS - 0.0015788
[12/18/2023 6:00:38 PM] MEASURE: REFRESH TOKEN ASSETS - 0.0245298
[12/18/2023 6:00:38 PM] MEASURE: ASSET LIST BUILD - 0.0500352
[12/18/2023 6:00:38 PM] MEASURE: LOAD - PART 1 - 1.983887
[12/18/2023 6:00:40 PM] [ERROR] Script execution error: [string "..rek Adventures 2d20:..pts/manager_ps2.lua"]:7: attempt to index global 'PartyXPManager' (a nil value)
[12/18/2023 6:00:40 PM] [ERROR] Script execution error: [string "..rek Adventures 2d20:..ata_desktop_sta.lua"]:19: attempt to call field 'setWindowMenuIconColor' (a nil value)
[12/18/2023 6:00:40 PM] MEASURE: MODULE LOAD - 0.2323129 - Star Trek Adventures Core Rulebook
[12/18/2023 6:00:40 PM] MEASURE: MODULE LOAD - 0.0025315 - UNOFFICIAL Discovery Campaign and Characters
The errors presented look like an issue with your CoreRPG as the existing asset is a CoreRPG control. I would suggest attempting to delete the CoreRPG.pak file in your rulesets folder and then doing another forced update to download a new copy.
Also, make sure you do not have any subfolders within your FG data folder under the rulesets subfolder. Any unpacked rulesets will override installed rulesets.
Regards,
JPG
That was probably it; I unpacked the CoreRPG pak a while ago, but it didn't give me any issues at the time. Deleting the unzipped folder fixed the issue. (Edit: I also checked for updates again after doing so.)Quote:
Originally Posted by Moon Wizard
I am now getting an error when I try to add weapons of any type to any ship.
Edit: I don't think this is related to my above issue, because everything seems to load properly, and I double checked and still get the error with an older db copy.Code:[12/20/2023 7:25:43 PM] [ERROR] Script execution error: [string "..rek Adventures 2d20:..anager_charship.lua"]:656: attempt to index field '?' (a nil value)
That should no longer be available as the system got revamped. Doesn't look like the new system was pushed LIVE before the lockdown. Once the current Beta is over, an update should be pushed LIVE to fix this issue.
Where can I find announcements about when the beta/lockdown is over? It's for all CoreRPG-based items, or just STA?
It's for anything based on CoreRPG, so all of the commercial rulesets we offer. City Hall and the Laboratory channels within the forums will relay updates on it's progress.
Looks like Vicious is no longer applying when effects are rolled
I will take a look, but I remember it working and don't believe I worked in that area.
Pushed a fix for Vicious not being processed with damage rolls.
An error keeps popping up whenever movement is plotted while in first person.
I just pushed a quick fix for that issue that applied to all CoreRPG-based rulesets. Please run a new Check for Updates to get the latest version.
Regards,
JPG
I have just come across a minor issue. Both "Quick Study" and "First Response" talents are in the system as the same effect. The "Quick Study" should actually read "When attempting a Task that will involve an unfamiliar medical procedure, or which is to treat an unfamiliar species, ignore any Difficulty increase stemming from your unfamiliarity". Manually fixing for myself right now, but felt this should be reported.
Updated the talent and will be available with next module update.
Thanks for the quick response