• If you have a mod, tool or prefab, please use the Resources section. Click Mods at the top of the forums.

Stallionsden Mods & Modlets

Status
Not open for further replies.
From what I've seen if you can search it and have the on search destroy it and replace it with your growable, which looks like open cabinets, and then have it grow into a helper (the one that determines if it'll be lootable again) it would work, but that's just going off of S420's mod for cars.
The timing isn't going to line up with days, it'll line up with whenever it was "broken" or "harvested" because it's acting like a plant.

So the workflow for searchables that have doors should go:

Helper -> Search (If helper returned true) -> search breaks the object (like supply crates) into an open cabinet with a growth parameter -> set the growth period to like one minute for testing -> growth into helper -> helper returns true or false.

Eventually this means that POIs will be unlootable as helpers won't always return true but it would close ones that can be searched again.

I kind of want to tinker with it myself, but I'm lazy as I said in my other thread, I want to play. though getting 2m exp per level is kind of stunting that. :p

-- Lana
Nah found the issue due to the block being a grass object it needed sun to work lol. So ofc inside they didn't work. When I put them on the roof they worked. Thanks to telric. I have a new method not as good as the growing as the growing you could set it to a long time between respawning whereas this way only allows 63 minutes unfort. But have a few workarounds I looking at atm. But hopefully soon will have a proper working version good for release

 
Last edited by a moderator:
OPEN DOOR SYNDROME WITH RESPAWN

***WARNING Not compatible with Open Door Syndrome****

WHAT DOES THIS MOD DO

This mod does the same thing opened door syndrome does except allows the respawn of containers thru out the world.

NOTES

- This makes all loot containers respawn that have a open version and randomlooter block

- A stage has 63 ticks before it goes to the next stage.

- Roughly 7 hours (441 minutes) before a container respawns.

- Changed the possibility of a full container to spawn to be 100% due to the possibility of one going a really long time of respawning. IE: A container goes thru 441 minutes then the randomlooter of that container picks a empty again therefore you would have to wait another 441 minutes to possibly get a full container and ofc the cycle would repeat.

FIXED

- Fixed pillcase not opening once looted

- Fixed mircrowave destroying on open

****WARNING****

Disregard yellow text that can be seen in console -

Those warnings are nothing important. Just means there is a repeating cycle of down / upgrades. x goes to y goes to z goes to x.

Big thanks to TELRIC for help and assistance and advice especially on direction.

 
Last edited by a moderator:
Hi Stallionsden,

I am getting the following warnings:

Code:
2019-02-11T18:22:30 63.367 WRN Block 'cntStoveOldVer1Closed' over downgrade limit
2019-02-11T18:22:30 63.367 WRN Block 'cntStoveOldVer2Open' over downgrade limit
2019-02-11T18:22:30 63.367 WRN Block 'cntRetroFridgeVer1Closed' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteel' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Closed' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open6' over downgrade limit
 
Those warnings are nothing important. Just means there is a repeating cycle of down / upgrades. x goes to y goes to z goes to x... :)

 
Hi Stallionsden,
I am getting the following warnings:

Code:
2019-02-11T18:22:30 63.367 WRN Block 'cntStoveOldVer1Closed' over downgrade limit
2019-02-11T18:22:30 63.367 WRN Block 'cntStoveOldVer2Open' over downgrade limit
2019-02-11T18:22:30 63.367 WRN Block 'cntRetroFridgeVer1Closed' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteel' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Closed' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntStoveOldRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntRetroFridgeRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelVer2Open6' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntFridgeStainlessSteelRandomLootHelper' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open1' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open2' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open3' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open4' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open5' over downgrade limit
2019-02-11T18:22:30 63.368 WRN Block 'cntMetalDesk02Open6' over downgrade limit
As Telric said ^^^^^^

And thanks Telric :-)

- - - Updated - - -

OPEN DOOR SYNDROME (NON RESPAWN VERSION) UPDATED

FIXED:

Pillcase not going to open state after being looted.

 
Those warnings are nothing important. Just means there is a repeating cycle of down / upgrades. x goes to y goes to z goes to x... :)
Have added that info to each info on both versions of open door syndrome. Thanks again Telric

 
How can I decrease the spawnrate of the wandering traders? I tried decreasing the probs, but even at 0.1 they are everywhere, literally every few meters I find wandering traders. Playing at 17.2 btw.

 
How can I decrease the spawnrate of the wandering traders? I tried decreasing the probs, but even at 0.1 they are everywhere, literally every few meters I find wandering traders. Playing at 17.2 btw.
I ventured to 17.2exp and came straight back to 17.1 Lol. Sorry tfp 17.2 was ♥♥♥♥e lol.

I been meaning to do it lol but keep forgetting ty for the reminder. Try 0.00001 or 0.05 or 0.0007 0.1 is 10% chance I will take another look tho and see if I can assist in reducing.

 
hmmm tried lowering the prob and yeh no different.. it dont seem any prob value changes the amount of traders that spawn. I tried several to no avail

 
Last edited by a moderator:
WANDERING TRADERS UPDATE

**Removed spawning.xml.

**Added traders to enemyanimals group

**lowered probability

**Traders now spawn a lot less.

SURVIVORS UPDATE

**added survivors to the enemyanimals group

**removed survivors from all other groups

**now spawns less

ADDED

*new ai tasks (still dont move or wander, however do attack enemies now)

*Approach Maggi to be healed (defend her as she dont attack enemies)

*Adjusted delays of all weapons and added in a few changes (to many to go thru)

ISSUES

- Sometimes survivors stop attacking

- Survivors struggle with snakes

 
Hi, we found a Multiplayer glitch for Stallionsdens Open Door Syndrome With Respawn. A player can destroy the blocks unlimited and 'duplicate' their items.

Any fix for this? Maybe disable the destroy items?

 
Hi, we found a Multiplayer glitch for Stallionsdens Open Door Syndrome With Respawn. A player can destroy the blocks unlimited and 'duplicate' their items.
Any fix for this? Maybe disable the destroy items?
will look into this i dont play mp lol. so was unaware thanks for bringing it to my attention.

- - - Updated - - -

do you mean the destroy on close code in loot or the destroy - 0 in blocks. The destroy on close is what is needed to make the container turn into the next stage

 
will look into this i dont play mp lol. so was unaware thanks for bringing it to my attention.
- - - Updated - - -

do you mean the destroy on close code in loot or the destroy - 0 in blocks. The destroy on close is what is needed to make the container turn into the next stage
Yes, people can destroy the blocks and the block will loop into looted, not looted, looted, not looted and that without removing the block. They can use the blocks to get stuff easy. Like the 'dead tree bug' were you can smash a tree unlimited under 0% health.

I understand that the Destroy on close code is necessary to change the block to 'open doors'. But it's now in a loop.

If this cannot be fixed, i think it's better to disable the items you get from it when you smash it. I only need to change destroy items in block.xml, right?

 
Yes, people can destroy the blocks and the block will loop into looted, not looted, looted, not looted and that without removing the block. They can use the blocks to get stuff easy. Like the 'dead tree bug' were you can smash a tree unlimited under 0% health.
I understand that the Destroy on close code is necessary to change the block to 'open doors'. But it's now in a loop.

If this cannot be fixed, i think it's better to disable the items you get from it when you smash it. I only need to change destroy items in block.xml, right?
i have removed that already. How are you looping them lol.

they should only be like this -

loot container - goes to open state. leave it alone it goes to next open state leave it alone goes to next open state etc etc til it goes back to respawn state.

destroying block effectively you have gotten rid of the container so it wont go thru that process.

Possibly when the chunk reloads it may spawn back as I have read elsewhere.

I will upload the new one for you to test as i dont play MP so it be a big help if you could test it for me to see if it fixed it :-)

- - - Updated - - -

It has been uploaded to the same link

- - - Updated - - -

I destroyed the container it went to open state i then destroyed it again and it dissappeared to a million pieces lol so maybe i not understanding

 
Status
Not open for further replies.
Back
Top