Problems with simple things: Hatchet(Melee weps) & Custom_Loadouts

J

justchil

Well-Known Member
Guys I'm having a hell of a time here with very simple things.

I have a reality hive all setup... everything is working great... except for some reason I can't custom loadouts to work and the hatchet and other melee weapons stay at 0 ammo...

I'd really appreciate any advice on where to look for problems... I've been watching my RPT and just put hive in trace log mode... I've been looking/checking everything I can think of with no luck.'

Any suggestions?
 
u have the tables in the db for the cust loadouts and u added it when u did the build? if yes, u are missing the correct file in dayz_server/compile/server_playerLogin.sqf with the code that make the cust loadout works.

for the hatchet, u got me there.
 
I spent ALOT of time comparing files and such... :\

I had this installed for me so i didnt know about the control panel and such. I made a local server on a VM and custom spawn / melee weapons work. I made a new build on my "production" server and copied over the server pbo then made my tweaks. I deleted the cust_loadout tables and recreated via updating schema. This fixed the loadouts somehow some way I'm not sure :D

Right now I can't import(update) the Reality schema for some reason. I'm not sure where to look for errors.

I just get Current version is 0.39 -- Attempting to update to 0.45 -- FATAL: Database migration failed!

This is my priority at the moment although working hatchets and getting wreck/care package loot to not spawn under the 'vehicle' would be nice :)
 
I see the stuff in my db log... I'm not seeing where it bombs out. I'm double checking now to make sure I don't have anything using the id's it's trying to insert. Also shouldn't it say .40 not .45? ;)

Code: 
130625 23:18:30      613 Connect    root@localhost on dayz
          613 Query    set autocommit=0
          613 Query    SHOW TABLES LIKE 'migration_schema_version'
          613 Query    commit
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    SELECT version FROM migration_schema_version WHERE name = 'Reality'
          613 Query    commit
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    SHOW TABLES LIKE 'migration_schema_version'
          613 Query    commit
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    SELECT version FROM migration_schema_version WHERE name = 'Reality'
          613 Query    commit
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    insert ignore INTO `vehicle` (`id`, `class_name`, `limit_min`, `limit_max`, `parts`) VALUES
(95, 'Ka137_DZ', 0, 1, NULL),
(96, 'ibr_as350lingor', 0, 1, NULL),
(97, 'ibr_as350_pmc', 0, 1, NULL),
(98, 'ibr_as350_pol', 0, 1, NULL),
(99, 'JetSkiYanahui_Case_Yellow', 0, 1, NULL),
(100, 'JetSkiYanahui_Case_Green', 0, 1, NULL),
(101, 'JetSkiYanahui_Case_Blue', 0, 1, NULL),
(102, 'JetSkiYanahui_Case_Red', 0, 1, NULL),
(103, 'JetSkiYanahui_Yellow', 0, 1, NULL),
(104, 'JetSkiYanahui_Green', 0, 1, NULL),
(105, 'JetSkiYanahui_Blue', 0, 1, NULL),
(106, 'JetSkiYanahui_Red', 0, 1, NULL),
(107, 'SUV_SpecialSkaro', 0, 1, NULL)
          613 Query    update vehicle set parts='motor,elektronika,mala vrtule,velka vrtule' where id='35'
          613 Query    insert ignore into world_vehicle ( vehicle_id, world_id, worldspace, chance, last_modified) values
( 95, 2, '[0,[5205.9272, 4022.6003, 1.4305115e-005]]', 0.250, 0.40),
( 96, 2, '[0,[5889.4961, 6797.897, -9.5367432e-007]]', 0.400, 0.40),
( 97, 2, '[0,[4491.751, 4787.2593, -3.8146973e-006]]', 0.400, 0.40),
( 98, 2, '[0,[1395.826, 608.14166, -1.5258789e-005]]', 0.400, 0.40),
( 99, 2, '[54,[1028.6489, 5299.1694, -0.13182747]]', 0.555, 0.40),
( 100, 2, '[170,[6046.6108, 6032.4341, 0.071113408]]', 0.555, 0.40),
( 101, 2, '[125,[1095.5248, 1502.8373, 0.011992991]]', 0.500, 0.40),
( 102, 2, '[170,[4236.9077, 3593.072, 0.053207695]]', 0.500, 0.40),
( 103, 2, '[105,[7171.2598, 1379.329, -0.046738148]]', 0.500, 0.40),
( 104, 2, '[5,[6673.5703, 1599.817, -0.1397385]]', 0.500, 0.40),
( 105, 2, '[0[7217.437, 2314.2693, -0.055636108]]', 0.500, 0.40),
( 106, 2, '[75,[7590.3486, 8260.0996, -0.082376719]]', 0.500, 0.40),
( 107, 2, '[80,[3965.0176, 9361.5029, 0.00010919571]]', 0.500, 0.40)
          613 Query    update world_vehicle set worldspace='[222,[2926.8052, 7965.2969, 0]]' where worldspace='[291,[5873.05,5326.02,0.00148487]]'
          613 Query    update world_vehicle set last_modified='0.40' where worldspace='[222,[2926.8052, 7965.2969, 0]]'
          613 Query    UPDATE migration_schema_version SET version = 0.400000 WHERE name = 'Reality'
          613 Query    INSERT INTO migration_schema_log
                (schema_name, event_time, old_version, new_version)
            VALUES ('Reality', now(), 0.390000, 0.400000)
          613 Query    insert into deployable (class_name) values ('StashSmall')
          613 Query    rollback
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    SHOW TABLES LIKE 'migration_schema_version'
          613 Query    commit
          613 Query    set autocommit=1
          613 Query    set autocommit=0
          613 Query    SELECT version FROM migration_schema_version WHERE name = 'Reality'
          613 Query    commit
          613 Query    set autocommit=1
          613 Quit
 
pretty sure i see it now lol. just ran a test db... forgot about the vehicles from other maps it will try to insert i'm sure :x
 
well removed all my vehicle spawns below 1000 still not having any luck. same output in the log and don't see error :(
 
I'll have to see how to do that exactly. I noticed If I changed the version number to either 42 or 43 it would allow the upgrade to 45 but it didn't seem to completely upgrade. I just noticed 1 new vehicle in the vehicle table when there should have been several.

I think if all else fails I'll drop my current db, upgrade then bring the user data tables back over.
 
Awesome :D

Now to figure out why melee weps don't work and why loot for wrecks/carepackages spawn in a pile under object :x
 
justchil said:
Awesome :D

Now to figure out why melee weps don't work and why loot for wrecks/carepackages spawn in a pile under object :x
Click to expand...
as far as i know i have not had any probs with melee weapons. I do however have the same problem with care packages and wrecks spawning the loot in a pile under them.
 
I figured out what it was. Nothing related to Reality actually. I messed up a couple vars when doing custom loot table.

If I figure it out I'll post it up.
 
You must log in or register to reply here.
Back
Top