Відео

@@im_Snas The point of this mod wasn't to have it get popular. If anything, it was more of an experiment.

@@bndlett8752 oh alright!

@@100lol2-tc9bw It is far from "new tech."

@@lelegoguemraoui772 about that...

@@bndlett8752 yah?

@@bndlett8752you WHAT

With logic?

@bndlett8752 Yea I got to do it manually...

@@OChunks could you send your code here?

@@bndlett8752 ubind @flare ulocate building storage false @copper outx outy found building ucontrol approach outx outy 0 0 0 ucontrol itemTake Container_ spore_pod 10 0 0 ucontrol itemTake Container_ spore_pod 10 0 0 end This is what I put

ubind @flare ulocate building storage false @copper outx outy found building ucontrol approach outx outy 0 0 0 ucontrol itemTake Container_ spore_pod 10 0 0 ucontrol itemTake Container_ spore_pod 10 0 0 end

It isn't difficult within itself tbh. The worst part was getting used to the feel of the mouse itself. Otherwise, it was similar to using a regular infrared mouse. (There's also some cleaning that has to be done once in a blue moon)

Elaborate, please.

@@bndlett8752 A good design must contain a unique and interesting idea, and it must be implemented correctly. Is this an interesting idea? Simply combining the properties of two walls already in the game, What does it have to do with the bad sprite, which is a simple recolor and a palette that makes you want to puke.

@@Velan1gt What is a unique and interesting idea is purely subjective. To me, composite walls were a unique and interesting design. Although, to other individuals, it may not be as interesting of a design - understandably so. As for the "sprite recolor," you're not making sense there. If you're just saying that my spiriting is bad, then yes: it is. I never had intentions to go full production with this mod. I made it primarily to experiment with the Mindustry modding API. With that said, I never found it useful to actually try to get a proper sprite made.

Thank you for the suggestion. I don't have any spriting experience, so I just took a color from the plastanium wall and overlayed it over the surge-alloy wall at 50% opacity. The sprite shown in the thumbnail and in-game was mostly just there to act as a placeholder. Also, I'll be copy and pasting this reply to another comment that is similar, so don't be surprised if you see this reply again but on a different comment.

Thank you for the suggestion. I don't have any spriting experience, so I just took a color from the plastanium wall and overlayed it over the surge-alloy wall at 50% opacity. The sprite shown in the thumbnail and in-game was mostly just there to act as a placeholder. Also, I copy and pasted this from another comment that is similar, so don't be surprised if you see this reply again but on a different comment.

It's possible, yeah.

I had the same question in mind

It is possible, it's just that someone is going to have to design and optimize a 3D engine.

It is.

I was thinking about that implementation, but I never got around to doing it. It seemed a lot simpler to just make a basic moving block implementation in order to ensure that it worked. Although, if I wanted to, I could absolutely do a unit implementation now. It's just that there wouldn't be much of a use.

@@bndlett8752 ok, it could be used to siege at distance

@@Mantyros No. Mindustry already has a better native implementation.

@@bndlett8752 ok

Please do elaborate on what you mean with this

​@@bndlett8752Use shootX and shootY

Here are the pros and cons to using an arc: Pros: 1. Only one person can try to control the touchscreen at a time 2. An arc doesn't need to be powered (and therefore, shoot) in order for it's click to be registered, which is overall more convenient for the user. Cons: 1. Someone can just force you out of the arc via deleting it, which will basically remove your authority of the screen until you get back into the arc. 2. You need to actually get into the arc first. This isn't as much of an issue on Erekir sandbox maps, but it does cause issues on Serpulo sandbox maps. Especially whenever the schematic is placed a decent distance away from the core. I am willing to deal with the cons in order to have the pros.

@@bndlett8752 Shootx and shooty can also only have one person at a time, and it does not need power either

@@someone4229 until someone moves in closer and the authority is switched. The issue is primarily with ensured authority. Generally speaking, I'd say that arcs will provide more "ensured authority."

No specific reason. That's just my preference. Although, it does come with its pros: 1. Only one person can control the touchscreen at a time 2. An arc doesn't need to shoot in order for it's x and y values to be recorded, which is overall more convenient for the user. Although, it isn't without it's cons: 1. Someone can just force you out of the arc via deleting it, which will basically remove your authority of the screen until you get back into the arc. 2. You need to actually get into the arc first. This isn't as much of an issue on Erekir sandbox maps, but it does cause issues on Serpulo sandbox maps. Especially whenever the schematic is placed a decent distance away from the core.

Get yourself the developer mode mod and run the command "Blocks.hyperProcessor.instructionsPerTick = 200" (or whatever integer best fits your needs) whenever you're testing the logic. It's probably going to be painful to try to test the logic otherwise. Also, you probably will have to rerun the command every time you load a world. Mindustry doesn't save the JS configuration when you leave the world. Although, it could also be the client itself that is affected by the command, but I can't say for sure as I don't know the dynamics behind adjusting variables for blocks and how that information is managed when joining/leaving a world.

Use sensor to detect arc firing position it will still be detected even though it have no energy

You can read the turret's target position and whether or not it's firing

@@bignerd3783 Generally speaking, there are certain turrets whose turret position you cannot read. I'm pretty sure those are typically just turrets that require a physical resource in order to operate (don't take my word for it, I haven't read the source code for that). Although, the arc is generally an exception as you can read its position at all times: even if it has no power.

In Russian / русском языках Читать описание. В нем содержится ссылка как на исходный код, так и на компилятор, который использовался для его реализации. Хотя в фактическом объяснении: Сначала он определяет положение дуги и дисплея, вычисляет относительное положение, а затем умножает относительное положение на количество пикселей в блоке. После этого вы получите положение курсора. Затем он занимает указанное положение курсора и сверяет его со списком значений положения и размера. Эти значения положения и размера предназначены для кнопок. Если курсор находится в нужном диапазоне значений, то он проверит, нажимает ли игрок. Если игрок нажимает, то он, наконец, возвращает значение true. После того, как оно вернет значение true, будет запущена функция, которая управляет положением блока в зависимости от того, какой блок был возвращен. Это довольно общее объяснение, и оно не объясняет всей динамики кода, поэтому я предложил посмотреть исходный код на Github, поскольку он показывает полную динамику кода. In English / на английском языке Read the description. It provides a link to both the source code and the compiler that was used to implement it. Although, in an actual explanation: First, it takes the position of the arc and display, calculates the relative position, then multiplies the relative position by the number of pixels per block. This will then give you a cursor position. Then, it takes that cursor position and checks it against a list of position and size values. These position and size values are for the buttons. If the cursor are within the proper range of these values, then it will check if the player is clicking. If the player is clicking, then it will finally return true. After it returns true, then it will run a function that controls the position of the block depending on what block was returned. This is a bit of a general explanation and doesn't explain the full dynamics of the code, which is why I specified to look at the source code on Github as it does show the full dynamics of the code.

@@bndlett8752 Thanks! / Спасибо!

Absolutely. This was primarily just a test implementation. I intend to possibly use it for something more other than just moving a block around the screen. Then again, as shown in the video, processors as-is are just not fast enough to handle all of the operations that are used. I wrote the system to be highly dynamic, which results in it also being severely limited by logic processor speed. It will also get *a lot* slower with more button implementations.

@@bndlett8752 multi threads?

@@ArdLight I probably could do that but I'm not sure how much it'll help. AfaIk, there isn't really much that multiple processors could optimize.

@@bndlett8752now make a working phone with internet to download mindustry on this phone

Same tbh

HAHAHAHAH

I FOUND YOU LETT

YOU CANNOT HIDE FROM A DIVINE BEING

Why? All I did was press one button.

​​@@bndlett8752i celebrate every parry i do because i do it by luck 💀

I can, I just don't feel like it - I'd have to perfectly parry each time.