NooBlet
-
Posts
1,530 -
Joined
-
Last visited
-
Days Won
14
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by NooBlet
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.6
-
Please delete your config file before update . i have Rewritten the config to fix this issue ive tested it over 4 different seed and it was correct every time hope this help you
-
Changed Status from Pending to Work in Progress
-
applied some fixes . opening test server now to test wipe cycle
-
ill have a look
-
Changed Status from Pending to Not a Bug
-
yes the makeportal command is only to get the data that has to be entered into the config file to let the portal spawn at that monument .. and that spawned portal will be an exit only . you can only have one portal per monument , and as many monuments as you like ... monuments that duplicate like supermarcet,lighthouse and undewaterlabs are excluded to prevent issues . . so when you watch the video . i show how to do this
-
i need more than that my friend. where is your current config . need the logs from console around that time what portal did you create . teammate , last death or monument
-
how do you know? . id the map bounds correct for the rigs . is it a prefab from latest rust , is the prefab constraints correct ..... i dont create maps . i just make plugins . so i can show you in normal rust the plugin works ... and as i said . because i dont know what makes the oilrig different in a custom map i cant preproduce this issue . or even know how to fix it
-
you need to reach out to the map dev . and ask what is different to proc map oilrig and his . .. like i said before . all this plugin does is hacking extra crate . so there is no control(from pluginside) with the npc . thats all on facepunch side . and on this case the map
-
so now the question is . is the oilrig the exact same as normal rust . or did the dev of that map changed it
-
no .... you did not say custom map ..... the seed and size is to get the exact map to reproduce the issue ... custom map is different .. that means there is something else going on with the npc nav spawn that could be the issue .
-
ok so its the seed ... in test server with your seed and size and the heavyrigplugin not loaded . small oil ch48 npc dont move from spawn . but do in large .... with plugin loaded large all moves with event or not .. so this is not plugin its the map seed that has a nav mesh issue at small oil rig . i did record all the test if you need it
-
maybe a silly question..... with betternpc . are changing the aperance of the npc . if so . can i see your config and data file of betternpc that pertain to Ch47
-
im going to load that map quick and check
-
all this plugin does is calling more chinooks so if working normal without plugin it must work correct with wave ... map size? so i can test seed
-
Map seed ? and does the npc move if wave is not activated ? (normal oilrig crate hack)
-
again this plugin does not controlling npc's . please check in your console these 2 convars ai.think ai.move and then provide list of all current plugins . map seed and oxide version
-
and if you can give me the console error at time
-
mmmm as the rpc is to with mount . , @JuJu can you please make video what you did and to see the error happening ?
-
i dont own this plugin . but wrecks . what else is mountable in this plugin .. just the computer station ?
-
myself i try to respond within 24hours . but as life always getting the way it might take a few hours longer . then with info supplied from customer . you have to try ro replicate the results and find away around it .... i agree with @Wrecks do some test to give as much info to the dev and your problem can be then properly addressed
-
you do realize that some issues can not be sorted out within few min.... just give the guy some time to respond and look into the issue ... .
-
you need to give more time . some of us is in different timesones and not to mention some of use has jobs aswell . min give the guy 2 days 48 hours
-
when did you open the support ticket ? on the plugin page? @JuJu
