By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!Can someone help me figure out how to share one configuration file through lets say 4 map cluster, so I can edit just one file for whole cluster to take change
First things first, the sell options to the store is near the bottom of the script, you will have to manually add the code yourself, along with the blueprint price, description and so on, its very time consuming for anyone to do it just like that, specially since you will have to chose the price, the amount, the description,
The code below is for the sell items, in this particular example, is 1000 element dust for the price of 1010 points, for every new item you want people to sell in your shop you will have to add new chunk of code after the
lementDust'"
},
{
"elementdust":{
"Type":"item",
"Description":"description here",
"Price":x price here,
"Amount":x Number here,
"Blueprint":"blueprint path here"
},
{ and so on
Hi i am not getting it to work / sell correctlyCode:}, "SellItems":{ "elementdust":{ "Type":"item", "Description":"1000 x Element Dust", "Price":1010, "Amount":1000, "Blueprint":"Blueprint'/Game/Extinction/CoreBlueprints/Resources/PrimalItemResource_ElementDust.PrimalItemResource_ElementDust'" } },
this way is the only way that works correctly for me
"piedra":{
"Type": "item",
"Description": "100x stone",
"Price": 10,
Amount: 100,
"Blueprint": "Blueprint '/ Game / Mods / Stack50 / Resources / PrimalItemResource_Stone_Child.PrimalItemResource_Stone_Child'"
}
but not this way
"piedra1": {
"Type": "item",
"Description": "100x stone",
"Price": 10,
Amount: 100,
"Blueprint": "Blueprint '/ Game / Mods / Stack2500-50 / Resources / PrimalItemResource_Stone.PrimalItemResource_Stone'"
}
I have also tried with
"piedra2": {
"Type": "item",
"Description": "100x stone",
"Price": 10,
Amount: 100,
"Blueprint": "Blueprint '/ Game / PrimalEarth / CoreBlueprints / Resources / PrimalItemResource_Stone.PrimalItemResource_Stone'"
}
and also with
"piedra3": {
"Type": "item",
"Description": "100x stone",
"Price": 10,
Amount: 100,
"Blueprint": "Blueprint '/ Game / Ragnarok / CoreBlueprints / Resources / PrimalItemResource_Stone.PrimalItemResource_Stone'"
}
without having a good result, the idea is to be able to add more articles so that the user can sell, I would appreciate it if you can help me, thanks in advance
View attachment 2731hi,sir,thank you for your work,thank you,it is great progress.
how to change ark shop word color?could you add it,thanks.
Hola.Hello, I'm having an issue where the game, upon loading, keeps saying it cannot use value() with null. I am using the MySQL database to try and connect all of the servers on the cluster, but I am at a loss on how to try and fix this issue. JSON is valid, so no issues there. I'm fairly new at this, but I followed all the tutorials that I could find and could not find anything to resolve this issue. ;-;
Any help is appreciated!
@ProjectRoot
Yes, im sure. The entire /shop X pages displays sequential numbers, however only the proper buyid from the config file work. The very first test file I used had sequential buyids, but that file is long gone. Could it be cached somewhere?
Can someone help me figure out how to share one configuration file through lets say 4 map cluster, so I can edit just one file for whole cluster to take change
how to fix
error after update ARK Version: 311.74
all plugin not change config
ArkShop 2.8 config.json not change last change time 2020-06-10 9:09pm on GMT+7
before update ARK Version: 311.74 plugin is normal work
Thanks
View attachment 2736View attachment 2737
You can fix your shop and your permissions. Wooly has posted an api update on his discord that will fix the shop plugin , and Agito has posted a permissions fix in his discord. They both work! Good luck!After update ArkApi::IApiUtils::GetSteamIdFromController(player) can't get correct steamID, so shop doesn't work.
Wooly #fixed-plugins channel - https://discord.gg/mkRWyNqDo you happen to have those discord links?
We use essential cookies to make this site work, and optional cookies to enhance your experience.