format on this page are copyright by kmscript, parser for public are not allow.
- .kms
- kms is source code of script made by kmscript, international supported(names of module/step support all unicode)
- to run kms must release as KMSZ format
- kms is plain text format, can read/edit like javascript
- kms own by author(not kmscript)
- kms never upload to anywhere by kmscript, even for compile with lock only use an part of kms
- .kmsz
- kmsz is file compiled of kms by kmscript
- kmsz can run in W3Config
- kmsz can be lock, to unlock require an key with same lock from author
- kmsz can't read/edit, and can't decode to original kms
- kmsz doesn't have the name(module/step names) infomation, replace as number already
- kmsz packaged all resource that need, so bigger than kms
- kmsz can sell to user with or without kmscript, no need ask for kmscript official
- kmsz can jump to another kmsz by Execute
- kmsz with an version flag, can public for kmscript's Market
- .kmsz.json
- kmsz.json are number and name map file, also plain text
- an KMS release to KMSZ will made same name.kmsz and name.kmsz.json
- run an KMSZ, all names replace as number, so user only see:
1#2 failed
in console(and log), if error even author also don't known which wrong - but run an KMSZ with KMSZ.JSON file, the user can see the module and step name:
NameBoxModule1#GetBoxPosition3 failed
in console, so author will known what's wrong - but remember sell an KMSZ don't with KMSZ.JSON, that can help decode back(known what want do) to kms by cracker
- the KMSZ.JSON only for debugger, for example the author remote control target, then upload, after debug delete it
(overwrite before delete prevent undelete for non-expert, for example: type c:\windows\explorer.exe>1.kmsz.json before delete) - anyway, upload the KMSZ.JSON still no recommend, the author can get the name by number as sequence number follow the original kms
- for example:
- module1 have step1 and step2
- module2 have step3 and step4
- then module1 number 1 always, then step1/step2 are 2 and 3
- the module2 is 4, then step3/step4 are 5 and 6
- .kmsi
- kmsi is kmscript's video format, is lossless, contains all pixel information
- kmsi base on XOR(the P frame) but without nearby blur algorithm. in same location only 1 bit if same pixel
- unlike yuv420p etc.., kmsi are fully colors, RGB888 all pixels for digital signal, 100% same of original
- kmsi bigger than mp4(h264/265), depends on how different each frame is.
- kmsi without frame reference(h264) also no line filter(PNG), it's one-way streaming buffer-free data, can be play on very-small device
- kmsi can(but no default) with key-frame(the I frame), so lose(such UDP network) and fast-seek are supported
- automation key-frame then made when percent of content change(so a man speak with fixed position never have)
- set an fixed-value then force the key-frame by fixed interval
- kmsi can recordand replay in kmscript, and can use as image engine
- .kmsa
- kmsa is kmscript's audio format, also lossless, like kmsi
- kmsa not public yet
- .kmr
- kmr is keyboard/mouse/touch record file made by kmscript, can play back by kmr_running
- kmr is plain text format, can open any editor(such notepad), the syntax:
time command parameter1 [parameter2] - all number are HEXformat, for example after 161 milliseconds move the mouse to 178,195
a1 mm b2 c3 - kmr replay is different way from kms:
- kmr run in the background(thread), so after running call, the kms can continue do other thing, such power check.
- unlike kms, the kmr are exact times, if any event delay the timer will ahead of next event, for example: an key press in kmr is time 10 ms but 50 used, to next wait time will -50ms
- kmr with global offset(x and y) and delay(milliseconds)
- .kmsf
- kmsf is font construct file made by kmscript, use for the character identify, such OCR
- kmsf can create in kmscript menu named KMSF Create
also cancreate by kmscript.com after developer login, support get construct as font from image
- .kmss
- kmss is audio construct file made by kmscript, use for character/people identify
- kmss
cancreate by kmscript.com after developer login
- .kmsd2
- kmsd2 is 2D construct file made by kmsript
- kmsd2 support the target by rotation, extrusion, cover and more
- kmsd2 not public yet, but D2 modelis ready
- .kmsd3
- kmsd3 is 3D construct file made by kmsript
- kmsd3 support the target by rotation, cover and more
- kmsd2 support the target by extrusion but d3 not, d3 are fixed relationship for AI, so can get the other part even invisible
for example: read the word from lips, the kmscript only need known 1/4 of lips
or known the little or ring finger also known which key of index finger pressed - kmsd3 not public yet
- .kmsd4
- kmsd4 are kmsd3 with an time line, use to known the future of object action or object will changes by action
- kmsd4 can move the position of time, to check the result is match or samething to need do because time of object should be..
- kmsd4 still in test, no business yet
UI: li_tag
KMScript.com
中文（简体）