Help
This issue is locked
Quote
With creative programming, robots can handle just about anything in MegaZeux (check out &, okay I cheated but still). You're right that anything remotely like this would be put off into the distant future, at which point programs would be separated from robots and the current built-ins could easily be represented as such. This is just wild speculation, though. I think this request needs a bit of work:
1) What do you plan on using this for?
2) Why can't it be handled by robots?
3) Are there any alternate solutions using what already exists?
4) Is there a way that this could be more easily integrated into MegaZeux as it is today?
Rejected for now, but I'll leave it open in case you have anything to add
1) What do you plan on using this for?
2) Why can't it be handled by robots?
3) Are there any alternate solutions using what already exists?
4) Is there a way that this could be more easily integrated into MegaZeux as it is today?
Rejected for now, but I'll leave it open in case you have anything to add
1: To extend the use of built-ins (both out of and in robotics) from the games using these so-called MZL-formatted Libraries so you can have use the same programming language (Currently named Robotics in v2.xx, should change in 3.xx), without the use of Robots,
2: Because certain elements need not be restricted to robotic extensions, mostly because of the Robot/Scroll/Sign's Element Parameter, which is the ID, PZX is dead, because ZZO stopped making forks and that's good enough, Plus if you can emulate what built-ins are included already so you can extend from the normal MZX standard built-ins.
3: For standards, MZX appearently has no reason for some elements to be modded unless forking it for your own game types and adding a counter to keep track of what version you're using, My original forks and ZZO's forks come to mind about this method of version control...
And even then, No one will want to use it because of a certain thing called a ''Fork Phobia'' even though it's open source.
In other words, Some people refuse to make a standard easy to implent even if its some good reason (That's why I wanted to add new object types as part of adding libraries of objects to MZX by 3.xx and not use the old PZX with it's incompatibilities)
4: Not that it matters, All it is is that makes it easy for those mastering robotics or a bit new to it but familiar with making stuff yourself to use in games, Plus no needing forks for more element mods/addins (ZIG(OLF format) and Game Maker(GML)/MMF(Lua) is an example of how elements as using a programming language was to be a standard)
This may be a lot difficult for me to say a bit, but I needed some time to think about what I said, MZX is ok for now, But remember, as previously stated- by v3.xx things will change as far as revamping the whole format like the switch from v1.xx to v2.xx, So it should be for the better by then!
You can process the request for later, too. As long as it's queued until then, so this should be put aside in ''Archived Requests'' even though this seems to be a redux of what I said already!
This post has been edited by smilymzx: 18 October 2014 - 01:08 PM
