Grimrock

@GameMakers:

Can I ask you about adding :setOffset and :setRotation functions for Socket commponent? Please.


I want to create some object like LOG1 MultiAlcoveManager viewtopic.php?f=14&t=5314&p=58238&hilit ... ger#p58238.
In LOG1 system I spawn for every inserted object new alcove object (this system was very objects messy ).
I was lucky for LOG2 component system, becouse there is possible make different definitions in game. But for socket component it isnt possible.
---
I known problems with combination of surface and socked component, but I solved it.

I added a daemon face with eye sockets in my game. My first version tried to have 2 socket components as part of the daemon face object. That didn't work because the first socket component always got ignored by the game. Everything put into the first socket clickable area ended up being put into the second socket.

I just decided it was hardcoded to allow only 1 socket component per object and instead made the sockets separate objects with no models of their own.

Its a problem.
My idea for this socketed object is make surface object as alcove.
Check inserted object to surface, and in code make socket and clickable component.
Next step is move item to this new socket and destroy socked. (Item stay in socket position).
For this item is missing onRemove hook, but is possible to take it.
Removing this item must be managed by party hook.

This procedure worked, only isnt possible to make ingame socket in custom position.

EDIT:
description above is bad. This procedure dont worked correctly.
I make on system where is redefined WorldPosition of items in surface. This Items stay in surface only is changed this position.
This system looks good.