Old fork of the sphere with features about source-x HOT 3 OPEN

I don't see any reason to be added as we already have them,

FOR loop or FORTAGS loops is not a big deal, can be added but I am not sure if it's necessary.

REF1 is a CUID reference so you can use .NAME .TYPE .BLABLA, so no need to add PLOCAL for it.

@SaveStart and @saveend triggers for every item can be really expensive, I am not sure but it can be added after made some tests.

We don't need ADDTIMERD as we already have TIMERFMS for it.

For dialog close, we already have dialogclose command for any dialog but it may be improved.

from source-x.

1. Can you explain better PLOCAL? It looks like REFx.
2. I fear this will encourage using a lot of tags, polluting them, but per se it could be a good idea.
3. 100% sure it will be really too much expensive.
   4, 5) I second what xwerswoodx said.

from source-x.

1. I'll finish you off
   we have also PTAG like tag+ref.
   ptag.item =
   ptag.item.name = blablba
   ptag.item.cont =

first of all, it is clear and readable

plocal.sys
plocal.plr
plocal.item
plocal.npc

on the third page, I already forget what happened at the beginning.

well, for example, there is also comfort

for 1 2
	local.i = "<eval(<local._for>)>"
	doswitch <local.i> - 1
		begin
			plocal.npc_<local.i> = <f_newnpc c_enc_angel>
			plocal.npc_<local.i>.speechcolor 050
		end
		begin
			plocal.npc_<local.i> = <f_newnpc c_enc_daemon>
			plocal.npc_<local.i>.speechcolor 112
		end
	enddo
	plocal.npc_<local.i>.p = <args>
	doswitch <local.i> - 1
		plocal.npc_<local.i>.move 1 <eval {-1 1}>
		plocal.npc_<local.i>.move <eval {-1 1}> -1
	enddo
endfor

3. Well, these are actually my seconds, why should you count them?
   I use BACKGROUND SAVE and it's almost unnoticeable

or you can do it so that it can be enabled and disabled from scripts. in principle, is this enough for statistics once a day?

from source-x.