rocket skins work all skins work
the new hiveext.dll is breaking all loadout configs. Revert back to the original hivext.dll pre 1.7.5.1 and your loadouts will work.
wait for a fix. Hopefully they just remove gender selection screen all together.
were these changes implemented in your last commit? I tried with the last version of the hiveext.dll and i have same issues with custom inventory and gender load screens.
I think the best possible solution would be if you had a custom inventory you just didnt get the gender loadscreen at all.
debug fps always reports high fps on server startup because their is no AI running around. Id like to see your FPS after running for 5 hours.
IF you run 30-50fps after 5 hours im presuming you are using a Headless Client to offload the zombie calculations.
I viewed my rpt for compairison and...
hey,
Not sure if you received my pm about my idea of multi theaded hiveext.dll.
At the moment im offloading alot of hive calls using a HeadlessClient thats also connecting to the DB. 2 threads are better than 1. << though id like to avoid that if we can make the servers hiveext.dll multi thread.
After doing a build it doesnt seem that my Date/Time in HiveExt.ini is taking effect. The server is still going on 24 hour rotation even after restart.
Any ideas why this is?
edit: it seems after server restart the servers time is starting at 12 even though 16 is set.
I think ayan was over worked with the amount of mods and maps out for dayz and the changes needed to make bliss work on those variants.
who knows where bliss will go.
But if 1.7.5 is released on the 1st as rumoured i can forsee a shitstorm as the vast majority of servers our their are hosted...
Confirmed by R4Z0R49 that bliss in its current state wont work with 1.7.5 to its full extent.
R4Z0R49_: None of the medical system would work tho
R4Z0R49_: as the evenhandles are now server side
Alright, i tried a few things
1. created a key and signed the .pbo. Gave files to client side and still results in kick.
2. set verifySignatures=0; and tried again, client can connect but char is invisible and db sets model back to default of Survivor1_DZ
From my point of veiw 1 Hacker running a monitor is better than 5-10 hackers running amuck in my servers. But if we can get this monitor working server side that would result in zero hackers... well untill they find a work around.
its a "hack" because its being remote executed through the client side. If this was server side it wouldnt be a "hack".
Each monitor is different in some ways. Some monitors will kill scripters when scripts are executed some dont. Some monitors you can disable the debug monitor but still have...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.