View Full Version : weapons from .d3dbsp
maxdamage99
7th January 2019, 11:55
how get array of weapons from map?
example?:
weapons = getentarray("weapon", "classname");
precacheItem limit: 64
my scripts precacheitems: 64
but someone maps have weapons from mapper => items more 64 => bugggggggs
i want delete all weapons, which not precached from my scripts
voron00
7th January 2019, 11:59
Maybe hex edit the bsp and remove those weapons.
maxdamage99
7th January 2019, 12:20
I need to make a decision that will work on all maps
+ I need to remove not all weapons, but only those that I did not register in the scripts
if the weapon is on the map and is in my scripts - it remains
stoiczkow
7th January 2019, 19:33
It depends what you understand by saying all maps :cool:
I have about 210 maps on 400 Mb with 29 random weapons and 24 fast options and with 15 weapons you can buy for money and 20 weapons blocked or changed for another model and blocked.
The best way is to block weapons you don't need or change for another model to get a new aspect.
If you want to see it let me know.
kung foo man
8th January 2019, 02:26
Track down the function which actually parses the entity text in d3dbsp and just filter the items/weapons via libcod (maybe add gsc parse entity callback for the gsc-only developers)
maxdamage99
8th January 2019, 11:00
It depends what you understand by saying all maps :cool:
I have about 210 maps on 400 Mb with 29 random weapons and 24 fast options and with 15 weapons you can buy for money and 20 weapons blocked or changed for another model and blocked.
The best way is to block weapons you don't need or change for another model to get a new aspect.
If you want to see it let me know.
Interesting, tell here
maxdamage99
8th January 2019, 11:04
Track down the function which actually parses the entity text in d3dbsp and just filter the items/weapons via libcod (maybe add gsc parse entity callback for the gsc-only developers)
yes, callback for "spawn" items on map - good
main problem: weapons and map lists: constantly changing and very problematic to keep track => therefore, the file .d3dbsp editing option is not suitable
stoiczkow
8th January 2019, 13:55
Interesting, tell here
Come and see here; connect 137.74.7.15:25076.
maxdamage99
9th January 2019, 04:40
Come and see here; connect 137.74.7.15:25076.
:)
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.